Repository navigation
Conversation
… of a default namespace Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
…tring Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Contributor
Author
|
Switched to encoding an unset |
Contributor
Author
|
Paused. Instead of the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Services without a
service.namespace(attribute unset or empty) got inconsistent identities: services and resource relations used an inventeddefaultnamespace, while instances, service-graph relations and monitors broke on the missing value. The namespace mapping also created an empty-name component, which sync rejects.Per the OTel semantic conventions,
service.namespaceis optional and the unset namespace is just another valid namespace;service.instance.idis unique within its(service.namespace, service.name)pair. This change encodes the unset namespace as the empty string everywhere:service.namespace.urn:opentelemetry:namespace/:service/<name>for such services. Service-graph relations no longer require the namespace dimension.label_replace, because PromQL drops empty labels and a missing label inurnTemplateyields an incomplete health state.Identifiers for services without a namespace change from
namespace/defaulttonamespace/; those components are recreated.Tracking: https://github.com/StackVista/stackstate/issues/888
🤖 Generated with Claude Code