# Restrict data forwarding to elasticsearch index

**URL:** <https://discuss.elastic.co/t/restrict-data-forwarding-to-elasticsearch-index/216488>\
**Category:** Elasticsearch\
**Created:** [January 24, 2020, 8:43pm UTC](https://discuss.elastic.co/t/restrict-data-forwarding-to-elasticsearch-index/216488 "2020-01-24T20:43:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bhargav](https://avatars.discourse-cdn.com/v4/letter/b/dfb087/32.png) [@bhargav](https://discuss.elastic.co/u/bhargav)\
**Post date:** [January 24, 2020, 8:43pm UTC](https://discuss.elastic.co/t/restrict-data-forwarding-to-elasticsearch-index/216488/1 "2020-01-24T20:43:37Z")

</div>

Greetings,

We are storing logs from some applications in our elasticsearch cluster, and every day we index the data to a new index with increased number in the end of the name.  
E.g.: app-data-0001, app-data-0002 ...

Unfortunately, a person has started forwarding data with same field names but with another field types and that occurs many conflicts in index pattern.

I understand how to fix it, but my question is how to prevent this incidents in future?  
What kind of configurations can I perform to restrict indexing conflicting information?

The data is being sent with beats agents, we are not using ES ingest node or logstash right now.

---

<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:** [February 21, 2020, 8:43pm UTC](https://discuss.elastic.co/t/restrict-data-forwarding-to-elasticsearch-index/216488/2 "2020-02-21T20:43:46Z")

</div>

Closed on February 21, 2020, 8:43pm UTC

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