> For the complete documentation index, see [llms.txt](https://docs.datalogz.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datalogz.io/guides/monitors/sigma-monitors.md).

# Sigma monitors

Sigma monitors are pre-configured monitors to help you quickly begin monitoring common and critical aspects of your Sigma environment. For more information, see the Monitors documentation.

{% hint style="info" %}
This list contains all out of the box Datalogz Sigma monitors. Customisations can be made by cloning an existing monitor or on request.
{% endhint %}

### The default monitor catalog

Control Tower ships 9 default Sigma monitors. Every monitor can be switched on or off in the Monitor Catalog, and cloned into My Monitors to tailor its logic.

* **Broken Connections** (Performance): data connections that are failing or no longer reachable.
* **Broken Lineage** (Quality Standards): workbooks or data models whose lineage references are broken.
* **Direct User Grants** (Security): permissions granted directly to individual users instead of teams.
* **Empty Teams with Active Grants** (Security): teams with no members that still hold permissions.
* **Tag Coverage & Drift** (Governance): assets missing required tags or drifting from your tagging standards.
* **Concurrent Materialization Schedules** (Performance): materializations scheduled to run at the same time and competing for resources.
* **Duplicate Formulas** (Quality Standards): the same formula defined in multiple places.
* **Orphaned Assets** (Governance): assets without an active, accountable owner.
* **Personal Workspace Drift** (Governance): content accumulating in personal workspaces instead of governed ones.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.datalogz.io/guides/monitors/sigma-monitors.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.