Repository navigation
Name the machine: host.name and host.arch on the resource - #63
Merged
Merged
Conversation
Detection covered container, Kubernetes and cloud identity but never the host itself, so a plain VM or bare-metal box — the most common self-hosted deployment there is — reported nothing that ties a request to the machine that served it. Anything reading that host's own exporters had nothing to join on. Inside a container the hostname is the container, which is the right answer from the process's point of view; a Kubernetes operator whose node name differs substitutes it through OTEL_RESOURCE_ATTRIBUTES, which is merged last and wins. host.arch is spelled the way the semantic conventions do, amd64 and arm64 rather than the kernel's names.
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
1 participant
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.
Resource detection covered container, Kubernetes and cloud identity but never the host itself. On a plain VM or bare-metal box — the most common self-hosted deployment — nothing on the trace says which machine served the request, so anything reading that host's own exporters (node_exporter, a health endpoint) has nothing to join on.
Found while wiring infrastructure discovery in
laravel-telemetry-ui: the host-side context could not work against a real stack because the traces carried nohost.name.Inside a container the hostname is the container, which is the right answer from the process's point of view and is already recorded separately as
k8s.pod.namewhere it applies. An operator whose node name differs substitutes it throughOTEL_RESOURCE_ATTRIBUTES, which is merged last and wins — there is a test for that.host.archis normalised to the semantic conventions' spelling (amd64,arm64) rather than the kernel'sx86_64/aarch64.804 tests.