# Working with the Monitoring Table

The Monitoring table is the primary workspace for tracking compliance check performance in Sprinto. It provides a consolidated, filterable view of all active, available, and disabled checks — allowing you to triage issues, investigate failures, and take corrective actions in one place.

Whether you're a compliance owner reviewing failing tasks or a security lead prioritising automation gaps, the Monitoring table helps you take informed action quickly.

***

### Table Layout and Columns

Each row in the table represents a single monitor or compliance check and includes the following details:

<table><thead><tr><th width="138.203125">Column</th><th width="517.890625">Description</th></tr></thead><tbody><tr><td><strong>Check Name</strong></td><td>The title of the monitor; includes type (Automated or Workflow)</td></tr><tr><td><strong>Entity</strong></td><td>The system or person being evaluated (e.g., EC2, Staff, Vendor)</td></tr><tr><td><strong>Provider</strong></td><td>The integration/source linked to the check (e.g., AWS, GitHub)</td></tr><tr><td><strong>Area</strong></td><td>Compliance area (e.g., Infrastructure, People, Access, Risk)</td></tr><tr><td><strong>Owner</strong></td><td>The assigned user responsible for this check</td></tr><tr><td><strong>Task Status</strong></td><td>The compliance outcome (Passed, Due, Failing, Critical)</td></tr></tbody></table>

Clicking any row opens the **Check Details** view.

***

### Tabs: Active, Available, Disabled

The table is divided into three views:

* **Active Checks**: Enabled monitors that are currently being evaluated
* **Available Checks**: Checks you can configure and enable
* **Disabled Checks**: Monitors that have been turned off or archived

Tabs share a common filter set and persist your preferences across sessions.

***

### Use Filters to Narrow Down Checks

Select **Filters** in the top-right corner to customise your view. Filters apply to all tabs.

Available filter criteria:

* **Framework** (e.g., SOC 2, ISO 27001)
* **Control** (mapped compliance controls)
* **Area** (People, Infrastructure, Access, Risk)
* **Task Status** (Passed, Due, Failing, Critical)
* **Check Owner**
* **Provider** (e.g., AWS, Azure, GitHub)
* **Check Type** (Workflow, Automated)

You can use multiple filters simultaneously. To reset, manually deselect fields or refresh the view.

***

### Table Actions

You can perform the following actions directly from the Monitoring table:

<table><thead><tr><th width="155.85546875">Action</th><th>Description</th></tr></thead><tbody><tr><td><strong>View &#x26; Fix</strong></td><td>Opens the Check Details page with task insights and remediation options</td></tr><tr><td><strong>View Details</strong></td><td>Opens the side panel or drawer view with health summaries</td></tr><tr><td><strong>Create Check</strong></td><td>Launches a guided interface to add a new workflow monitor</td></tr><tr><td><strong>Bulk Actions</strong></td><td>(Planned) Apply filters to batch-edit or triage multiple monitors</td></tr></tbody></table>

***

### Tips for Working Efficiently

* **Sort by Status**: Focus on failing or critical tasks first.
* **Use Owners**: Assign clear owners to distribute accountability.
* **Monitor Areas Separately**: Use Area filter (e.g., People vs Infrastructure) for focused reviews.
* **Leverage Check Types**: Distinguish between automated and workflow monitors to identify manual gaps.
* **Keep Tabs Clean**: Disable old or irrelevant checks to reduce noise.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sprinto.com/monitoring/dashboard-actions/working-with-the-monitoring-table.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.