influxasync sink
Toplevel influxAsyncSink
Categories:
influxasync
sink
The influxasync
sink uses the official InfluxDB golang client to write the metrics to an InfluxDB database in a non-blocking fashion. It provides only support for V2 write endpoints (InfluxDB 1.8.0 or later).
Configuration structure
{
"<name>": {
"type": "influxasync",
"database" : "mymetrics",
"host": "dbhost.example.com",
"port": "4222",
"user": "exampleuser",
"password" : "examplepw",
"organization": "myorg",
"ssl": true,
"batch_size": 200,
"retry_interval" : "1s",
"retry_exponential_base" : 2,
"precision": "s",
"max_retries": 20,
"max_retry_time" : "168h",
"process_messages" : {
"see" : "docs of message processor for valid fields"
},
"meta_as_tags" : []
}
}
type
: makes the sink aninfluxdb
sinkdatabase
: All metrics are written to this buckethost
: Hostname of the InfluxDB database serverport
: Portnumber (as string) of the InfluxDB database serveruser
: Username for basic authentificationpassword
: Password for basic authentificationorganization
: Organization in the InfluxDBssl
: Use SSL connectionbatch_size
: batch up metrics internally, default 100retry_interval
: Base retry interval for failed write requests, default 1sretry_exponential_base
: The retry interval is exponentially increased with this base, default 2max_retries
: Maximal number of retry attemptsmax_retry_time
: Maximal time to retry failed writes, default 168h (one week)precision
: Precision of the timestamp. Valid values are ’s’, ‘ms’, ‘us’ and ’ns’. (default is ’s’)process_messages
: Process messages with given rules before progressing or dropping, see here (optional)meta_as_tags
: print all meta information as tags in the output (deprecated, optional)
For information about the calculation of the retry interval settings, see offical influxdb-client-go documentation
Using influxasync
sink for communication with cc-metric-store
The cc-metric-store only accepts metrics with a timestamp precision in seconds, so it is required to use "precision": "s"
.
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.