# How to get host.name reporting uniformity?

**URL:** <https://discuss.elastic.co/t/how-to-get-host-name-reporting-uniformity/373953>\
**Category:** Elastic Agent\
**Created:** [January 31, 2025, 3:37pm UTC](https://discuss.elastic.co/t/how-to-get-host-name-reporting-uniformity/373953 "2025-01-31T15:37:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![catn0b0t](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/catn0b0t/32/122758_2.png) [@catn0b0t](https://discuss.elastic.co/u/catn0b0t)\
**Post date:** [January 31, 2025, 3:37pm UTC](https://discuss.elastic.co/t/how-to-get-host-name-reporting-uniformity/373953/1 "2025-01-31T15:37:23Z")

</div>

We see a lot of variation in how different fleet agent integrations report the hostname. Although we have configured our agent policies to report the FQDN. Some integrations still just report the hostname instead of the FQDN, and some integrations even don't report a hostname at all, for example the RabbitMQ log integration, it only reports the agent.name.  
Would be great to see some standardization in that field to increase data quality.

---

<div class="post-metadata">

**Author:** ![willemdh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/willemdh/32/16922_2.png) [@willemdh](https://discuss.elastic.co/u/willemdh)\
**Post date:** [January 31, 2025, 5:50pm UTC](https://discuss.elastic.co/t/how-to-get-host-name-reporting-uniformity/373953/2 "2025-01-31T17:50:34Z")

</div>

I completely agree on this. Lowercase fqdn is the best key imho, so we also configured our agent policies to report the FQDN. Otherwise your host names can get into conflict with identically named hosts from test domains or other networks. The original hostname should be in host.hostname.  
ECS also recommends lowercasae FQDN =\> [Host Fields | Elastic Common Schema (ECS) Reference [8.17] | Elastic](https://www.elastic.co/guide/en/ecs/current/ecs-host.html#field-host-name)