2026-04-22 13:39:35 +02:00
|
|
|
- [Go client docs](https://www.elastic.co/docs/reference/elasticsearch/clients/go/typed-api)
|
|
|
|
|
- [ES API docs](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-get)
|
2026-04-29 13:44:21 +02:00
|
|
|
|
2026-05-13 13:51:09 +02:00
|
|
|
- index show: add more details, see screenshots
|
2026-05-18 12:19:45 +02:00
|
|
|
|
2026-06-03 13:13:44 +02:00
|
|
|
- add datastream support:
|
|
|
|
|
https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-get-data-stream
|
|
|
|
|
|
2026-07-17 08:55:48 +02:00
|
|
|
- Fix: cluster status word wrapping adds one \n to much:
|
|
|
|
|
|
|
|
|
|
```console
|
|
|
|
|
Bad health shards_availability This cluster has 1 unavailable replica shard.
|
|
|
|
|
-> cause Elasticsearch isn't allowed to allocate some shards from these indices to any of the nodes in the
|
|
|
|
|
|
|
|
|
|
cluster.
|
|
|
|
|
-> affected indices foo-t-log-logs-002947
|
|
|
|
|
-> suggested action to fix Diagnose the issue by calling the allocation explain API for an index [GET
|
|
|
|
|
|
|
|
|
|
_cluster/allocation/explain]. Choose a node to which you expect a shard to be allocated, find this
|
|
|
|
|
|
|
|
|
|
node in the node-by-node explanation, and address the reasons which prevent Elasticsearch from
|
|
|
|
|
```
|
|
|
|
|
|
