docs(inputs.netflow): Add note on how to tag metrics (#15713)
This commit is contained in:
parent
cd5008cce8
commit
61efaee971
|
|
@ -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
|
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.
|
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
|
## Metrics
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue