CarbonAPI supports a significant subset of graphite functions [see COMPATIBILITY]. In our testing it has shown to be 5x-10x faster than requesting data from graphite-web.
For requirements see Requirements section below.
At this moment we are building packages for CentOS 6, CentOS 7, Debian 9, Debian 10, Ubuntu 14.04, Ubuntu 16.04 and Ubuntu 18.04. Installation guides are available on packagecloud (see the links below).
Stable versions: Stable repo
Autobuilds (master, might be unstable): Autobuild repo
Carbonapi can be configured by environment variables or by config file. For an example see
$ ./carbonapi -config /etc/carbonapi.yaml
Request metrics will be dumped to graphite if corresponding config options are set, or if the GRAPHITEHOST/GRAPHITEPORT environment variables are found.
Request data will be stored in memory (default) or in memcache.
Configuration is described in docs
Every parameter in config file are mapped to environment variable. I.E.
concurency: 20 cache: # Type of caching. Valid: "mem", "memcache", "null" type: "mem" upstreams: backends: - "http://10.0.0.1:8080" - "http://10.0.0.2:8080"
That config can be replaced by
CARBONAPI_CONCURENCY=20 CARBONAPI_CACHE_TYPE=mem CARBONAPI_UPSTREAMS_BACKENDS="http://10.0.0.1:8080 http://10.0.0.2:8080"
You should be only aware of logging: because carbonapi support a list of logger, env variables will replace only first logger.
If you apply variable
LOGGER_FILE=stdout to config:
logger: - logger: "" file: "stderr" level: "debug" encoding: "console" encodingTime: "iso8601" encodingDuration: "seconds" - logger: "" file: "carbonapi.log" level: "info" encoding: "json"
it will be equal to config:
logger: - logger: "" file: "stdout" # Changed only here level: "debug" encoding: "console" encodingTime: "iso8601" encodingDuration: "seconds" - logger: "" file: "carbonapi.log" # Not changed level: "info" encoding: "json"
auto- carbonapi will do it's best to determine backend's protocol. Currently it can identify only
protobuf- carbonapi <0.11 style protocol. Supported by go-carbon, graphite-clickhouse
carbonapi_v3_pb- new carbonapi protocol, that supports passing metadata through. Supported by carbonzipper >=1.0.0.alpha.3. Implementing support for that is in-progress for go-carbon
carbonapi_v3_grpc- grpc version of new carbonapi protocol. Currently no known implementation exists.
msgpack- messagepack based protocol, used in graphite-web 1.1 and metrictank. It's still experimental and might contain bugs.
prometheus- prometheus HTTP API
You need to have Go >= 1.14 to build carbonapi from sources. Building with Go 1.10 or earlier is not supported since 0.11.0. Building with Go 1.12 or earlier is not supported since 0.13.0.
CarbonAPI uses protobuf-based protocol to talk with underlying storages. For current version the compatibility list is:
msgpackprotocol. Support is not very well tested and might contain bugs. Use with cautions. Tags are not supported.
For backends that uses proper database (e.x.
graphite-clickhouse) you should set
maxBatchSize: 0 in your config file for this backend group.
For other backends (e.x. go-carbon) you should set it to some reasonable value. It increases response speed, but the cost is increased memory consumption.
Tag support was only tested with
graphite-clickhouse, however it should work with any other database.
Some additional steps may be needed to build carbonapi with cairo rendering on MacOSX.
$ brew install Caskroom/cask/xquartz $ brew install cairo --with-x11
This program was originally developed for Booking.com. With approval from Booking.com, the code was generalised and published as Open Source on github, for which the author would like to express his gratitude.
In summer 2018, Booking.com forked version 0.11 of carbonapi and continued development in their own repo: github.com/bookingcom/carbonapi.
This code is licensed under the BSD-2 license.