> 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/datalogz-framework/datalogz-bi-pillars.md).

# Datalogz BI Pillars

A healthy analytics environment requires attention across five essential pillars: **Security, Cost Management, Governance, Quality Standards, and Performance**. Every monitor and alert in Datalogz Control Tower is tagged with one or more of these pillars, so you always know why an issue matters and who should care about it.

### Security

Security is continuous oversight of who can access your BI environment and how it is being used. Control Tower flags risks such as unusual access activity, suspicious export behavior, and permission changes on sensitive assets.

**What you do:** review security alerts as they appear and route them to the right owner. High-visibility assets get extra protection automatically.

### Cost Management

Cost Management is about getting full value from your BI investment without waste. Control Tower identifies unused licenses, idle reports and dashboards, redundant refreshes, and other avoidable spend across your BI tools.

**What you do:** review surfaced savings opportunities, confirm with asset owners, and clean up. Most customers surface measurable savings within the first weeks.

### Governance

Governance keeps your analytics estate structured, owned, and compliant. Control Tower detects orphaned and unowned assets, uncertified content, stale reports, and policy breaches such as users outside your SSO standard. Control Tower finds duplicate measures, reports built without a proper data model, and conflicting or redundant content that leads to inconsistent answers across teams.

**What you do:** assign owners to unowned assets, certify the content your organization should trust, and retire what is stale. Consolidate duplicates and standardize on certified definitions so every team reports from the same source of truth.

### Performance

Performance ensures reporting stays fast and reliable. Control Tower tracks failed and long-running refreshes, capacity pressure, and configuration issues before they slow your users down.

**What you do:** act on refresh and capacity alerts to keep dashboards loading and data fresh.

### How it works

Control Tower ships with a catalog of curated **default monitors** for each connected BI platform (Power BI, Tableau, Qlik Sense, Sigma, and Databricks). Each monitor continuously checks your environment against a specific rule and is tagged with the pillar it protects. When an asset breaches a rule, an **alert** is created with the affected asset, the reason, and a recommended fix.

You can also create **custom monitors** to track rules specific to your organization, such as internal naming standards or department-specific thresholds.

**Actions to take:**

1. Open the **Monitor Catalog** and enable the monitors relevant to your environment. Default monitors work out of the box.
2. Subscribe the right people to monitor notifications so alerts reach owners immediately.
3. Triage alerts from the **Alerts** page: assign, prioritize, and resolve. Every change is tracked in an audit trail.
4. If a check you need is missing, create a custom monitor or request one from the catalog.


---

# 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:

```
GET https://docs.datalogz.io/guides/datalogz-framework/datalogz-bi-pillars.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.