> 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/insights.md). # Insights ### Overview Insights is the single pane of glass for everything happening across your BI estate. It blends live signals with historical context to surface the health, risk, and usage of your BI tools in a clean, visual dashboard, so you can spot issues fast and act with confidence. Datalogz offers two types of Insights: * **BI360 (Org-wide Global Insights):** A consolidated pulse of key metrics and alerts across connected platforms like Power BI, Tableau, and Qlik. See uptime, freshness, failures, usage, and cost drivers across your entire BI ecosystem in one place. * **Team-based Insights (Tool/Team level):** Focused views scoped to specific tools and ownership teams. Drill into what matters for that team—pipelines, reports, datasets, schedules, orphaned assets, and SLA adherence. ### What makes Insights different Datalogz Insights into your BI environment are critical because it convert logs and usage into operational intelligence that protects SLAs, cuts waste, reduces risk, and drives adoption. Beyond flagging failures, it reveal trends, dependencies, and ownership so you can plan changes and enforce governance with evidence. By contrast, Power BI and Tableau admin tools focus on administering one platform, for example workspaces/projects, gateways/servers, extracts/refreshes, and surface tool-specific snapshots for a limited amount of time. Estate-level insights (e.g., BI360 and team views) normalize signals across tools, preserve history, correlate events to affected assets and owners, and link every finding to an action. In short: admins run a tool; insights let you run the whole BI estate. ### How to create Insights Today, Insight tabs aren’t self-service. To add new views or tailor existing ones (metrics, filters, thresholds, layouts), reach out and we’ll configure them with you, aligned to your governance model, SLAs, and business goals. {% hint style="info" %} For further questions on insights, please contact our team at {% endhint %}
--- # 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/insights.md?ask=&goal= ``` `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.