-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Collector metrics are not tagged #395
Comments
Yes, we should do that. Collector is the oldest component implemented back when we didn't use tag-based metrics system internally, so its instrumentation never got upgraded to tags, even though the metrics API was upgraded to support them. Incidentally, it will break our internal dashboard :-( ... But still worth it. |
PS did you implement influx reporter directly or with go-kit https://github.com/go-kit/kit/tree/master/metrics/influx ? |
I used go-kit support from jaeger-lib: jaegertracing/jaeger-lib#23 |
I think this is addressed by #776 and available in 1.5 release. |
I've added influx reporter and I'll attempt to make some PR out of it, but there are no tags so it's not possible to e.g. use group by or to filter by service. The reason for this is the use of
metrics.Factory.Namespace
which just adds another section to the metric name.Can this be replaced with tags? Especially
countByServiceName
could report service name as a tag, andhostMetrics
could have hostname as a tag.The text was updated successfully, but these errors were encountered: