Is there a way to clean .kibana* indices? I got 22 of them!

I'm running a cluster on Elastic Cloud, in which I have 3 index.

But my cluster is also filled with plenty of "system indices" I never really wanted:


I don't have Fleet, I don't have APM, and most of these indices are empty. But still they all assign shards and consume CPU/RAM.

As we are not supposed to delete system indices, my question are:

  • can we have a description on each system index? Like in the "_meta" field that would be awesome;
  • is there a way to clean things up? I only need the .kibana index in my opinion;
  • should I stop upgrading versions to avoid new system indices :grimacing:


Related to Kibana system indices

EDIT : I see there is a plan to "hide" thoses indices: but still, I feel like there is too much indices here.

1 Like

Why do you want to remove these indices? Do you believe them to be causing you performance issues? Or is it the "clutter" in e.g. lists of indices on system that concerns you?

We have spent a long time telling users to reduce shard count, yet there's all these system ones with nothing in then, with no use, that we're auto-creating. I think this is a reasonable basis for wanting these removed.

1 Like

I had many of this since 7.2 and all the upgrade till 7.15.1 that I apply.

just nuke them. it does not used if you do not have any of that version install. I remove all them last week.

make sure you don't delete latest one or you are doomed.
Also do not remove .kibana, .security, .tasks etc... which are alias

you can check by just printing all aliases

GET /_cat/aliases?v

1 Like

Like @warkolm said, yes it feels like my cluster is dirty: lots of indices / shards with no use.

I'm indeed worried about performance and resources wasted (RAM, file descriptor, CPU...).

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