> ## Documentation Index
> Fetch the complete documentation index at: https://docs.insaion.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Incidents

## Incident History

The Incident History page gives you a clear, chronological view of incidents raised by your alarm rules. It’s designed to help you triage issues quickly, see which alarms are most active, and find the context you need to resolve problems.

<img src="https://mintcdn.com/insaion/6G7kMJ9f-czk-eIb/assets/alarms/incidents.png?fit=max&auto=format&n=6G7kMJ9f-czk-eIb&q=85&s=b4fce9fd132a16085f35659a7a1048cb" alt="Incidents main list placeholder" width="2940" height="1502" data-path="assets/alarms/incidents.png" />

### At-a-glance information

Each row in the incident list shows the most relevant details so you can quickly scan and prioritize:

* Status: The current lifecycle of the incident (Open, Acknowledged, Resolved). Color-coded badges make it easy to spot urgent items.
* Triggered: A human-friendly time indicator (e.g., "5 minutes ago") with the exact timestamp available on hover.
* Alarm Name: Which alarm rule created the incident, so you know what condition was met.
* Summary: A short description of why the incident fired to help you triage faster.

Click any row to see more details or use the action menu to analyze the incident with Insaion Copilot.

### Filters and time ranges

Use the controls above the list to narrow the incidents shown:

* Status filter: Show only Open, Acknowledged, or Resolved incidents.
* Alarm filter: Limit the list to incidents from a specific alarm rule.
* Time range picker: Focus on recent events or look back over a custom period.

There's also a Clear Filters button to quickly reset all filters.

<img src="https://mintcdn.com/insaion/6G7kMJ9f-czk-eIb/assets/alarms/incidents-filters.png?fit=max&auto=format&n=6G7kMJ9f-czk-eIb&q=85&s=3c4249f4ff83a4d80699a029901de07b" alt="Incidents filters placeholder" width="2554" height="182" data-path="assets/alarms/incidents-filters.png" />

### Sorting and pagination

You can sort the list by status, triggered time, or alarm name using the column headers. Results are paginated so you can step through large sets of incidents. Use the page controls at the bottom of the list to move between pages.

### Analysis

For a complete walkthrough of the AI flow, see [Copilot Incident Analysis](/copilot/incident-analysis).

Click the action menu (three-dot button) on an incident to access quick actions such as:

* Analyze with Copilot: Launch incident analysis with context preloaded so you can investigate root causes faster.

When you choose Analyze with Copilot, the app starts an AI-assisted investigation using the incident context and related telemetry.

During analysis, Copilot correlates relevant signals, suggests a focused visualization layout, and highlights likely causes or related anomalies to validate.

When additional packet-level evidence is required, Copilot prepares an MCAP extraction request with a scoped time window and pipelines. After approval, upload and artifact registration proceed automatically, and Copilot resumes deep analysis in the same thread.

Final findings are streamed live and stored as a structured report so they remain available after refresh or reconnect.

You can continue exploring the same incident manually in the embedded Lichtblick visualizer at any point.

If your workspace reaches its AI credit limit, the app will show a clear warning and you can continue with manual investigation using the same incident context.

<img src="https://mintcdn.com/insaion/Z0A9BnZWnKPozWQY/assets/alarms/analysis.png?fit=max&auto=format&n=Z0A9BnZWnKPozWQY&q=85&s=d7d0b2a7abaa2936b1ac2c51bfe55f70" alt="Analysis placeholder" width="1891" height="925" data-path="assets/alarms/analysis.png" />

### Best practices

* Triage Open incidents first — these indicate active conditions that may need immediate attention.
* Acknowledge incidents you’re investigating so teammates know someone is working on them.
* Resolve incidents after the problem is fixed to keep the list focused on ongoing issues.

### Troubleshooting tips

* If expected incidents do not appear, confirm the alarm rule is enabled and that the time range or status filters do not exclude the event.
* Use the alarm name to jump back to the rule definition if you need to adjust thresholds or scope.

<div className="insaion-footer" role="contentinfo">
  <div className="insaion-footer__card">
    <div className="insaion-footer__content">
      <span className="insaion-footer__icon" aria-hidden="true">
        <svg viewBox="0 0 24 24" width="20" height="20" aria-hidden="true" focusable="false" className="insaion-footer__svg" role="img">
          <path fill="currentColor" d="M21 6.5A3.5 3.5 0 0 0 17.5 3h-11A3.5 3.5 0 0 0 3 6.5v5A3.5 3.5 0 0 0 6.5 15H8v3l3-3h6.5A3.5 3.5 0 0 0 21 11.5v-5zM7 8.5a1 1 0 1 1 0 2 1 1 0 0 1 0-2zm4 0a1 1 0 1 1 0 2 1 1 0 0 1 0-2zm4 0a1 1 0 1 1 0 2 1 1 0 0 1 0-2z" />
        </svg>
      </span>

      <div>
        If something's unclear or you hit a blocker, contact us on

        <a href="https://discord.gg/ZJMPfMmu3S" target="_blank" rel="noopener">
          Discord
        </a>

        or <a href="mailto:contact@insaion.com">[contact@insaion.com](mailto:contact@insaion.com)</a>
      </div>
    </div>
  </div>
</div>
