> 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/alert-details.md). # Alert Details There are two ways to get details about a given alert. You can either click on an alert in the [Alerts](/guides/alerts.md) tab or you can click on the Alert button on the [Active Alert](/guides/inventory/asset-health.md) tab for a given asset in [Inventory](/guides/inventory.md). Both options opens the Alert Details page which provides the details of the alert. This page offers all the information needed to diagnose and resolve the problem, including: * **Event Occurrence** (only for Event based alerts): Shows when and how often the event that triggered the monitor occurred. * **Tracking details**: Details that help you track the alert and its lifecycle, including its status, priority and who the alert is assigned to. You can change tracking details on this page or in the Alerts tab via the [Bulk Edit](/guides/alerts/bulk-edit-alerts.md) feature. * **Summary** * **Alert Type**: The type of alert, Asset based or Event based. * **Monitor**: The name of the monitor that triggered the alert, providing context for the rule that was violated. * **Monitor Category**: The kind of problem the monitor checks for, such as Governance, Performance, or Unused. Categories let you group and reason about alerts by problem type rather than by individual monitor names. * **Timeframe** (for staleness and unused-asset alerts): 30 / 60 / 90 badges that show how long the condition has persisted. A green badge means the condition is breached at that window; a grey badge means it is not. * **Asset details**: Key details about the asset affected by the alert, including its type (e.g., Report, Dashboard, Dataset), name, and unique ID. * **Connector**: The specific data source or connector (e.g., Power BI, Tableau) from which Datalogz captured the alert. * **Metadata**: A detailed view of the metadata Datalogz has collected for the impacted asset. This information is crucial for understanding the state of the asset at the time of the alert.
## How to resolve an alert When you're ready to resolve an alert, you have a couple of options: * Resolve via [workflow](/guides/alerts/alert-workflows.md): You can resolve an alert yourself by leveraging Datalogz's built-in alert workflows. These workflows provide you with scripts to resolve the issue in your BI environment. * Share with an external contact: If you need to involve someone who doesn't have access to Datalogz, such as an asset owner or a data engineer, you can share the alert's details with them via the Share button. This sends the alert details to an email address.
--- # 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/alerts/alert-details.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.