From 177af26ea878e673166ebbeb4518539f624a81f0 Mon Sep 17 00:00:00 2001 From: Vladimir Kobal Date: Sat, 1 Feb 2020 00:05:45 +0200 Subject: Parse host tags (#7702) * Fix memory leaks * Check for configuration options * Parse simple tags * Parse JSON tags * Remove an unnecessary check * Parse a JSON object * Parse a JSON array * Update the documentation * Fix host locks --- backends/README.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) (limited to 'backends') diff --git a/backends/README.md b/backends/README.md index 470544774b..767fd05f43 100644 --- a/backends/README.md +++ b/backends/README.md @@ -183,9 +183,14 @@ from your Netdata): are different: disks with device-mapper, interrupts, QoS classes, statsd synthetic charts, etc. - `host tags = list of TAG=VALUE` defines tags that should be appended on all metrics for the given host. These are - currently only sent to opentsdb and prometheus. Please use the appropriate format for each time-series db. For - example opentsdb likes them like `TAG1=VALUE1 TAG2=VALUE2`, but prometheus like `tag1="value1",tag2="value2"`. Host - tags are mirrored with database replication (streaming of metrics between Netdata servers). + currently only sent to graphite, json, opentsdb and prometheus. Please use the appropriate format for each + time-series db. For example opentsdb likes them like `TAG1=VALUE1 TAG2=VALUE2`, but prometheus like `tag1="value1", + tag2="value2"`. Host tags are mirrored with database replication (streaming of metrics between Netdata servers). + + Starting from Netdata v1.20 the host tags are parsed in accordance with a configured backend type and stored as + host labels so that they can be reused in API responses and exporting connectors. The parsing is supported for + graphite, json, opentsdb, and prometheus (default) backend types. You can check how the host tags were parsed using + the /api/v1/info API call. ## monitoring operation -- cgit v1.2.3