One of the key factors for a successful application tuning is to find the root cause of the performance issues.
It sounds obvious but it’s common to see a lot of effort and resource being wasted trying to solve what seems to be the cause of the problem but instead is a consequence. Besides all that effort and used resources, it won’t bring the expected result!
The methodology used to monitor your application environment can give you a distorted view of the problems. In a production environment, your database is not only accessed by your application. There is always some maintenance operations held by your DBA, other applications, an ETL job, a query executed by the development team, a forgotten application that runs once a month and etc.
When you monitor only from the application perspective, you leave a gap by not considering the other actors that compete for your database resources as well.
NAZAR shows a database perspective of your application environment, presenting a global view of each actor that uses your database resources (not only from your application!). You can also view a complete report for all databases in your server or you can filter and have a detailed report for a specific one.
Our team has now enhanced its capability to help you identifying the root causes of performance bottlenecks by showing, in the “Commands By Hour” section, commands other than DMLs that may compromise your application's performance.
Originally published at blog.nazar.io.
