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

Add metrics to understand cost of telemetry #30729

Closed
pavolloffay opened this issue Jan 23, 2024 · 4 comments
Closed

Add metrics to understand cost of telemetry #30729

pavolloffay opened this issue Jan 23, 2024 · 4 comments
Labels

Comments

@pavolloffay
Copy link
Member

Component(s)

No response

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

I would like to use the collector to understand the cost of telemetry data collection. Usually, observability vendors charge per ingest volume.

Describe the solution you'd like

I would like to have internal telemetry metrics that will help me understand how much data is collector processing/sending.

I want to understand how much each instrumented process (service) reports bytes. What is average span size and attribute cardinality?

Describe alternatives you've considered

No response

Additional context

No response

@pavolloffay pavolloffay added enhancement New feature or request needs triage New item requiring triage labels Jan 23, 2024
@crobert-1
Copy link
Member

Am I correct in understanding that you're proposing to add these to the internal metrics the collector exposes? Would these values be per telemetry pipeline, or for the running collector as a whole?

@crobert-1
Copy link
Member

Related: open-telemetry/oteps#249

Copy link
Contributor

github-actions bot commented Apr 8, 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.

Copy link
Contributor

github-actions bot commented Jun 7, 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 Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants