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

**URL:** <https://community.dynatrace.com/t/logs-from-aws-hosts-having-the-ec2-instance-id-as-host-name/47098>\
**Category:** Cloud platforms\
**Tags:** aws, logs\
**Created:** [August 9, 2024, 3:40pm UTC](https://community.dynatrace.com/t/logs-from-aws-hosts-having-the-ec2-instance-id-as-host-name/47098 "2024-08-09T15:40:18Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dannemca](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/dannemca/32/7215_2.png) [@dannemca](https://community.dynatrace.com/u/dannemca)\
**Post date:** [August 9, 2024, 3:40pm UTC](https://community.dynatrace.com/t/logs-from-aws-hosts-having-the-ec2-instance-id-as-host-name/47098/1 "2024-08-09T15:40:18Z")

</div>

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?

 ![image (69).png](https://global.discourse-cdn.com/dynatrace/original/3X/c/1/c17984a7c349e3ae76aeef09f4f8828f74a7669f.png)

 ![image (68).png](https://global.discourse-cdn.com/dynatrace/original/3X/9/d/9d387d08ac81dd285bbe3907c76d4ad8ea4facc3.png)

 ![image (67).png](https://global.discourse-cdn.com/dynatrace/original/1X/e07efcf62a893404ec30626a3c1f21c6f43ffacc.png)

---

<div class="post-metadata">

**Author:** ![sivart\_89](https://avatars.discourse-cdn.com/v4/letter/s/848f3c/32.png) [@sivart\_89](https://community.dynatrace.com/u/sivart_89)\
**Post date:** [September 8, 2024, 3:45pm UTC](https://community.dynatrace.com/t/logs-from-aws-hosts-having-the-ec2-instance-id-as-host-name/47098/2 "2024-09-08T15:45:21Z")

</div>

I noticed this after deploying new EC2s, ones with a different ami than what we have in our prod environment. We are using&nbsp;ami-066784287e358dad1 for nonprod and&nbsp;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.

---

<div class="post-metadata">

**Author:** ![Shirai](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/shirai/32/27711_2.png) [@Shirai](https://community.dynatrace.com/u/Shirai)\
**Post date:** [September 26, 2024, 2:59am UTC](https://community.dynatrace.com/t/logs-from-aws-hosts-having-the-ec2-instance-id-as-host-name/47098/3 "2024-09-26T02:59:53Z")

</div>

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).

---

<div class="post-metadata">

**Author:** ![dannemca](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/dannemca/32/7215_2.png) [@dannemca](https://community.dynatrace.com/u/dannemca)\
**Post date:** [September 26, 2024, 12:27pm UTC](https://community.dynatrace.com/t/logs-from-aws-hosts-having-the-ec2-instance-id-as-host-name/47098/4 "2024-09-26T12:27:59Z")

</div>

This is now fixed, after the OneAgent 1.299 update.

There is no mention on the [release notes](https://docs.dynatrace.com/docs/whats-new/release-notes/oneagent/sprint-299), but I had informed by support team that this was the version that contains this fix.

---

<div class="post-metadata">

**Author:** ![sivart\_89](https://avatars.discourse-cdn.com/v4/letter/s/848f3c/32.png) [@sivart\_89](https://community.dynatrace.com/u/sivart_89)\
**Post date:** [September 26, 2024, 12:55pm UTC](https://community.dynatrace.com/t/logs-from-aws-hosts-having-the-ec2-instance-id-as-host-name/47098/5 "2024-09-26T12:55:24Z")

</div>

Thank you&nbsp;[@dannemca](https://community.dynatrace.com/user/18264)&nbsp;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
