Date: Tue, 19 Mar 2024 08:56:41 +0000 (UTC) Message-ID: <1192373502.2881.1710838601436@ip-10-0-1-161.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2880_894628595.1710838601429" ------=_Part_2880_894628595.1710838601429 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Contents
The most critical component of any application is the network that surro= unds it. To ensure that your network is available and running smoothly, we = suggest monitoring the following components around your database server:
In this section we will review the monitors that are generally recommend= ed to fully monitor your services.
We recommend using the service monitors listed below to monitor the inte= rnal application performance of your database server.
MySQL (Advanced Metrics) M= onitor. The MySQL (Advanced Metrics) service monitor provides deta= iled internal performance information from your database server. In an inst= anced environment you will need to add a single monitor to each instance (t= he monitor will track performance of all databases within any given instanc= e). If you want to graph or report on internal database performance at a la= ter date, be sure to click the Save for Graphing checkbox beside each stati= stic in the service monitor. For a full list of metrics available from the = MySQL (Advanced Metrics) service monitor, please see the MySQL Advanced Metrics article. The following = graph shows an example of MySQL performance statistics colected from an exi= sting MySQL Advanced service monitor:
The following example shows some = important settings and thresholds in the MySQL (Advanced Metrics) Monitor:<= /p>
Note
Performance Service Monito= r. The Performance Service monitor will allow you to monitor the a= verage CPU consumption of your critical database processes over time. We su= ggest that each database process have a Performance monitor dedicated to it= . Each process should not consume more than an average of 70% of system CPU= for a period greater than 15 minutes. Here are some example settings for t= he Performance Service monitor:
MySQL (Basic Checks). This monitor allows you to verify that your MySQL database is respondi= ng to query requests by either executing a standard query or performing a s= imple port check against your server. This monitor also allows you to execu= te application-specific queries that may help you to evaluate end user expe= rience problems if these set queries begin to slow down. The following exam= ple shows a configured MySQL (Basic Checks) monitor:
Process Count Monitor. The Uptime Infrastructure Monitor Process Count Monitor can be config= ured to ensure that your database processes are present on the host system.= We recommend setting thresholds indicating if 0 instances of the processes= in the following table are found.
Process Name | Application | Details |
mysqld | The MySQL Daemon | N/A |
safe_mysqld | MySQL Wrapper Process= td> | Alternate: mysqld_safe<= /td> |
mysql-nt | Windows MySQL Daemon |
Here are some example settings to check for the mysqld pr= ocess:
Don't forget the value of monitoring the server that is hosting your dat= abases. Monitoring and alerting on the performance of your servers will be = critical to ensure that you maintain database availability and meet capacit= y demands. Monitoring on key performance indicators such as CPU Usage, Disk= I/O, Network I/O and Memory usage is essential to ensure your servers are = running properly.
Now that you are monitoring your MySQL Database Server it is time to mov= e on to one of these next steps: