> For the complete documentation index, see [llms.txt](https://awsnotes.dendron.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://awsnotes.dendron.so/database/amazon-aurora/common/monitoring-metrics-in-an-aurora-db-cluster.md). # Monitoring metrics in an Aurora DB cluster {% hint style="info" %} This page was generated from content adapted from the [AWS Developer Guide](https://github.com/awsdocs/amazon-aurora-user-guide.git) {% endhint %} ## Viewing cluster status and recommendations * **Note**\ Aurora also uses another status called *maintenance status*, which is shown in the **Maintenance** column of the Amazon RDS console. This value indicates the status of any maintenance patches that need to be applied to a DB cluster. Maintenance status is independent of DB cluster status. For more information about maintenance status, see [Applying updates for a DB cluster](https://github.com/kevinslin/aws-reference-notes/blob/main/services/amazon_aurora/USER_UpgradeDBInstance.Maintenance.md#USER_UpgradeDBInstance.OSUpgrades). * **Note**\ Amazon RDS also uses another status called *maintenance status*, which is shown in the **Maintenance** column of the Amazon RDS console. This value indicates the status of any maintenance patches that need to be applied to a DB instance. Maintenance status is independent of DB instance status. For more information about maintenance status, see [Applying updates for a DB cluster](https://github.com/kevinslin/aws-reference-notes/blob/main/services/amazon_aurora/USER_UpgradeDBInstance.Maintenance.md#USER_UpgradeDBInstance.OSUpgrades). ## Analyzing performance with DevOps Guru for RDS * **Important**\ We recommend that you test any changes on a test instance before modifying a production instance. In this way, you understand the impact of the change. --- # 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://awsnotes.dendron.so/database/amazon-aurora/common/monitoring-metrics-in-an-aurora-db-cluster.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.