Philipp Krenn

Just as an idea: Maybe this is going a bit too deep down the rabbit hole for one datastore and it would make more sense to leave that part to...

> If we limit this to hourly indexes, still anyone can use curator or similar to rescale these to daily, weekly monthly.. correct? Not sure I'm reading this correctly, but...

Yes, if you are looking at a short timeframe (like 1h). I'm not sure what the common access pattern is to be honest. On the other hand if you have...

Sounds good on trying it out on a branch. On the re-scaling: Rather than reindexing indices together, you could have an index template with 3 primary shards (just as an...

If Zipkin can write to an alias (without any date math) then you could set that up with with ILM (https://www.elastic.co/guide/en/elasticsearch/reference/current/overview-index-lifecycle-management.html) in the background. That this was part of Zipkin...

Looking at the relevant part of the mapping: "tags" : { "type" : "object", "enabled" : false } I'm afraid [`"enabled" : false`](https://www.elastic.co/guide/en/elasticsearch/reference/7.9/enabled.html) is exactly doing that: > The JSON...

Thanks! I've updated this to the right checkbox list and added references to the upcoming implementation for Kibana and Elasticsearch

The right combination should be the user `elastic` with `password` (from https://github.com/xeraa/vagrant-elastic-stack/blob/master/elastic-stack/vars.yml#L4). Alternatively you could disable security, but with the amount of unsecured public instances I'd be double careful with...

> Only solution is to go OpenSearch now Elastic has sabotaged the Spring Data Elastic Search project by making it unusable for most cases. Elastic has tainted the transitive dependencies...

Unfortunately no. Would still love to use it though...