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.
Hi Rainer, thanks for the explanation.
I see this going into 2 direction: for our Alerting, we assess if a more global approach makes sense. On the other side, those entities should not trigger offline events, if the JVMs are actually still online. I'd like to investigate this a bit more.
Can you file a ticket with our support and have this investigated? Please put in the link to this idea and also my name. Either this can be resolved by configuration, or the engineering team needs to have a deeper look.
Thanks & kind regards
Henning
Hi Henning,
The problem is that we see offline events but in reality the JVM is online. Healtchecks show the JVM is still responding. Due to this problem, the customer has now decided not to let Instana trigger alerts towards Service Now anymore. The original idea was to link several events with AND to make the whole thing more secure. For example, an offline event of the JVM AND a health check or some other metric that shows whether the JVM is still running. The current approach in the new release is not bad, but only makes this possible on the level of the same entity. I can imagine that opening the whole thing up and allowing different entities will make events more comfortable. In this way, some of the build-in events could certainly be better readjusted if the default settings do not fit.
Best regards
Rainer
Hi Rainer,
exploring your statement "agent updates ... lead to the agents being switched offline in extreme cases" a little further: what are these extreme cases and why will the agent be switched offline? In Addition, when this happens, is it an event where you don't want an alert to be fired to resol;ve the "agent down" situation?
Thanks & best
Henning Treu - Product Manager Instana Agent & Application Perspectives