( MaxGauge Logging ontroller )
The limitation of real-time performance management is in that the problem diagnosis and resolution must be done in real-time. However, a DBA cannot work 24 hours around the clock at the workstation for real-time monitoring and diagnosis. And in the event performance issues arise, if we try to resolve the issues by rebooting the database, cancelling sessions by force, or program’s automatic shutdown, the source of data through which the root cause of the problem may be identified will be destroyed, making it impossible to further investigate the problem through a post-analysis.
MaxGauge logs various performance information collected from MySQL in a safe repository to support post-analysis of the performance issues, and it compensates for the timing limitation of real-time monitoring through log analysis.
Especially, it replays the past execution situations as if in real-time, and by rewinding back to a specific time in the past, the analyzing function of the sessions and SQL executed at the corresponding time can be a helpful resource in identifying the root cause of the problem and finding the solutions. MaxGauge also provides trends analysis function for a log accumulated over a period of several of days.
MaxGauge collects and logs MySQL ‘s performance information, session information, and lock information by using the queries. The DBA can set up the logging cycle and logging data through the Logging Controller program, and do an analysis with the Performance Analyzer program.
You can check the performance degradation and database error phenomenon generated in the system, after it has occurred. Since you can check the performance indicators trends of data for specific time period by using the Performance Analyzer, you can accurately and conveniently pinpoint the time at which overload occurred, and by migrating to that specific time, you can identify the sessions and SQL executed at that time.