# Elastic SIEM Alert hostname missing

**URL:** <https://discuss.elastic.co/t/elastic-siem-alert-hostname-missing/376858>\
**Category:** SIEM\
**Created:** [April 7, 2025, 10:09am UTC](https://discuss.elastic.co/t/elastic-siem-alert-hostname-missing/376858 "2025-04-07T10:09:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![axvfvv79zcx57xv7k](https://avatars.discourse-cdn.com/v4/letter/a/2bfe46/32.png) [@axvfvv79zcx57xv7k](https://discuss.elastic.co/u/axvfvv79zcx57xv7k)\
**Post date:** [April 7, 2025, 10:09am UTC](https://discuss.elastic.co/t/elastic-siem-alert-hostname-missing/376858/1 "2025-04-07T10:09:16Z")

</div>

Hello,

I'm currently using Elastic SIEM and trying to troubleshoot an issue regarding some detection rules. For several rules — for example, "Unusual File Transfer Utility Launched" (which monitors tools like rsync, scp, etc.) — the field host.name (or hostname) is missing in the alert document, even though it appears correctly for other rules.

This is a problem for me because I have multiple VMs with Elastic agents deployed, and without host.name, I can't easily determine which system triggered the alert. In such cases, the rule becomes difficult to act upon.

![grafik](https://us1.discourse-cdn.com/elastic/optimized/3X/7/1/71320a668feb07d74037b7fa94c00bfd43f31fbe_2_690x37.png)

Am I missing a configuration or mapping step?  
Any insight would be greatly appreciated — thanks in advance!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 5, 2025, 10:10am UTC](https://discuss.elastic.co/t/elastic-siem-alert-hostname-missing/376858/2 "2025-05-05T10:10:15Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.