# Filebeat Cisco AMP Module and host.name Error

**URL:** <https://discuss.elastic.co/t/filebeat-cisco-amp-module-and-host-name-error/268510>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [March 26, 2021, 2:49pm UTC](https://discuss.elastic.co/t/filebeat-cisco-amp-module-and-host-name-error/268510 "2021-03-26T14:49:46Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![Marius\_Iversen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_iversen/32/68988_2.png) [@Marius\_Iversen](https://discuss.elastic.co/u/Marius_Iversen)\
**Post date:** [March 29, 2021, 8:31pm UTC](https://discuss.elastic.co/t/filebeat-cisco-amp-module-and-host-name-error/268510/21 "2021-03-29T20:31:35Z")

</div>

The discussion around host.hostname and host.name is a hard one, since in theory they can both be the same. I know there is some ongoing ECS discussions around that subject.

I will take a look tomorrow to see if there is a inconsistency between this one and the other security related modules.

For user.name, are you talking about the SIEM dashboards or specific custom dashboards? I think its usually either source/destination/host.user, but I can give that a check as well, will note down the feedback and make sure I will give it a lookover 🙂

In the meantime you would unfortunately have to either modify the ingest pipeline, or setup a override pipeline on your specific index: [Index modules | Elasticsearch Reference [master] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/master/index-modules.html#index-final-pipeline)

---

<div class="post-metadata">

**Author:** ![MakoWish](https://avatars.discourse-cdn.com/v4/letter/m/e56c9b/32.png) [@MakoWish](https://discuss.elastic.co/u/MakoWish)\
**Post date:** [March 30, 2021, 2:21pm UTC](https://discuss.elastic.co/t/filebeat-cisco-amp-module-and-host-name-error/268510/22 "2021-03-30T14:21:22Z")

</div>

For the user name, Winlogbeat and Auditbeat events utilize `user.name`, so I also continued with that theme for our custom sources. I was talking about custom dashboards we have that give high level views of user or computer activity. If you click a `user.name` field, or a `computer.name` field from anywhere in the platform, it takes you to a dashboard that shows activity for that specific user or computer from all our event sources (AD, A/V, DLP, NGFW, IDS, etc.). Standardizing `host.name` and `user.name` is necessary for that sort of correlation to work properly.

Thank you, @Marius_Iversen ! I appreciate your insight and help with this. As you mentioned, I will just tweak the pipeline a bit for now. 🙂 👍

---

<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:** [April 27, 2021, 4:22pm UTC](https://discuss.elastic.co/t/filebeat-cisco-amp-module-and-host-name-error/268510/23 "2021-04-27T16:22:22Z")

</div>

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

[Previous page](https://discuss.elastic.co/t/filebeat-cisco-amp-module-and-host-name-error/268510.md?page=1)