-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[connectors/servicegraph] Add native histograms support #35460
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I'm ready to start working on this |
@mar4uk please go ahead. Codeowners, any comment on direction? |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
this issue is still relevant |
Component(s)
connector/servicegraph
Is your feature request related to a problem? Please describe.
Currently, the classic histogram is used for generating request duration metrics (
traces_service_graph_request_server_seconds
andtraces_service_graph_request_client_seconds
). It requires providing explicit buckets withlatency_histogram_buckets
configuration parameter or using default buckets[2ms, 4ms, 6ms, 8ms, 10ms, 50ms, 100ms, 200ms, 400ms, 800ms, 1s, 1400ms, 2s, 5s, 10s, 15s]
Configuration could be improved with adoption on exponential histogram
Describe the solution you'd like
Allow servicegraph connector to support exponential histograms. Configuration should allow configuring which type of histograms to use
The configuration of servicegraph connector should be changed to make it possible to configure different types of histograms. It could be similar to spanmetrics connector:
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: