Skip to Main Content
Cloud and AIOps


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).

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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

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.

Status Not under consideration
Workspace Instana
Categories Agent Alert
Created by Guest
Created on Jun 10, 2026

Smart Root Cause Detection for "Agent Not Reporting" Events

## Executive Summary (Elevator Pitch)

 

The current "Instana Agent not reporting" event doesn't differentiate between network issues, host failures, or agent process problems. During network incidents, this creates alert storms with hundreds of identical incidents, making it impossible to quickly identify the root cause. We need intelligent event classification similar to Dynatrace, New Relic, and Datadog to distinguish between network, host, and agent-level failures.

 

## Problem Statement

### Current Situation

When agents stop reporting, Instana generates a single event type: **"Instana Agent not reporting"**

 This same event is triggered for completely different scenarios:

1. **Network Issues**: DNS resolution failure, network path disruption, firewall blocking

2. **Agent Process Down**: Service stopped, process crashed, configuration error

3. **Host/Infrastructure Down**: Server powered off, OS crash, interface down

 

### Real-World Impact

During a recent network incident, we received **500+ identical "Agent not reporting" incidents**:

- ❌ No indication it was a network-wide issue

- ❌ Teams wasted time investigating individual hosts

- ❌ Actual root cause (network) took much longer to identify

- ❌ Increased MTTR (Mean Time To Resolution)

- ❌ Alert fatigue and operational inefficiency

 

### Business Impact

- **Operational Cost**: Teams investigating wrong layer (application vs network vs host)

- **Delayed Resolution**: Cannot quickly identify if it's a single host issue or infrastructure-wide problem

- **Alert Fatigue**: Mass incidents during network issues reduce team responsiveness

- **Competitive Gap**: Other APM solutions already solve this problem

 

## Proposed Solution

 ### Option 1: Enhanced Event Classification (Minimum Viable)

Create distinct event types based on root cause:

✅ "Network Connectivity Issue" - Cannot reach host network

✅ "Host Not Reachable" - Network OK, but host not responding

✅ "Agent Process Not Running" - Host OK, but agent process down

✅ "Agent Communication Failure" - Process running, but cannot communicate

### Industry References

- Dynatrace Davis AI: https://www.dynatrace.com/platform/artificial-intelligence/

- New Relic Infrastructure Monitoring: https://docs.newrelic.com/docs/infrastructure/

- Datadog Network Monitoring: https://docs.datadoghq.com/network_monitoring/

- AppDynamics Health Rules: https://docs.appdynamics.com/appd/24.x/latest/en/application-monitoring/configure-monitoring/health-rules

Idea priority High
  • Admin
    Máté Návay
    Aug 5, 2026

    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.