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.
Since the agent needs to communicate to the backend, once the heartbeats stop, there is no way for us to know why the communication stopped.
Even competitors can only make assumptions. In most enterprise environments pings are disabled for external connections, so pretty complicated logic would need to be implemented for another in-network agent to try to check the availability of the machine where the agent is no longer responding.
Since these cases are fully transparent for our backend, we cannot reliably differentiate between the listed cases.
Similarly, how would Instana backend know that the agent process is running, if it is not communicating?
For this reason we intentionally defined the issue as Agent offline, since all we can know, is that it is no longer emitting the heartbeats.