Restrict data forwarding to elasticsearch index


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.

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