> 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/organizational-setup/user-onboarding-guide/users-and-user-groups/monitor-catalog.md).

# Monitor Catalog

The **Monitor Catalog** is where you control which Datalogz monitors run for each BI platform. Every monitor is on by default.

**What you do:**

1. Go to **Settings > Monitor Catalog**.
2. Open the tab for your BI platform (Power BI, Tableau, Qlik Sense, Sigma, or Databricks).
3. Toggle individual monitors on or off. Monitors you switch off stop generating alerts.
4. If a check you need is missing, use the **request a monitor** option and the Datalogz team will follow up.

The catalog controls what is available account-wide; which monitors run for a specific team is set during team setup.


---

# 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/organizational-setup/user-onboarding-guide/users-and-user-groups/monitor-catalog.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.