> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/data-library/incidents/dashboard-actions/monitor-incident-checks.md).

# Monitor Incident Checks

Track incident resolution and data loss reporting using Sprinto’s automated monitoring checks for complete compliance visibility.

Sprinto automatically generates and tracks monitoring checks for all integrated incident sources to ensure timely incident resolution and compliance with security frameworks. These checks validate whether incident tickets have been closed and if associated data loss has been reported to the appropriate stakeholders.

All active and failing checks are displayed in the *Monitoring* tab within the **Incidents** section.

***

### View Monitoring Checks

1. Go to **Data Library > Incidents > Monitoring**.
2. The interface displays:
   * **Check name**
   * **Source system** (e.g. Jira, Microsoft Defender, PagerDuty)
   * **Current status** (Passing, Failing, Not active)
   * **Days to fail/critical**
   * **Associated zones**
   * **Status history**

{% hint style="info" %}
Monitoring is consistent across all incident source tabs and follows the same filtering and action logic.
{% endhint %}

***

### Filter and Sort Checks

Use the filters at the top to narrow down your view:

* **Check Status:** Passing, Failing, Not active
* **Severity Tags:** Due, Critical
* **Zones:** Filter by business unit or functional area
* **Time-based:** Days until check becomes failing or critical

You can also use the **Search** bar to locate checks by name or source.

***

### Add New Checks

You can define additional incident checks based on workflows and team-specific requirements.

1. Click **Add check** at the top right.
2. Choose one of the following methods:
   * **From template:** Use predefined compliance workflows.
   * **Add single check:** Manually define a specific incident check.
   * **Bulk upload:** Import multiple checks using the provided spreadsheet format.
3. Fill in the necessary details and assign the check to a zone or control group.
4. Click **Create** to activate the check.

***

### View Status History

To review historical changes in a check’s status:

1. Click the **Status history** icon next to any check.
2. A side panel opens showing:
   * Timestamps of status changes (Failing/Passing)
   * Associated actions taken
   * Evidence (if any)
3. Click **Download history** to export this log for audits.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sprinto.com/data-library/incidents/dashboard-actions/monitor-incident-checks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.