-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Include service.version in prom to otlp #32398
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Actually, shouldn't this be set on all my telemetry from here? |
Not sure I understand. The prometheus receiver converts from Prometheus' |
sorry – i mean right now we get in You're probably right that until prometheus has that support this may add too much complexity. |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
receiver/prometheus
Is your feature request related to a problem? Please describe.
Right now service.name, service.instance.id, and a few others are converted to OTLP semantic convention.
service.version
is currently not converted.Describe the solution you'd like
I think it would be great if the value for service_version were converted with similar logic to allow for compatibility with otel recommendations.
Describe alternatives you've considered
I've considered using a transform processor, which would make this work, but I don't think it would let me move something from the attribute to the
Additional context
No response
The text was updated successfully, but these errors were encountered: