# Kibana Infrastructure UI shows no metrics for hosts or kubernetes pods

**URL:** <https://discuss.elastic.co/t/kibana-infrastructure-ui-shows-no-metrics-for-hosts-or-kubernetes-pods/184216>\
**Category:** Metrics\
**Created:** [June 4, 2019, 3:10pm UTC](https://discuss.elastic.co/t/kibana-infrastructure-ui-shows-no-metrics-for-hosts-or-kubernetes-pods/184216 "2019-06-04T15:10:31Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![zx10r](https://avatars.discourse-cdn.com/v4/letter/z/a587f6/32.png) [@zx10r](https://discuss.elastic.co/u/zx10r)\
**Post date:** [June 4, 2019, 7:11pm UTC](https://discuss.elastic.co/t/kibana-infrastructure-ui-shows-no-metrics-for-hosts-or-kubernetes-pods/184216/3 "2019-06-04T19:11:40Z")

</div>

@simianhacker so i seem to have found the problem and it was not due to metricbeat but rather filebeat somehow affecting the infrastructure UI when going to metrics view. Both filebeat and metricbeat are running in kubernetes and have the - add\_kubernetes\_metadata: flag enabled.

Once i go into the Infrastructure UI and update the Log Indices source that points to something other than filebeat (some index that doesnt exist) everything works. I do want to note that filebeat outputs to logstash and logstash to ES.

But why would the Log Indices source cause the metrics to now show up? Is there some conflict that both metricbeat and filebeat both have add\_kubernetes\_metadata: flag enabled?

---

_[View the full topic](https://discuss.elastic.co/t/kibana-infrastructure-ui-shows-no-metrics-for-hosts-or-kubernetes-pods/184216)._