Skip to main content
Incident Knowledge groups repeated production detections into reusable patterns. The CLI calls these patterns Error Knowledge Units, or EKUs.
Entelligence product dashboard

Read the dashboard

  • Live detections shows current event volume.
  • Fixes ready shows generated work waiting for review.
  • Patterns learned is the pattern library built from connected sources.
  • Active patterns are still appearing in the selected period.
  • Repository breakdown confirms where sources and patterns are mapped.

Investigate a pattern

  1. Open the repository report and select a pattern.
  2. Check severity, confidence, detection count, and last activity.
  3. Read representative logs and linked source events.
  4. Confirm the repository and service ownership.
  5. Check related incidents, pull requests, tickets, and monitored fixes.
A cluster groups related patterns; it is not automatically one root cause. Use the underlying evidence before treating it as a single failure.

Report tabs

What’s New? shows detections and patterns. Monitored Fixes follows deployed fixes. Risky PRs and Incidents appear when the workspace has qualifying data.

Next step

Continue to Fixes and monitoring or use the incident CLI commands.