# Add\_kubernetes\_metadata does not append kubernetes metadata

**URL:** <https://discuss.elastic.co/t/add-kubernetes-metadata-does-not-append-kubernetes-metadata/167170>\
**Category:** Beats\
**Tags:** heartbeat\
**Created:** [February 5, 2019, 5:44pm UTC](https://discuss.elastic.co/t/add-kubernetes-metadata-does-not-append-kubernetes-metadata/167170 "2019-02-05T17:44:24Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\
**Post date:** [February 7, 2019, 7:02pm UTC](https://discuss.elastic.co/t/add-kubernetes-metadata-does-not-append-kubernetes-metadata/167170/2 "2019-02-07T19:02:56Z")

</div>

I realize this is confusing, but the `add_kubernetes_metadata` processor adds metadata about the pod that heartbeat is running on. Not very useful for your scenario.

Starting in heartbeat 6.7 , when using the heartbeat autodiscovery provider k8s metadata will be added automatically.

Till then, you may want to use a similar approach to [Autodiscover and metadata](https://discuss.elastic.co/t/autodiscover-and-metadata/162980/2?u=andrew_cholakian1)

---

_[View the full topic](https://discuss.elastic.co/t/add-kubernetes-metadata-does-not-append-kubernetes-metadata/167170)._