We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
detected_hostname
See meta issue and spec for the description and details:
The spec PR: elastic/apm#805
The text was updated successfully, but these errors were encountered:
If/when doing this, we should consider finding doing the detected_hostname update for the Node.js agent as well, to conform to https://github.com/elastic/apm/blob/main/specs/agents/metadata.md#hostname (spec PR/discussion: elastic/apm#517)
Sorry, something went wrong.
Some impl notes from Steve:
FYI - I looked into the source for the .NET APIs I plan to use to collect the detected_host_name to see how they are implemented. On Windows it calls down into the native IpHlpApi, collecting what it needs from FIXED_INFO. On Linux-based operating systems it calls into getdomainname (see https://man7.org/linux/man-pages/man2/getdomainname.2.html) and falls back to uname.
host.domain
feat!: metadata.system.{configured_hostname,detected_hostname}, prefe…
13641c8
…r FQDN Refs: elastic/apm-agent-nodejs#3310
a90fe47
…r FQDN (#200) This also adds testing of node v20 and testing on windows (just one node version). Refs: elastic/apm-agent-nodejs#3310
trentm
Successfully merging a pull request may close this issue.
See meta issue and spec for the description and details:
detected_hostname
apm#793detected_hostname
apm#794The spec PR: elastic/apm#805
The text was updated successfully, but these errors were encountered: