# Limiting index creation - where to set values?

**URL:** <https://discuss.elastic.co/t/limiting-index-creation-where-to-set-values/150485>\
**Category:** Logstash\
**Created:** [September 30, 2018, 7:04pm UTC](https://discuss.elastic.co/t/limiting-index-creation-where-to-set-values/150485 "2018-09-30T19:04:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ethrbunny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ethrbunny/32/34603_2.png) [@ethrbunny](https://discuss.elastic.co/u/ethrbunny)\
**Post date:** [September 30, 2018, 7:04pm UTC](https://discuss.elastic.co/t/limiting-index-creation-where-to-set-values/150485/1 "2018-09-30T19:04:34Z")

</div>

One of my indexes is hitting the "1000 fields" limit pretty regularly and I'd like to calm it down a bit.

I've seen [this](https://www.elastic.co/guide/en/elasticsearch/reference/6.3/mapping.html) information but I can't figure out how to set these values.

Oddly enough (to me) when i go to Kibana and look at the "management" / "index patterns" page the index that's suffering reports 615 fields. There are others with many more (\> 800).

Do I need to filter out my outputs better (via logstash) and create more separated index patterns? At present I have only a minimal set (all updated daily): filebeat, metricbeat, auditd, collectd and docker.

Collectd is the unhappy lot. It's used to gather JMX data from kafka and cassandra. Perhaps it's nested too deeply?

---

<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:** [October 28, 2018, 7:04pm UTC](https://discuss.elastic.co/t/limiting-index-creation-where-to-set-values/150485/2 "2018-10-28T19:04:41Z")

</div>

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