Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Workspace Instana
Categories Metric Store
Created by Guest
Created on Oct 14, 2022

Implement ElasticSearch Index Rotation

Currently there is no mechanism to clean up ElasticSearch Indices. That means the grow infinitely and searches will slow down. IBM provides scripts to clean up this indices with the delete_by_query api which deletes all documents older than a specified time. This has some disadvantages i have to do this regularly and have to set up an automation to do this. Moreover, ElasticSearch does not reclaim the space because it only marks the documents as deleted (https://www.elastic.co/de/blog/lucenes-handling-of-deleted-documents). Furthermore, when i want more shards for an certain index i have to split and clone them with index rotation in place i would just adjust the number of shard for an "index set" and new indices will be created with this number of shard and the older ones will be deleted after some time.


Graylog is doing this already with the index sets feature (https://docs.graylog.org/docs/index-model). We realy like their implementation because you get more control of your data. It would be helpful to get such a feature for instana as well.

Idea priority High
  • Guest
    Reply
    |
    Feb 9, 2023

    Hey Edwin,

    thank you very much! Do you have any documentation for this?

  • Guest
    Reply
    |
    Feb 8, 2023

    The Instana Infrastructure team has delivered capability to manage Elasticsearch Indices natively. This capability is available for use now.