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

support string replace for resources/attributes names #9994

Closed
newly12 opened this issue May 13, 2022 · 4 comments
Closed

support string replace for resources/attributes names #9994

newly12 opened this issue May 13, 2022 · 4 comments
Labels

Comments

@newly12
Copy link
Contributor

newly12 commented May 13, 2022

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
resources and/or attributes key currently follows semconv, or k8s labels/annotations enriched by k8sattrs processor, would contains ., /, -, in cases the backend storage doesn't not allow such characters it will need a processor that converts them to a different character, e.g. _. Currently, resource / attributes processor allows doing this only by explicitly define the key name, in cases regexp is used in k8sattrs processor that, say captures all labels or annotations, there is no way to define all possible keys.

Describe the solution you'd like
A clear and concise description of what you want to happen.
Support replace string action for resources/attributes name in resource/attributes processor, which seems to be a general enough solution that would support metrics/traces/logs.

Describe alternatives you've considered
Support such action in a dedicated processor that updates resources/attributes keys, or in current transform and metricstransformprocessor.

Additional context

@newly12 newly12 changed the title support updating resources/attributes key support string replace for resources/attributes names May 13, 2022
@dmitryax
Copy link
Member

This should be a feature request for transform processor

@TylerHelmuth
Copy link
Member

I believe this will be fixed by #12991

@github-actions
Copy link
Contributor

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 10, 2022
@TylerHelmuth
Copy link
Member

Closing as this capability now exists.

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

3 participants