Azure Database for MySQL Monitoring

Azure SQL Database is Microsoft's cloud database service. Based on SQL Server database technology and built on Microsoft's Windows Azure cloud computing platform, Azure SQL Database enables organizations to store relational data in the cloud and quickly scale the size of their databases.

What You Can Monitor

Opsview's Azure Database for MySQL monitoring provides all the metrics to track your MySQL databases. MySQL service checks include active connections, CPU Percentage, memory and storage metrics.

Service Checks

Service Check Name	Description	Default Thresholds (Warning, Critical)	UOM
Azure - MySQL - Active Connections	The average number of active connections [Default Timespan = 5mins, Default Check Interval = 5mins]	N/A	N/A
Azure - MySQL - CPU Percent	The CPU usage [Default Timespan = 5mins, Default Check Interval = 5mins]	cpu_percent=70,90	%
Azure - MySQL - Connections Failed	The the number of failed connections [Default Timespan = 5mins, Default Check Interval = 5mins]	N/A	N/A
Azure - MySQL - Memory Percent	The memory usage [Default Timespan = 5mins, Default Check Interval = 5mins]	memory_percent=70,90	%
Azure - MySQL - Storage Limit	The average storage limit [Default Timespan = 5mins, Default Check Interval = 5mins]	N/A	B
Azure - MySQL - Storage Percent	The storage usage [Default Timespan = 5mins, Default Check Interval = 5mins]	storage_percent=70,90	%
Azure - MySQL - Storage Used	The storage usage in bytes [Default Timespan = 5mins, Default Check Interval = 5mins]	N/A	B
Azure - MySQL - IO Consumption Percent	The average IO consumption [Default Timespan = 5mins, Default Check Interval = 5mins]	io_consumption_percent=70,90	%
Azure - MySQL - Server Log Storage Percent	The average server log storage usage percentage [Default Timespan = 5mins, Default Check Interval = 5mins]	serverlog_storage_percent=70,90	%
Azure - MySQL - Server Log Storage Used	The average server log storage usage [Default Timespan = 5mins, Default Check Interval = 5mins]	N/A	B
Azure - MySQL - Server Log Storage Limit	The average server log storage limit [Default Timespan = 5mins, Default Check Interval = 5mins]	N/A	B
Azure - MySQL - Replication Lag	The average replication lag in seconds [Default Timespan = 5mins, Default Check Interval = 5mins]	N/A	s
Azure - MySQL - Backup Storage Used	The average backup storage usage [Default Timespan = 15mins, Default Check Interval = 15mins]	N/A	B
Azure - MySQL - Network Out	The number of bytes sent across active connections [Default Timespan = 5mins, Default Check Interval = 5mins]	N/A	B
Azure - MySQL - Network In	The number of bytes received across active connections [Default Timespan = 5mins, Default Check Interval = 5mins]	N/A	B

NOTE: The "Default Timespan" given for these Service Checks refers to the time period we use when retrieving metrics from Azure.

NOTE: See details about Nagios thresholds here.

Azure Database for MySQL Monitoring Prerequisites

The monitoring plugin for this Opspack has been tested with Python 2.7. In order for the Opspack to run, you will need to have some Python packages installed by running the pip python package tool.

If a cryptography error occurs when trying to install the Azure packages, you can run the commands which should fix the problem.

Debian and Ubuntu

sudo apt-get install build-essential libssl-dev libffi-dev python-dev python-pip

CentOS and RHEL

sudo yum install gcc libffi-devel python-devel openssl-devel python-pip

Common

When python-pip is installed, you can then run:

sudo pip install --upgrade pip==9.0.2
sudo pip install --upgrade setuptools
sudo pip install --upgrade requests
sudo pip install nagiosplugin
sudo pip install azure
sudo pip install azure-monitor

Azure Database for MySQL Monitoring Setup

To monitor you Azure environment, you need to configure it for monitoring

This requires Administrator access on Azure. You need to retrieve the following credentials:

Subscription ID
Tenant/Directory ID
Client/Application ID
Secret Key

Step 1: Find Subscription ID

The Subscription ID can be found in the Subscriptions section under the All services section from the Azure dashboard

Step 2 : Find the Tenant/Directory ID

The Tenant/Directory ID can be found in the Azure Active Directory under the Properties section from the Azure dashboard

Step 3: Find the Client/Application ID for your application

You need to create and register your application if you haven't already. Use the following documentation from Microsoft: Create an Azure Active Directory application

The Client/Application ID can be found in Azure Active Directory under the App registrations section from the Azure dashboard

Step 4: Generate the Secret Key for your application

You will need to create a Secret Key for your application, once this has been created its value will be hidden so save the value during creation

To create the Secret Key, select your application from the list, select the Settings within your application and then select the Keys option

There you can create a new key by adding the description and expiration period and the value will be generated

Step 5: Provide access to the subscription you wish to monitor

Navigate to the Subscriptions section and select the Subscription you selected before

In the Subscription to be monitored, click Access Control (IAM)

Then click the Add button, select Monitoring Contributor and select the application

If you are running more than one subscription these steps will need to be done for each one you wish to monitor

Setup and Configuration

To configure and utilize this Opspack, you simply need to add the 'Cloud - Azure - Virtual Machines' Opspack to your Opsview Monitor system

Step 1: Add the Host Template

Add the Cloud - Azure - MySQL Server Host Template to your Opsview Monitor host.

For more information, refer to Opsview Knowledge Center Adding Host Templates to Hosts.

Step 2: Add and configure variables required for this host

Add 'AZURE_CREDENTIALS' to the host and set the Resource Group as its variable value, then override the Subscription ID, Client ID, Secret Key and Tenant ID to match the values retrieved earlier.