> For the complete documentation index, see [llms.txt](https://docs.datasentinel.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datasentinel.io/manual/features/key-features/alerting/manager.md). # Manager Various methods exist for both viewing and managing notifications. A notification is composed of several elements:

Element	Description
Event time	Creation time of the notification
Notification type	Possible values: PROBLEM, RECOVERY, ACKNOWLEDGED
Instance name	PostgreSQL instance name
Check name	Name of the rule
State	Possible values: WARNING, CRITICAL, OK
Message	Informational message giving more details about the problem

## Issue Overview > The top right corner of dashboards displays the count of instances currently on alert, along with the number of ongoing issues.

Click buttons to access detailed issues.

{% hint style="info" %} Datasentinel auto-sets problems as **OK** with a **RECOVERY** notification when they're no longer relevant.\ You can also manually acknowledge problems. (Notification type **ACKNOWLEDGED**) {% endhint %} ## Notifications All current or past issues are visible on the dashboard **All notifications**

*Click a notification to view its details.* ## Notifications by Instance > The dashboard **Notifications by instance** summarize problems by instance with the ability to switch to a particular instance

## Annotations > Problems are visible on the activity graph of sessions and on the top queries graph as annotations

*Moving the mouse over the icon displays the problem details* ## Instance Details > When examining a particular instance, you'll have access to its current rules and any associated issues.

--- # 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.datasentinel.io/manual/features/key-features/alerting/manager.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.