Incidents Not Appearing

Cluster is not connected

Incidents are only created for connected clusters. Go to Settings → Clusters and verify the cluster shows Connected.

If the cluster is disconnected, see Agent not connecting.

Analysis hasn’t run yet

The first analysis runs within 5 minutes of the agent connecting. Subsequent analyses run every 5 minutes.

If you just connected the cluster, wait up to 5 minutes for the first results.

Condition is within the suppression window

Transient conditions are suppressed to reduce noise. If the issue resolved itself quickly (within the suppression window), no incident is created.

If the condition is ongoing and still not appearing after 10 minutes, contact support.

Condition is not covered by K8sGPT analyzers

DataAgent detects conditions that K8sGPT can observe via the Kubernetes API. Some conditions are not detectable:

• Application-level errors not reflected in pod status or events
• Conditions inside custom resources without a K8sGPT analyzer
• Network-level issues not visible to the Kubernetes API

The incident was auto-resolved

If the condition was previously detected but fixed, the incident may have been auto-resolved. Check the Resolved filter in the Incidents view for recent resolutions.

You are filtering it out

Check the active filters in the Incidents view. The severity filter, cluster filter, or status filter may be hiding the incident. Click Clear filters to reset.