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.
When using very minimal container images like the distroless, the
hostname
command line tool that our agents use to capture the host name is missing and can't be used.When no value is captured for host name, the most obvious symptom is missing metrics in Kibana, the traces are not impacted.
While the
HOST
andHOSTNAME
environment variables allow to provide a fallback, adding them to very large deployments can become an extra burden.However, reading the content of the
/etc/hostname
is still possible and we should then use it to provide a value to the host name. In this case we don't know if a simple host name or an FQDN is provided.In containers the actual value is usually the container ID or a random string thus it's not for "human consumption" but is still relevant for correlation.
In short, this just adds an extra fallback option to existing heuristics.
CODEOWNERS
)To auto-merge the PR, add
/
schedule YYYY-MM-DD
to the PR description.If this spec adds a new dynamic config option, add it to central config.n/a