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
Wanted to discuss a proposal. We’re currently using Dogstatsd clients to emit certain stats as gauge types for SignalFx cumulative counter type metrics. The way we do this in our fork is we designate a specific tag (i.e. cumulative_counter) to determine whether to emit a gauge as a cumulative counter in our SignalFx sink.
This is useful for third party libraries that expose cumulative counter metrics but don’t have statsd support. When being aggregated or sampled these metrics would be treated the same as gauges.
We’d like to submit our tagging and conversion functionality upstream as we could see it being a common pain point for SignalFx users. Thoughts?
Hey Folks,
Wanted to discuss a proposal. We’re currently using Dogstatsd clients to emit certain stats as gauge types for SignalFx cumulative counter type metrics. The way we do this in our fork is we designate a specific tag (i.e.
cumulative_counter
) to determine whether to emit a gauge as a cumulative counter in our SignalFx sink.This is useful for third party libraries that expose cumulative counter metrics but don’t have statsd support. When being aggregated or sampled these metrics would be treated the same as gauges.
We’d like to submit our tagging and conversion functionality upstream as we could see it being a common pain point for SignalFx users. Thoughts?
cc: @prudhvi
The text was updated successfully, but these errors were encountered: