Skip to content
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

Service graph - exponential histogram support #29628

Closed
0x006EA1E5 opened this issue Dec 3, 2023 · 5 comments
Closed

Service graph - exponential histogram support #29628

0x006EA1E5 opened this issue Dec 3, 2023 · 5 comments

Comments

@0x006EA1E5
Copy link

0x006EA1E5 commented Dec 3, 2023

Component(s)

connector/servicegraph, processor/servicegraph

Is your feature request related to a problem? Please describe.

Current use of "traditional" histograms creates many timeseries, which is prohibitively expensive (in our org).

Describe the solution you'd like

Config option to use exponential histogram, similar to span metrics connector.
https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/connector/spanmetricsconnector/README.md#L92

Describe alternatives you've considered

No response

Additional context

As mentioned above, this config option is available for span metrics
https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/connector/spanmetricsconnector/README.md#L92

@0x006EA1E5 0x006EA1E5 added enhancement New feature or request needs triage New item requiring triage labels Dec 3, 2023
Copy link
Contributor

github-actions bot commented Dec 3, 2023

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@JaredTan95
Copy link
Member

JaredTan95 commented Dec 3, 2023

make sense. @0x006EA1E5 If you do not have time to contribute or enhance, I will make time to finish this.

@JaredTan95
Copy link
Member

make sense. @0x006EA1E5 If you do not have time to contribute or enhance, I will make time to finish this.

waiting for discussion: #26648

Copy link
Contributor

github-actions bot commented Feb 5, 2024

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Feb 5, 2024
Copy link
Contributor

github-actions bot commented Apr 5, 2024

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants