Joern Ott

Yes, that is what the check is sending and Icinga is passing to the writer. So I would expect it to handle that value without spamming the logs.

Despite not using elasticsearch::user and elasticsearch::role any more, Puppet still shows an error when building a machine from scratch: `27/11/2018 09:30:03 default: Error: Could not retrieve catalog from remote server:...

We build our own RPMs, accounting for customer specific paths and I encountered the same issue with the systemd file using a hard coded /usr/share/elasticsearch/bin folder. For now, I am...

What stops you from creating releases here on github and attach the files to it?

As my customer an I prefer to distribute software via RPMs instead of tar.gz or zip files, I have created a small build script and SPEC file for the module.

I actually managed to get it back to "online" by just deleting the account and re-adding it.

yep, but 3 years ago, I didn't...

Yes, we are working with Postgresql

The same happens with elasticsearch as well: ``` Fri, 18 Nov 2022 12:55:16 GMT - finest: [telemetry.ElasticSearch.f5telemetry_default::Elasticsearch_cluster] response body: {"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"failed to parse"}],"type":"mapper_parsing_exception","reason":"failed to parse","caused_by":{"type":"illegal_argument_exception","reason":"Limit of total fields [1000] has been...

I am currently working with the data modification feature (see https://clouddocs.f5.com/products/extensions/f5-telemetry-streaming/latest/data-modification.html) to limit the output to the relevant fields. Maybe, that is also a way for you to reduce the...