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

[charts/opentelemetry-demo] Use helm namespace for service.namespace in default helm values #1482

Closed
wants to merge 1 commit into from

Conversation

henry-maier
Copy link

Currently, service.namespace always gets set to opentelemetry-demo.

This results in confusing metric labels when deploying the chart into a namespace that is not opentelemetry-demo. With this change, service.namespace will be set to the namespace the chart is deployed in.

Should I also bump the chart patch or minor version here?

…in default helm values

Currently, service.namespace always gets set to opentelemetry-demo.

This results in confusing metric labels when deploying the chart into a namespace that is not opentelemetry-demo. With this change, service.namespace will be set to the namespace the chart is deployed in.
@henry-maier henry-maier requested review from puckpuck and a team as code owners January 3, 2025 19:26
Copy link

CLA Not Signed

@puckpuck
Copy link
Contributor

puckpuck commented Jan 10, 2025

The demo already follows the semantic conventions, which state that service.namespace is to represent the group of related services. This is not meant to be the Kubernetes namespace which should be captured as well with the k8s.namespace.name attribute.

Copy link

This PR was marked stale due to lack of activity. It will be closed in 14 days.

@github-actions github-actions bot added the Stale label Jan 24, 2025
@henry-maier
Copy link
Author

Closing per #1482 (comment), as the current setup is actually intended.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants