<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=95128&amp;fmt=gif">

Troubleshooting Best Practices: Monitoring the Production Database Without Killing Performance


Please watch Percona’s Principal Support Engineer Sveta Smirnova as she presents Troubleshooting Best Practices Monitoring and Don’t Kill Your Production.

During the MySQL Troubleshooting webinar series, I covered many monitoring and logging tools such as: 

- General, slow, audit, binary, error log files 
- Performance Schema 
- Information Schema 
- System variables 
- Linux utilities 
- InnoDB monitors 
- PMM 

However, I did not spend much time on the impact these instruments have on overall MySQL performance. And they do have an impact. 

And this is the conflict many people face. MySQL Server users try exploring these monitoring instruments, see that they slow down their installations, and turn them off. This is unfortunate. If the instrument that can help you resolve a problem is OFF, you won’t have good and necessary information to help understand when, how and why the issue occurred. In the best case, you’ll re-enable instrumentation and wait for the next disaster occurrence. In the worst case, you try various fix options without any real knowledge if they solve the problem or not. 

This is why it is important to understand what impact monitoring tools have on your database, and how to minimize it. 

In this webinar, I cover why certain monitoring tools affect performance, and how to minimize the impact without turning the instrument off. You will learn how to monitor safely and effectively.