# Filebeat on Kubernetes, host.name got the pod names (and not the Kubernetes host name ?)

**URL:** https://discuss.elastic.co/t/filebeat-on-kubernetes-host-name-got-the-pod-names-and-not-the-kubernetes-host-name/189951
**Category:** Beats
**Tags:** filebeat
**Created:** [July 11, 2019, 9:19am UTC](https://discuss.elastic.co/t/filebeat-on-kubernetes-host-name-got-the-pod-names-and-not-the-kubernetes-host-name/189951 "2019-07-11T09:19:25Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![fgabolde](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fgabolde/32/50267_2.png) [@fgabolde](https://discuss.elastic.co/u/fgabolde)
#### Post date: [July 19, 2019, 12:25pm UTC](https://discuss.elastic.co/t/filebeat-on-kubernetes-host-name-got-the-pod-names-and-not-the-kubernetes-host-name/189951/3 "2019-07-19T12:25:24Z")

</div>

This is interesting, I've been having a similar issue with `host.name`: [Filebeat adds a host.name field to JSON messages even when already set](https://discuss.elastic.co/t/filebeat-adds-a-host-name-field-to-json-messages-even-when-already-set/190780)

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-on-kubernetes-host-name-got-the-pod-names-and-not-the-kubernetes-host-name/189951)._