# Metricbeat Kubernetes - limiting information being retrieved

**URL:** <https://discuss.elastic.co/t/metricbeat-kubernetes-limiting-information-being-retrieved/192948>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [July 30, 2019, 4:35pm UTC](https://discuss.elastic.co/t/metricbeat-kubernetes-limiting-information-being-retrieved/192948 "2019-07-30T16:35:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![warnerrj79](https://avatars.discourse-cdn.com/v4/letter/w/ecb155/32.png) [@warnerrj79](https://discuss.elastic.co/u/warnerrj79)\
**Post date:** [July 30, 2019, 4:35pm UTC](https://discuss.elastic.co/t/metricbeat-kubernetes-limiting-information-being-retrieved/192948/1 "2019-07-30T16:35:51Z")

</div>

Hi all. First post here so go easy on me 😉  
I am in the middle of setting up Minikube Kubernetes with ElasticSearch, Kibana and MetricBeat.

I have been successful in setting up all three (with a lot of effort) but have noticed that there is a lot of information being pulled down from MetricBeat. Is there any way I can limit the amount of columns/information in any way (either by internal configuration of by yaml file set up)?

Any questions on this , please let me know.  
Many 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:** [August 27, 2019, 4:35pm UTC](https://discuss.elastic.co/t/metricbeat-kubernetes-limiting-information-being-retrieved/192948/2 "2019-08-27T16:35:53Z")

</div>

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