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
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)
The Unbounded Analytics is operating on the data-set that's in the data-store for the selected timeframe. When the timeframe is outside of the (full-granularity) short term window that is defined in the self-hosted configuration the results are imprecise. In that case we display an indicator in UA and/or the timeframe selector to make clear that the results are not precise. This means that the saved data is no longer representing the real data and while we state we save 1% of data this is 1% of the whole data and not 1% of the data per service.
There are multiple approaches how to continue:
increase the data retention period so that it covers the period you want to analyze. Please be aware that this will increase the utilization of the compute and storage resources. => Knowing your OnPrem physical hardware resources are exhaused this is a no-go... create daily API calls to retrieve the real numbers reading the explanation above and following our joint analysis we found and concluded that the data not in retention timeframe is very close to the real number. It would therefore be an option to run an API call retrieving the count allowing you to compare this number for covering the use-case enhance the Instana product for this use-case while from customer perspective this will be the most desired one the complexity of building this into the Instana architecture will be huge... Reason being that all calls are tagged with data not resulting in a typical timeseries metric data we want to maintain but a highly complex multi-dimensional dataset needing high velocity calculation and costing more resources and performance for realisation... => We will keep this item on our radar and re-evaluate options during 2022 when our own histogram based new metric store is further adopted into the product looking at options if this can address the use-case
For now we advice to consider option 2 until further notice. In the meanwhile we will be moving this ticket to a feature request for future tracking.
Do not place IBM confidential, company confidential, or personal information into any field.