[host] stabilize host.id definition#3916
Conversation
Pull request dashboard statusStatus last refreshed: 2026-07-25 20:02:13 UTC.
This automated status or its linked feedback items may be incorrect. If something looks wrong, please report it with the result you expected. If you believe this pull request is incorrectly routed as waiting on the author, comment |
There was a problem hiding this comment.
Pull request overview
This PR updates the OpenTelemetry host semantic conventions to make host.id more deterministic and explainable by defining a detector priority order, enumerating currently recognized (cloud) environments, and documenting fallback expectations when automatic detection is not possible.
Changes:
- Reworked the
host.iddefinition to be based on a priority-ordered set of sources rather than a single OS-specific rule. - Added explicit guidance on recognized cloud environments and on how to treat user-provided
host.idwhen automatic detection fails. - Regenerated the rendered host resource documentation and added a changelog entry.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| model/host/registry.yaml | Updates the host.id attribute brief to reference priority-based resolution. |
| model/host/entities.yaml | Adds detailed normative guidance for host.id detector priority, recognized environments, and fallback behavior. |
| docs/resource/host.md | Regenerated docs reflecting the updated host.id definition and host entity note. |
| .chloggen/stabilize-host-id-definition.yaml | Adds a release-note entry for the host.id definition stabilization work. |
Define an explicit priority order for host.id sources (cloud provider, VM vendor, OS machine-id, user-provided fallback), list the currently recognized cloud/VM environments paired with their cloud.provider and cloud.platform values for disambiguation, and clean up wording around machine-id lookup and the user-configured fallback properties.
d0e9417 to
704712d
Compare
lmolkova
moved this from Untriaged
to Needs More Approval
in Semantic Conventions Triage
Fixes #3897
Changes
host.idvalue lookup.host.idsource is determined).host.idproperties for fallback cases. Added an explicit call for the user to providehost.id(or make it discoverable in other way) when no standard detectors worked.Merge requirement checklist
Footnotes
Yes, I can answer maintainer questions about the content of this PR without using AI. ↩