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
Could you let us what would be the potential use cases please ? I am worried that adding a different payload format could confuse dogstatsd-ruby users.
The use case is portability, being able to support tags and move easily from using influx and telegraf to datadog. Because at the moment no ruby statsd client supports the influx serialization, so it makes sense to use a client that already supports tags, and by being the defacto client for telegraf/influx statsd you also always ensure to any user of telegraf/influx that it's easy to move to datadog
Hi
So the telegraf agent (made by the creators of InfluxDB) allows tags to serialized into a modified statsd protocol as well.
influxdata/telegraf#39 (comment)
https://github.com/influxdb/telegraf/tree/master/plugins/statsd#influx-statsd
But they chose a different way to serialize the data.
Ideally this package should support both for portability
The text was updated successfully, but these errors were encountered: