Since a couple of weeks we have some Elastic-Instances on which we did not get any statsd-Messages into ElasticSearch. All this Messages end with:
{"type":"illegal_argument_exception","reason":"Rejecting mapping update to [statsd-6.3.3-2020.11.23] as the final mapping would have more than 1 type: [_doc, doc]"}
We have made no changes on purpose since around 1 Year or so.
Any Ideas? Even how we can try to find the cause or a work-a-round?
ELS: 7.4.2
Statsdbeat: 6.3.3
OS: Amazon Linux
Since a couple of weeks we have some Elastic-Instances on which we did not get any statsd-Messages into ElasticSearch. All this Messages end with:
{"type":"illegal_argument_exception","reason":"Rejecting mapping update to [statsd-6.3.3-2020.11.23] as the final mapping would have more than 1 type: [_doc, doc]"}We have made no changes on purpose since around 1 Year or so.
Any Ideas? Even how we can try to find the cause or a work-a-round?
ELS: 7.4.2
Statsdbeat: 6.3.3
OS: Amazon Linux