This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
As discussed with Martin Fuentes, IBM Instana Product Management, we want to address and support this FR as per our detailed business needs
Detail top level business case
Monitoring MOVAS services is important to the Application Manager, especially for identifying services that are recognized by the platform but are no longer running or no longer receiving calls.
The goal is to support the Monitoring and Reporting on the LifeCycle of Services deployed for and operating under the Business Plattform MoVAS, through autonomous Teams.
Idle Services or Services without any calls over a selected timeframe must be swiftly identified and reported to the relevant Ops Teams for appropriate measures.
However, manual monitoring of idle services in Instana is time-consuming and error-prone.
The obstacles to the Automation of Idle Service Monitoring are as follows:
Query-based Analysis of Service idleness is not possible, as the 0-calls results are curtailed by design on the Analytics View.
Alerting is not possible, as a calls.sum of 0 is not returned by the alerting configuration.
Service idleness cannot be displayed on a Custom Dashboard in Instana, as the query framework does not support a calls Count.
No external data Analysis tool can be used to assess calls data, as the Instana API qqueries do not include Services with 0 calls in the Response Body.
Conclusion
Currently the transparency and traceability of existing services (without current request use) within Instana is questionable
Hi there, is there any update on this FR?
Thanksfully FR is under review for a while now ... is there an update -> Our Business Case to query and report also services currently not in use