> 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/databricks-monitors.md).

# Databricks monitors

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

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

### The default monitor catalog

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

* **Catalogs with Non-User Ownership** (Governance, high priority): catalogs owned by groups or service principals rather than an accountable user.
* **Schemas Without User Owner** (Governance): schemas lacking an accountable owner.
* **Tables Without Description** (Governance): tables missing documentation.
* **Hot Schemas** (Performance): schemas with more than 25 tables, candidates for restructuring.
* **Wide Tables** (Performance): tables with unusually large column counts.
* **Empty Schemas** (Governance): schemas that contain no tables.
* **Delta Sharing Exposed** (Security, high priority): data exposed externally through Delta Sharing.
* **Stale Managed Tables** (Governance): managed tables that have not been updated recently.


---

# 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/databricks-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.