Introducing new troubleshooting guides features
We are excited to announce the release of new features aimed at enhancing the troubleshooting experience in Azure PostgreSQL Flexible Server. These features provide detailed insights and metrics, enabling you to optimize your database performance effectively. Here are the use cases where these features can be used: Enhancements to autovacuum monitoring: One of the significant enhancements is the addition of table-level autovacuum details. This feature allows you to: Monitor the number of times autovacuum ran. Check the number of dead tuples cleaned or not removed. Track the time taken to run the autovacuum. Furthermore, we now display the configuration of some important parameters which control autovacuum. We validate some of those parameters and warn you if we consider that the existing configuration might cause issues with the correct functioning of autovacuum. We have also added a new Enhanced metrics tab which displays the Maximum number of Transaction IDs in use and the Oldest backend XMin metrics to provide a comprehensive view of autovacuum health. Enhancements to the CPU troubleshooting guide: To help you manage high CPU usage, we have introduced several new features: Parameter check for excessive logging that might impact the CPU usage and overall server performance. New "Top queries by total duration" tab which displays Query Store queries with total time. New insight card showing sessions whose state is idle and have an open transaction. New tab to showcase PgBouncer metrics and best practices: A new tab to display the locking information: In this section, you can get the overview of locks in your server. You can get the count of sessions involved in Locks. You can monitor the acquired locks duration during the specified time. You can also get insights on blocking session where sessions are still waiting for lock acquisition. Enhancements to the memory troubleshooting guide: For troubleshooting high memory usage, we have added validation for memory parameters where it can show you an insight when you change these parameters higher than defaults. We have also introduced an insight for long (>24hrs) idle sessions that might consume server resources. We believe these new features will significantly enhance your ability to troubleshoot and optimize your Azure PostgreSQL Flexible Server. We look forward to your feedback! Getting started: To learn more about the troubleshooting guides, visit our documentation below: What are the troubleshooting guides in Azure Database for PostgreSQL Flexible Server How to use the troubleshooting guides for Azure Database for PostgreSQL Flexible Server
