> 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/default-monitors.md). # Default Monitors ### Overview Default Monitors are out-of-the-box monitors created and owned by Datalogz. Default Monitors are pre-configured to help users quickly begin monitoring common and critical aspects of their BI environment. These monitors are set up with default SQL queries and thresholds based on industry best practices, allowing users to start receiving alerts and insights without any initial setup. ### How does it work? * **Pre-Built by Our Team:** Default Monitors are developed and maintained by our team, designed to cover a wide range of use cases for managing BI environments. These monitors come preconfigured with SQL queries that evaluate common thresholds and criteria for data performance, security, usage, and compliance. * **Ready to Use:** Users can immediately begin using Default Monitors after setting up their BI environment. These monitors will automatically generate alerts based on predefined rules, requiring no further configuration from the user. * **Fixed Configuration:** Users cannot directly modify the SQL queries or thresholds of Default Monitors, ensuring that these monitors remain consistent and reliable as standard tools for all users.

--- # 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.datalogz.io/guides/monitors/default-monitors.md?ask=&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.