From 61efaee971b89bdff6a0a2f0bdd839b8e80d63da Mon Sep 17 00:00:00 2001
From: Sven Rebhan <36194019+srebhan@users.noreply.github.com>
Date: Wed, 7 Aug 2024 16:01:10 +0200
Subject: [PATCH] docs(inputs.netflow): Add note on how to tag metrics (#15713)

---
 plugins/inputs/netflow/README.md | 18 +++++++++++++++++-
 1 file changed, 17 insertions(+), 1 deletion(-)

diff --git a/plugins/inputs/netflow/README.md b/plugins/inputs/netflow/README.md
index 0c3a6b4b3..c8278acb2 100644
--- a/plugins/inputs/netflow/README.md
+++ b/plugins/inputs/netflow/README.md
@@ -112,7 +112,23 @@ the start of streaming and in regular intervals (configurable in the device) and
 Telegraf has no means to trigger sending of the templates. Therefore, we need to
 skip the packets until the templates are resent by the device.
 
-### Template
+## Metrics are missing at the output
+
+The metrics produced by this plugin are not tagged in a connection specific
+manner, therefore outputs relying on unique series key (e.g. InfluxDB) require
+the metrics to contain tags for the protocol, the connection source and the
+connection destination. Otherwise, metrics might be overwritten and are thus
+missing.
+
+The required tagging can be achieved using the `converter` processor
+
+```toml
+[[processors.converter]]
+  [processors.converter.fields]
+    tag = ["protocol", "src", "src_port", "dst", "dst_port"]
+```
+
+__Please be careful as this will produce metrics with high cardinality!__
 
 ## Metrics