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

[processor/attributes] add metrics process self metrics #8560

Closed
hanjm opened this issue Mar 21, 2022 · 3 comments
Closed

[processor/attributes] add metrics process self metrics #8560

hanjm opened this issue Mar 21, 2022 · 3 comments

Comments

@hanjm
Copy link
Member

hanjm commented Mar 21, 2022

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

The attributesprocessor and resourceprocessor are very useful to operator telemetry attributes, it seems no self metrics currently, like how many spans delete/update attributes are affected.

Describe the solution you'd like
Add some self metrics.
Describe alternatives you've considered

Additional context
Add any other context or screenshots about the feature request here.

@jpkrohling
Copy link
Member

There are some prerequisites for this. See open-telemetry/opentelemetry-collector#4198

@codeboten codeboten added the processor/attributes Attributes processor label Jun 27, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Nov 9, 2022

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 Nov 9, 2022
@github-actions
Copy link
Contributor

github-actions bot commented May 7, 2023

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 May 7, 2023
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

3 participants