-
Notifications
You must be signed in to change notification settings - Fork 35
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
Full Prometheus metric name normalization disabled by default #1139
Comments
Unpinning this, as the change was reverted upstream in open-telemetry/opentelemetry-collector-contrib#23229. I'm going to keep it open for now. |
Closing, as this is not relevant anymore. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Prometheus and otel metric naming conventions aren't entirely compatible. Prometheus metric name normalization is a feature intended to convert metrics between the two conventions. See the upstream documentation for details.
In the
0.76.1
release, the feature flag for this normalization was enabled by default.The feature primarily affects the
prometheus
andprometheusremotewrite
exporters. However, it also modifies some metrics collected by theprometheus
receiver. More specifically, it trims certain suffixes from metric names. Unfortunately, this affects a lot of widely used metrics. For example, the standard container CPU usage metric:container_cpu_usage_seconds_total
->container_cpu_usage_seconds
This change breaks a lot of content built using existing metric names and prevents the Prometheus receiver from being used as a drop-in replacement for Prometheus. Therefore, we've decided to default to having this flag disabled. #1138 implements this decision.
The behavior can be re-enabled by passing the
--feature-gates=+pkg.translator.prometheus.NormalizeName
flag to the collector at startup.There is an ongoing discussion about making this behavior configurable at runtime. Please follow this issue if you'd like to learn more.
The text was updated successfully, but these errors were encountered: