You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have Telegraf parsing a binary message that comes in at 50Hz. We want to write the 50Hz data to an Influx bucket that is kept locally on a remote location. We want to take the last values and write them to a bucket that is replicated to a central location. We also want to keep the same data schema. By adding a tag instead of changing the field name, we can route the down sampled values to a different influx output.
Expected behavior
The field names are the same, but a tag is added to indicate the metrics have passed through the aggregator.
Use Case
We have Telegraf parsing a binary message that comes in at 50Hz. We want to write the 50Hz data to an Influx bucket that is kept locally on a remote location. We want to take the last values and write them to a bucket that is replicated to a central location. We also want to keep the same data schema. By adding a tag instead of changing the field name, we can route the down sampled values to a different influx output.
Expected behavior
The field names are the same, but a tag is added to indicate the metrics have passed through the aggregator.
The extra tag can of course be added using tags.
Input
Output
Actual behavior
Input
Output
Additional info
I am willing to create a PR for this myself.
The text was updated successfully, but these errors were encountered: