Monitoring and KPIs for VMware Tanzu SQL with MySQL for VMs

Page last updated:

This topic describes how to monitor the health of the VMware Tanzu SQL with MySQL for VMs service using logs, metrics, and Key Performance Indicators (KPIs) generated by Tanzu SQL for VMs component VMs.

For more information about logging and metrics in VMware Tanzu Application Service for VMs, see Overview of Logging and Metrics.

About Metrics

Metrics are regularly-generated log entries that report measured component states. The default metrics polling interval is 30 seconds for MySQL instances. For the service broker, the default is 60 seconds.

You can configure the MySQL instance interval in Configure Monitoring in the Tanzu SQL for VMs tile. For more information, see Configure Monitoring.

Metrics are long, single lines of text with the format:

origin:"p.mysql" eventType:ValueMetric timestamp:1496776477930669688 deployment:"service-instance_2b5a001f-2bf3-460c-aee6-fd2253f9fb0c" job:"mysql" index:"b09df494-b731-4d06-a4b0-c2985ceedf4c" ip:"10.0.8.4" valueMetric:<name:"/p.mysql/performance/open_files" value:24 unit:"file" >

Access MySQL Metrics

To access MySQL metrics:

• Use the Indicator Protocol Dashboard
• Use Log Cache

Use the Indicator Protocol Dashboard

You can use the Indicator Protocol dashboard to view Key Performance Indicators (KPIs) for Tanzu SQL for VMs service instances. The dashboard includes a graphical representation of the KPIs and information about recommended alert thresholds.

For more information about the Indicator Protocol dashboard, see Indicator Protocol Dashboard (Beta). For information about Tanzu SQL for VMs KPIs, see KPIs for MySQL Service Instances below.

To access KPIs using the Indicator Protocol dashboard:

1. Install the Healthwatch tile in Ops Manager. See Installing and Configuring Healthwatch.
2. Enable the Indicator Protocol add-on in Ops Manager. See Enable the Indicator Protocol Add-on.

3. View the Indicator Protocol Dashboard by navigating to:

   https://healthwatch.YOUR-SYSTEM-DOMAIN/indicator-dashboards
   

The following image shows an example of the Indicator Protocol dashboard for a highly available (HA) cluster service instance:

View a larger version of this image

Use Log Cache

To access metrics for Tanzu SQL for VMs service instances, you can use Loggregator’s Log Cache feature with the Log Cache CLI plugin. Log Cache is enabled by default.

Note: To use this feature the V2 Firehose must be enabled and Enable Log Cache syslog ingestion must be disabled in the TAS for VMs tile. For more information about configuring these checkboxes, see Enable Syslog Forwarding.

To access metrics for on-demand service instances:

1. Install the cf CLI plugin by running:

   cf install-plugin -r CF-Community "log-cache"

2. To access metrics for a service instance, run:

   cf tail SERVICE-INSTANCE-NAME

   Two useful flags to append to this command are:
   • -f, --follow: Append metrics logs to stdout as they are generated, rather than returning a fixed number of metrics or metrics over a fixed interval.
   • --json: Output metrics logs as envelopes in JSON format. For a complete list of cf tail options, see the Log Cache CLI repository in GitHub.
   Where SERVICE-INSTANCE-NAME is the name of your service instance.
   
   For example:

   $ cf tail -f my-instance | egrep 'connected|available|persistent_disk_used_percent'
   2019-05-17T11:25:59.48-0700 [my-instance] GAUGE /p.mysql/available:1.000000 boolean
   2019-05-17T11:26:29.49-0700 [my-instance] GAUGE /p.mysql/system/persistent_disk_used_percent:17.000000 percentage
   2019-05-17T11:26:29.49-0700 [my-instance] GAUGE /p.mysql/performance/threads_connected:**6**.000000 connection
   2019-05-17T11:26:59.50-0700 [my-instance] GAUGE /p.mysql/available:1.000000 boolean
   2019-05-17T11:27:29.50-0700 [my-instance] GAUGE /p.mysql/system/persistent_disk_used_percent:17.000000 percentage
   2019-05-17T11:27:29.50-0700 [my-instance] GAUGE /p.mysql/performance/threads_connected:**7**.000000 connection
   

   For more information about the metrics output, see the Key Performance Indicators and Component Metrics sections below.

For more information about how to enable Log Cache and about the cf tail command, see Enable Log Cache.

KPIs for MySQL Service Instances

KPIs are metrics for MySQL service instances that you can monitor for two purposes:

• To ensure high performance.

• To discover emerging issues.

KPIs can be either raw component metrics or derived metrics generated by applying formulas to raw metrics.

VMware provides the following KPIs as general alerting and response guidance for typical Tanzu SQL for VMs installations. VMware recommends that you alter the alert measures by observing historical trends. You can also create your KPIs that are specific to your environment using the available component metrics.

For a list of all the Tanzu SQL for VMs component metrics, see Component Metrics below.

Server Availability

Persistent Disk Used

Ephemeral Disk Used

CPU Utilization Percent

Connections

Queries Delta

Highly Available Cluster WSREP Ready

Highly Available Cluster WSREP Cluster Size

Highly Available Cluster WSREP Cluster Status

Hours Since Last Successful Backup

Component Metrics

In addition to the above KPIs, the MySQL service emits the followings metrics for monitoring and alerting:

• MySQL Metrics
• Disk Metrics
• Leader-Follower Metrics
• Highly Available Cluster Metrics

MySQL Metrics

The metrics that all Tanzu SQL for VMs service instances emit:

Disk Metrics

The disk usage metrics that all Tanzu SQL for VMs services emit:

Leader-Follower Metrics

The metrics that leader-follower VMs emit:

Highly Available Cluster Metrics

The metrics that HA clusters emit: