> For the complete documentation index, see [llms.txt](https://docs.nuvens.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nuvens.cloud/admin/support-section/database-health.md).

# Database Health

In **Database Health**, you can view a live overview of the current database connection and overall health status. This page provides visibility into connectivity, transaction log usage, blocking activity, and database storage utilisation.

<figure><img src="https://1977539604-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5qADNWBPym2Zh4ZaguCE%2Fuploads%2F46H7pqCSXBHq3jysY8Oy%2Fdatbasehealth.png?alt=media&amp;token=658e37d0-af08-4b75-94b6-e8f70b081472" alt=""><figcaption></figcaption></figure>

The **Connectivity** section confirms whether the system can connect to and query the database, and displays the current database state and recovery mode.

The **Transaction Log** section shows the total log size and the percentage currently in use.

The **Blocking / Locks** section highlights any blocking sessions, lock waits, or blocked requests that may impact performance.

The **Database Data Files** section displays allocated, used, and available space within the database files.

The **AWS RDS Recent Events** section lists recent database events from AWS RDS, including notifications and backup activity from the last 24 hours.


---

# 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.nuvens.cloud/admin/support-section/database-health.md?ask=<question>&goal=<user_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.
