Arek Gil
Arek Gil
#93 with this change has been just merged in.
@dbern-stripe thanks for creating the issue! Sadly, I don't think the StatsD protocol specifies how to perform escaping of special characters (i.e. `.`, `|`, `:`, and `@`). Whatever approach we...
Hey @gabrielvf1 👋 Can you try hooking up the console reporter https://hexdocs.pm/telemetry_metrics/Telemetry.Metrics.ConsoleReporter.html#content and see if the event handlers are being invoked at all?
Thanks! #93 was just merged and it solves the same issue.
@benwilson512 you're right, that's what we're currently doing. Thanks for the suggestion! I'll look into it 👍
@lexmag Initially I went for a new library due to different models that `Telemetry.Metrics` and Statix assume. With Telemetry.Metrics you declare all of your metrics in one place, feed them...
@connorjacobsen You are right, two metrics will be pushed when that event is fired, but this is intentional. The library explicitly says that for counter metrics, the measurement is discarded...
Yes, I see how that might be a problem. @bryannaegele does this issue also apply to Prometheus reporter? I'm curious what's your opinion about it.
@bryannaegele in StatsD case, I group metrics by event name, so there is always a single handler for each unique event under the reporter. But thank you, it looks like...
> It does not support the "host" or "message" property @jeffutter are those just tags that need to be sent with the service check event?