Working as a database admin for a company that supports an e-commerce site, one of your top priorities should be to keep track of your database performance. If it is performing well, it is also crucial that it would be able to cater to all the traffic and user transactions it will continuously process.
For the past few years, you have been working mostly on SQL Server databases. One day the database admin that was in charge on PostgreSQL database management system had resigned, and the IT manager re-assigned the task of maintaining the PostgreSQL databases to you. Now it is up to you to monitor and manage those databases.
The DB team is using dbWatch Control Center, and you were wondering how dbWatch Control Center can monitor PostgreSQL databases performance as you’ve never worked of a PostgreSQL database platform before, and you need to know the key performance indicators of a healthy PostgreSQL database. What you need is a database monitoring system that can help you keep track of all your database servers in key aspects such as performance, resource usage, and reporting.
With dbWatch Control Center, database admin’s can easily analyze the different factors that cause performance impact in their PostgreSQL database environment, using the available performance jobs available to keep track of your database servers health.
Starting with the management module of dbWatch Control Center. In this view, if you expand the Test Group you can see that we have - T001-Postgresql13 instance that we are monitoring.
This view shows different information of the PostgreSQL database instance. Information such as the database management system name/platform, database management system version, server IP/Port.
It also contains information of the database sizes, as well as graphs for logical reads per/sec, total sessions, and memory pools configuration.
When you click on sessions, you will see the active sessions in the PostgreSQL instance. The view displays the active processes showing PID, username, database, wait event type, wait event, query start, current query, and other information.
You can see in this view that there is an ongoing blocking scenario; there are existing queries that are blocking one another. If you right-click on a session, you can check the explain query to know more about this session or query that causes the blocking, or maybe you can kill the process if you are certain that it isn’t a critical query process.
If you expand on Database, then choose Schemas. A new view will appear which gives you information on which schema consumes the most disk space and how many tables are in a specific schema.
If you go to the Monitoring module of dbWatch Control Center, click on the instance which is T001-Postgresql13. Expand the performance folder; you will find jobs which tracks your database performance.
Let’s look at the Details of the job – Locks held and statistics. Right-click on it and choose Details.
The report shows the objects most locked within the last 24 hours. The query blocked earlier was a select query that selects data from the “items” table. Which is shown in this report that it has a total of 5 lock counts during the last 24 hours.
This information helps you identify whether you need to do a table partition, create proper indexes, or archive some of your old data to lessen rows of data in a table to avoid long-running queries or continuous blocking scenarios such as this. Long-running queries could lead to deadlock processes – which affect transaction processing inside your database and affect your database performance.
With dbWatch Control Center, database admin’s can now monitor their PostgreSQL database performance and monitor other important information in their database. As a DBA, you can now analyze sessions and blocking occurrence in your database and identify which objects are usually affected by these scenarios.
dbWatch Control Center assists database admin’s to efficiently run their databases, from proactive monitoring of database performance to management of tasks.
You can try dbWatch Control Center today. Use this link to download a version of dbWatch Control Center that can monitor up to 5 instances for 6 months for free: dbWatch Control Center free license
If you have any questions or you would like to know more on how dbWatch can assist you in your current enterprise database monitoring and management situation, feel free to contact me directly: firstname.lastname@example.org or email presales@dbWatch.com
#DatabaseMonitoring #PostgreSQL #PostgreSQLMonitoring #DatabaseReporting #DBA #DatabaseManagement #DatabasePerformance #DatabaseAdmin
Chad Pabalan is a Pre-Sales Engineer for dbWatch and a DBA specializing in SQLServer high availability setups and disaster recovery planning and configurations. He is an AWS Certified Solutions Architect Professional, a cloud enthusiast specializing in architecture and designing scalable, high available, and fault-tolerant systems on AWS Cloud.