| 1 | # SIEM |
| 2 | |
| 3 | **Menu:** SIEM → Alerts |
| 4 | |
| 5 | **Best for:** Both |
| 6 | |
| 7 | This page shows a **high-level view of SIEM alerts** based on what **Graylog** indicates (using the filters on the page). |
| 8 | |
| 9 | Important: |
| 10 | - These are **different from Incident Management alerts**. |
| 11 | - SIEM alerts shown here are **not created/managed** in CoPilot’s Incident Management queue. |
| 12 | |
| 13 | Use this page for: |
| 14 | - a quick overview of alert volume and themes |
| 15 | - validating that Graylog alerting is working |
| 16 | - validating that alerts configured in Graylog are flowing into **Incident Management** when expected |
| 17 | |
| 18 | It is **not** intended to be the primary analyst workflow surface for alert handling. |
| 19 | |
| 20 |  |
| 21 | |
| 22 | --- |
| 23 | |
| 24 | ## How to use it (practical) |
| 25 | |
| 26 | 1) Apply your filters (customer/time window/stream/etc.) |
| 27 | 2) Confirm Graylog is producing the alerts you expect |
| 28 | 3) Pick an alert and pivot to underlying SIEM events (when available) |
| 29 | 4) Cross-check whether a corresponding Incident Management alert exists (if your routing/provisioning is configured to create one) |
| 30 | |
| 31 | --- |
| 32 | |
| 33 | ## Gotchas |
| 34 | |
| 35 | - If you see SIEM alerts here but not in Incident Management, it usually indicates an ingestion/routing gap (Graylog event definition/stream → CoPilot incident ingestion). |
| 36 | - If you only need the analyst queue, go to: [Incident alerts](/user/ui/incident-alerts) |