topic Re: Logs from AWS hosts having the EC2 instance id as host.name in Cloud platforms

Logs from AWS hosts having the EC2 instance id as host.name

dannemca — Tue, 20 Aug 2024 12:45:39 GMT

Hi team, good day.

Since few time ago (I don't know exactly when it started) our logs ingested automatically from OneAgents in AWS are receiving the EC2 instance id value as the host.name field value.

When we check the host name in the Host page, the metadata values are just fine. Host name, detected name all matches.

The "problem" is only on the logs. The field host.name is exactly the same as the aws.resource.id.

We see the host name as it should be in the field dt.entity.host, but that's only a "live translation" Dynatrace does, since in reality the field value is the Host ID (HOST-XYZ0123...).

So, our big issue here is, we can't filter the logs by host name, nor having the host name as a dimension for metrics, since the values captured are not the "human readable" format.

Is anyone here facing the same?

Re: Logs from AWS hosts having the EC2 instance id as host.name

sivart_89 — Sun, 08 Sep 2024 15:45:21 GMT

I noticed this after deploying new EC2s, ones with a different ami than what we have in our prod environment. We are using ami-066784287e358dad1 for nonprod and ami-01cc34ab2709337aa for prod. I'm wondering if you are in the same situation, where maybe it is showing correctly with one ami but not for another.

Re: Logs from AWS hosts having the EC2 instance id as host.name

Shirai — Thu, 26 Sep 2024 02:59:53 GMT

I am facing the same problem. AWS EC2 Log and event shows Instance ID in host.name. VM ware built host shows Detected name(Host name).

Re: Logs from AWS hosts having the EC2 instance id as host.name

dannemca — Thu, 26 Sep 2024 12:27:59 GMT

This is now fixed, after the OneAgent 1.299 update.

There is no mention on the release notes, but I had informed by support team that this was the version that contains this fix.

Re: Logs from AWS hosts having the EC2 instance id as host.name

sivart_89 — Thu, 26 Sep 2024 12:55:24 GMT

Thank you @dannemca for the update. Checking in our env after a recent agent upgrade I see the issue fixed as well although it is frustrating nothing is mentioned in the release notes