Monitoring is a vital component of maintaining the availability and performance of your databases.
VMware Data Services Manager collects health and metric data for each database. You can view this data and use it to track the resource consumption, performance, and activity of your databases.
Viewing Database Status
The Status of a database is an indicator of the overall health of the database.
VMware Data Services Manager uses the database Status to reflect the availability the database, and in some cases to identify an in-progress operation or a critical operation that failed. The Status of a database is also affected by alerts that VMware Data Services Manager might trigger on the database.
Procedure
Perform the following procedure to examine the status of a database:
Select Databases from the left navigation pane.
This action displays the Databases view, a table that lists the provisioned database databases.
Examine the databases listed in the table, identify the database of interest, and navigate to that table row.
Examine the Status.
Viewing Database Health
The health of a database reflects the status of the services running in the VM, the status of certain resources that it consumes, and its connectivity to internal and external components. Database health is directly related to alerts that VMware Data Services Manager may have triggered for the database. Refer to Database Alerts for details on the types and severity of alerts that VMware Data Services Manager may trigger for an database.
Procedure
Perform the following procedure to view the health of a database:
Select Databases from the left navigation pane.
This action displays the Databases view, a table that lists the provisioned databases.
Examine the databases listed in the table, identify the database of interest, and navigate to that table row.
Click the database Instance Name.
The database information Summary tab displays.
Select the Monitoring tab.
This action displays monitoring data for the database.
Review the database alerts and metrics.
Click the the three-dot icon next to a specific alert in the Alerts table, and click Further Info to display additional information.
If needed, use the Node or the Time Range Last drop-down menus in the Metrics section to change the node and metrics aggregation period.
To configure alert notifications and manage threshold values for the alerts, see Configuring Webhook Settings and Managing Alerts for Databases.
Database Alerts
VMware Data Services Manager triggers an alert on a database when it encounters connectivity or resource issues on the database. You monitor these alerts in the Alerts pane of the Monitoring tab.
About the Alert Levels
VMware Data Services Manager triggers alerts of the following levels:
- OK
- WARNING
- CRITICAL
About the Alert Types
Alerts that VMware Data Services Manager might trigger on a database include the following. The table also offers mitigation suggestions to resolve the alert without disrupting the daabase services.
| Alert | Description | DSM User | DSM Administrator | vSphere Administrator |
|---|---|---|---|---|
| CPU Health | CPU usage has exceeded the predefined threshold. | Try to reduce the database read/write load. If necessary, consider altering the VM class. | Try to reduce the database read/write load. If necessary, consider altering the VM class. | Verify the CPU usage in vCenter. If necessary, consider altering the VM class. |
| Data Disk Health | Data disk usage has exceeded the predefined threshold. | Increase the data disk size. | Increase the data disk size. | Increase the data disk size. |
| Database Bin Log | Database binary log is not being uploaded. | Contact the vSphere Administrator. | Contact the vSphere Administrator. | Validate the connection to the backup storage repository, check its status, verify the correctness of the bucket name, confirm the expiration date of certificates, ensure that credentials are up-to-date within VMware Data Services Manager, and check for sufficient available space. |
| Wal File Health | Database wal files are not being uploaded. | Contact the vSphere Administrator. | Contact the vSphere Administrator. | Validate the connection to the backup storage repository, check its status, verify the correctness of the bucket name, confirm the expiration date of certificates, ensure that credentials are up-to-date within VMware Data Services Manager, and check for sufficient available space. |
| Custom Config Health | The custom configuration settings for the database are not being applied as intended. | Verify and update the database configuration. | Verify and update the database configuration. | Verify and update the database configuration. |
| Database Engine Health | Database engine service is currently experiencing issues or disruptions. | Contact the vSphere Administrator. | Contact the vSphere Administrator. | Investigate and resolve any issues with the database engine service. |
| Database Engine Failed To Start | Failed to initiate database engine. | Contact the vSphere Administrator. | Contact the vSphere Administrator. | Investigate and resolve any issues with the database engine service. |
| Max Connections | Database connection usage has exceeded the predefined threshold. | Try to decrease the number of active connections or modify the configuration to raise the maximum connection limit. | Try to decrease the number of active connections or modify the configuration to raise the maximum connection limit. | Modify the configuration to raise the maximum connection limit. |
| Metrics | Data Service Manager is not receiving metrics from the database cluster. | Contact the vSphere Administrator. | Contact the vSphere Administrator. | Investigate and resolve any issues with the Telegraf service in the workload cluster. Additionally, verify the connectivity between Telegraf and the Provider appliance. |
| System Disk Health | System disk usage has exceeded the predefined threshold. | Contact the vSphere Administrator. | Contact the vSphere Administrator. | Investigate and remove unnecessary files from the system disk. |
Database Metrics
VMware Data Services Manager collects metric data for each database. You can view this data and use it to track the resource consumption, performance, and activity of your databases.
Available metrics include the following:
- Active Connections
- CPU Usage % - The ratio of used to allocated CPU.
- Memory Usage % - The ratio of used to allocated memory.
- Disk Usage % - The ratio of used to allocated disk.
- Write Throughput
- Read Throughput
- Commits & Rollbacks
- Deadlocks & Conflicts
By default, VMware Data Services Manager displays the last 3 hours of aggregated metric data. You can change this time period (calculated from current time) via the Time Range Last drop-down in the Metrics pane.
