DEBUG
Alert Details
The Alert Details Page is accessed when a user clicks on a specific alert from the Alert Inbox. This page provides a consolidated view of the alert, with options to investigate, reinvestigate, and analyze detailed diagnostic data.
🔍 What You Can Do on This Page
1. View Investigation Summary
- At the top of the page, users see the results of the most recent investigation.
- This includes:
- Tasks that were automatically or manually performed.
- Agent insights and hypotheses.
- Key metrics or logs analyzed during the process.
2. Reinvestigate (Start Over with Better Context)
- If the user finds the investigation insufficient or inaccurate, they can trigger a Reinvestigation.
- Reinvestigation:
- Re-runs the analysis using the same or improved alert data.
- Users are encouraged to add relevant integrations (e.g., logs, metrics, infra APIs) to enrich context and improve results.
- Can incorporate updated signals or environment state.
💡 Tip: Reinvestigation is most powerful when paired with comprehensive integration coverage.
3. Continue Investigation (Pick Up from Previous Steps)
- Users can choose to Continue Investigation if the existing investigation has helpful partial context.
- Continuing allows:
- Extending the diagnostic trail from the last agent action.
- Adding custom tasks or questions for deeper insights.
- Exploring the reasoning chain of the agent so far.
4. Task Execution View
- Each investigation consists of Tasks — discrete debugging or remediation steps (e.g., querying logs, checking CPU load).
- For each task, users can view:
- Command/query executed.
- Source of data (integration used).
- Agent-generated interpretation or anomaly detection.
- Tasks are grouped and timestamped, helping users track progress.
5. Data & Visualization Panels
- Investigation tasks often return structured data (tables, charts, timelines).
- Users can interact with this data directly in the Alert Details Page:
- View logs, metrics, infra states.
- Expand/inspect anomalies.
- Correlate multiple datasets for better root cause understanding.
🧠 Behind the Scenes
- All investigations (initial, continued, or reinvestigations) are driven by DrDroid’s agentic reasoning engine.
- The agent uses context from the alert metadata (e.g., datasource, affected service, triggering channel) to form hypotheses and take diagnostic steps.
- Users can provide feedback to improve agent understanding and future investigations.