-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
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
host.name
assigned with pod.name
#1636
Comments
I'm not seeing anything that sets |
The same node is running auditbeat and packetbeat. packetbeat reports the correct host name, auditbeat doesn't. I can't find what is different between the two that causes this. Both are running the same go agent version |
The go agent doesn't set the https://www.elastic.co/guide/en/apm/agent/go/current/configuration.html#config-hostname describes how a host name can be configured via the go agent. You'll need to check the setup of the instrumented services as to which configurations they have set. |
I had a quick call with @Mpdreamz , and he explained that the non-matching host names shipped by APM agents are due to missing configuration as exemplified in this comment https://github.com/elastic/observability-dev/issues/3321#issuecomment-2236909682. |
Describe the bug
When viewing the Hosts UI with Go APM service active in a k8s pod, Go agent monitored services report the pod name in the
host.name
, which makes the Hosts View display hosts that do not correlate with hosts monitored by the system integration.Steps to reproduce
edge-oblt can be used for the above.
Expected behavior
Only hosts (VMs) are expected to be present in the Hosts View.
Additional context
Sample doc
The text was updated successfully, but these errors were encountered: