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.
Specific links you will want to bookmark for future use
Differentiate between Agent and JVM offline events.
It is not possible to differentiate between a JVM going offline and if there is a communication drop with the Instana agent. This has been discussed with IBM support TS013050872.
Request for service improvement to be able to tell the difference so alerts can be tailored with more accuracy, if the agent disconnects for longer than a given time we recognise this and raise the alert via webhook, and the same with JVM offline.
Atm I am using DFQ to make it possible to detect JVM offline but this also picks up on the agent disconnecting, and so the wording of the event has been changed to "Agent/JVM not Reachable" with instructions to check the JVM first followed by the agent logs.
Do not place IBM confidential, company confidential, or personal information into any field.