> 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/alerts.md). # Alerts An alert is the direct result or notification that is triggered when a [monitor](/guides/monitors.md)'s condition is met. It's the action that the system takes to inform you that something requires your attention. It's designed to be actionable, providing you with the necessary information to diagnose and resolve an issue. Examples: * "The 'Monthly Revenue' dataset refresh failed at 2:00 AM." (This is the alert triggered by a monitor on dataset refresh status.) * "A new report was created in the 'Finance' workspace by a user with a non-finance role." (An alert from a governance monitor.) * "The 'Executive Dashboard' has not been viewed in over 90 days." (An alert from a monitor on report usage.) ## Where to find your alerts Within Datalogz, all alerts generated for a specific [team](/guides/organizational-setup/user-onboarding-guide/teams.md) are centralized in the Alerts tab. This tab serves as the primary location for managing and reviewing all notifications relevant to that team's BI assets. The Alerts tab displays a comprehensive table of all alerts, and it's equipped with powerful tools to help you manage them efficiently: * Filters: Use the filtering options to sort and find specific alerts based on criteria such as monitor, severity, date, or the specific BI asset type involved. * Quick Stats: The interface includes quick statistics that provide an at-a-glance overview of key alert trends, helping you quickly understand the overall health of your team's environment. * Bulk Edit: A Bulk Edit button lets you perform actions on multiple alerts simultaneously, allowing you to quickly change their status and priority, assign them, or dismiss them in a single action. * View by alert <> View by asset: A toggle that allows you to group alerts per asset or see the flat list of alerts. Together, these features give you a consolidated and efficient way to prioritize and resolve critical issues, ensuring your BI environment runs smoothly.
## Two ways to view alerts As you bring more of your analytics estate under Control Tower, a single problem asset can raise many alerts across multiple monitors. One stale Power BI report can fill the list with near-duplicate rows, burying the signal even when the number of real problems is small. To keep triage focused on what to fix first, the Alerts tab offers two views, toggled at the top of the table: * **View by alert**: the classic table with one row per alert. * **View by asset**: alerts grouped by the asset they affect, so a problem asset shows as a single row instead of many. **View by asset** reframes the list around the asset, not the symptom. Each asset row shows its monitor categories, its monitor count, and its top priority. Open any asset row to drill into every alert raised against it. Your selected view and the open asset are saved in the page URL, so a grouped view can be shared or bookmarked. Search, filters, sorting, and pagination work the same in both views, across open and resolved alerts. ### Timeframe badges (30 / 60 / 90 days) Staleness and unused-asset monitors now show how long a condition has persisted, using 30 / 60 / 90 timeframe badges. A colored (green, yellow, red) badge means the condition is breached at that window; a grey badge means it is not. A stale report raises one alert that tells you at a glance whether it has been stale for 30, 60, or 90 days, instead of a stream of near-duplicate alerts. The badges appear in the alerts table and in the alert drill-down. ## Updating alerts Effective alert management is a cornerstone of maintaining a healthy and reliable BI environment while fostering efficient team collaboration. By updating alerts, you actively manage the lifecycle of issues, which directly leads to: * Improved BI health: As you track an alert's status from "to do" to "resolved," you ensure that issues - like a failed dataset refresh or an underperforming report - are fixed. This proactive approach helps you minimize downtime and keep your data accurate. * Streamlined teamwork: Updating an alert gives your team a single source of truth. Everyone can see who's responsible for an issue, if it's being worked on, or if it's already been resolved. This transparency prevents people from doing the same work and keeps your team aligned. * Effective prioritization: You can change an alert's priority as a problem becomes more or less critical. This helps your team focus their energy on the most important issues, reducing disruption to your end-users and the business. You have two options for updating alerts: 1. Individual Update: To change a single alert, go to its dedicated [Alert Details](/guides/alerts/alert-details.md) page. 2. Bulk Edit: To update the status, assignee, or priority for multiple alerts at once, use the **Bulk Edit** feature in the alerts table. --- # 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/alerts.md?ask= ``` 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.