We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Being new to processors, I was wondering how I can use the "Metrics Transform Processor" in the OTLP collector?
The text was updated successfully, but these errors were encountered:
In your config yaml file, you simply specify the transforms, like in the example below:
receivers: # [...] processors: metricstransform/1: transforms: # Transform otelcol_some_metric to otel.some.metric - include: ^otelcol_([^_]+)_(.*)$$ match_type: regexp action: update new_name: otel.$${1}.$${2} # Transform my_metric to my.metric - include: ^([^_\.]+)_(.*)$$ match_type: regexp action: update new_name: $${1}.$${2} exporters: # [...] service: extensions: # your extensions pipelines: metrics: receivers: # your receivers processors: [memory_limiter,batch,metricstransform/1] # <-- metricstransform exporters: # your exporters
More details about possible metric transforms are documented here.
Sorry, something went wrong.
I wasn't able to get it working but will try again, thank you!
I have a full example as part of this repo:
https://github.com/jpkrohling/opentelemetry-collector-deployment-patterns/blob/main/pattern-2-normalizer
[chore] update tests to bind to localhost (#6224)
2570445
Update some tests to bind to localhost instead of 0.0.0.0
No branches or pull requests
Being new to processors, I was wondering how I can use the "Metrics Transform Processor" in the OTLP collector?
The text was updated successfully, but these errors were encountered: