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
Hi, I'm using micrometer-registry-statsd with @timed to report time series data to DataDog, and all of my metrics have "none" in the time unit section in the metrics summary page.
I saw that in the StatsdMeterRegistry class the "getBaseTimeUnit" method returns Milliseconds, and when I updated all my metrics manually (this took forever :) ) to milliseconds, the data in my graphs makes sense.
Why doesn't it show this reported time unit in the dataDog metric? Why isn't is sent?
BTW - I asked this question in micrometer gitHub and got this answer: micrometer-metrics/micrometer#2528
They say that in their implementation (DatadogMeterRegistry) they do send the time unit in the metric metadata, and that the issue here is in the dogStatsD client.
Thanks for your help :)
The text was updated successfully, but these errors were encountered:
@ayeletmorris I'm not sure how we can help you, micrometer-registry-statsd does not use this project, java-dogstatsd-client, internally. Perhaps I'm misunderstanding your question?
Hi, I'm using micrometer-registry-statsd with @timed to report time series data to DataDog, and all of my metrics have "none" in the time unit section in the metrics summary page.
I saw that in the StatsdMeterRegistry class the "getBaseTimeUnit" method returns Milliseconds, and when I updated all my metrics manually (this took forever :) ) to milliseconds, the data in my graphs makes sense.
Why doesn't it show this reported time unit in the dataDog metric? Why isn't is sent?
BTW - I asked this question in micrometer gitHub and got this answer: micrometer-metrics/micrometer#2528
They say that in their implementation (DatadogMeterRegistry) they do send the time unit in the metric metadata, and that the issue here is in the dogStatsD client.
Thanks for your help :)
The text was updated successfully, but these errors were encountered: