mirror of
https://github.com/ClusterCockpit/cc-metric-collector.git
synced 2025-12-26 00:56:17 +01:00
2.4 KiB
2.4 KiB
influxdb sink
The influxdb sink uses the official InfluxDB golang client to write the metrics to an InfluxDB database in a blocking fashion. It provides only support for V2 write endpoints (InfluxDB 1.8.0 or later).
Configuration structure
{
"<name>": {
"type": "influxdb",
"database" : "mymetrics",
"host": "dbhost.example.com",
"port": "4222",
"user": "exampleuser",
"password" : "examplepw",
"organization": "myorg",
"ssl": true,
"flush_delay" : "1s",
"batch_size" : 1000,
"use_gzip": true,
"precision": "s",
"process_messages" : {
"see" : "docs of message processor for valid fields"
},
"meta_as_tags" : []
}
}
type: makes the sink aninfluxdbsinkdatabase: All metrics are written to this buckethost: Hostname of the InfluxDB database serverport: Port number (as string) of the InfluxDB database serveruser: Username for basic authenticationpassword: Password for basic authenticationorganization: Organization in the InfluxDBssl: Use SSL connectionflush_delay: Group metrics coming in to a single batchbatch_size: Maximal batch size. Ifbatch_sizeis reached before the end offlush_delay, the metrics are sent without further delayprecision: 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)
Influx client options:
batch_size: Maximal batch sizemeta_as_tags: move meta information keys to tags (optional)http_request_timeout: HTTP request timeoutretry_interval: retry intervalmax_retry_interval: maximum delay between each retry attemptretry_exponential_base: base for the exponential retry delaymax_retries: maximum count of retry attempts of failed writesmax_retry_time: maximum total retry timeoutuse_gzip: Specify whether to use GZip compression in write requests
Using influxdb 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".