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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
IBM Turbonomic ARM
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
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.
Do not place IBM confidential, company confidential, or personal information into any field.