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
No response
Some providers require the service.instance.id to be present in order to group some of their metrics.
service.instance.id
But noticed into our scenarios that while the pod is being created the name may be empty and service.instance.id would not be provided.
Related to: open-telemetry/semantic-conventions#312
Fix at: #2678
service.instance.id should be added to the pod attibutes
Absence of service.instance.id due to pod name be empty
1.25
0.93.0 (0.47.0 chart)
0.93.0
OS: (e.g., "Ubuntu 20.04") Compiler(if manually compiled): (e.g., "go 14.2")
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Component(s)
No response
What happened?
Description
Some providers require the
service.instance.id
to be present in order to group some of their metrics.But noticed into our scenarios that while the pod is being created the name may be empty and
service.instance.id
would not be provided.Related to: open-telemetry/semantic-conventions#312
Fix at: #2678
Steps to Reproduce
Expected Result
service.instance.id
should be added to the pod attibutesActual Result
Absence of
service.instance.id
due to pod name be emptyKubernetes Version
1.25
Operator version
0.93.0 (0.47.0 chart)
Collector version
0.93.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: