Keep your security signal healthy
Start with the suggested fix in the console. Use these guides when you need to investigate a specific part of the path.
| What you see | Start here |
|---|---|
| A machine has stopped reporting | Fleet view and source silence |
| Events are waiting in the queue | Fleet and queue integrity |
| The test event is not found in Sentinel | Doctor and DCR checks, then evidence bundles |
| A repeated event conflicts with an existing one | Event identity conflicts |
| You need to see a protected event moving through the collector | Tap and top |
| A maintenance job needs attention | Background jobs |
| You need scripted management | PowerShell |
Preserve the evidence
Do not delete queue files to clear a warning. Keep acknowledgement and cursor state intact. Follow the recovery guidance in queue durability and fleet and queue integrity.
Console screenshots in these guides use synthetic preview data. A screenshot is not evidence that your deployment has delivered an event.