MySQL Flexible Server
QuickStart
To monitor your MySQL Flexible Server's system metrics like CPU Usage, Memory Usage, and Storage with SigNoz, configure Diagnostic Settings in Azure to export metrics and logs to Event Hub, and set up the OpenTelemetry Collector to pull data from Event Hub and send it to SigNoz.
Overview
In this guide, you'll learn how to monitor MySQL Flexible Server system metrics using SigNoz. This is achieved by pushing telemetry data to Azure Event Hub and configuring the Central Collector (OpenTelemetry Collector) to receive and forward it to SigNoz.
⚠️ Note: MySQL Flexible Server does not support SQL Monitoring Profile. Instead, it supports Diagnostic Settings to export logs and metrics to an Event Hub.
Prerequisites
Make sure the following are set up:
- An Azure subscription with a running MySQL Flexible Server
- Central Collector Setup
- A Diagnostic Settings configuration in Azure for your MySQL Flexible Server that sends metrics/logs to an Event Hub
Setup
Once prerequisites are in place, follow these steps:
Step 1: Enable Diagnostic Settings for MySQL Flexible Server
- Go to your MySQL Flexible Server resource in Azure.
- Select Diagnostic Settings.
- Create a new diagnostic setting:
- Choose Metrics and/or Logs (based on what you want to monitor)
- Destination: Stream to an Event Hub
- Select an existing Event Hub Namespace and Event Hub Name or create one.
- Save the diagnostic setting.
Step 2: Update Central Collector to Pull from Event Hub
In your
otel-collector-config.yaml
, update the metrics pipeline or logs pipeline to include theazureeventhub
receiver.A sample snippet:
receivers: azureeventhub: connection_string: "<EVENT_HUB_CONNECTION_STRING>" format: "azure" processors: batch: exporters: otlp: endpoint: "ingest.<region>.signoz.cloud:443" tls: insecure: false headers: "signoz-ingestion-key": "<ingestion-key>" service: pipelines: metrics: receivers: [azureeventhub] processors: [batch] exporters: [otlp] logs: receivers: [azureeventhub] processors: [batch] exporters: [otlp]
Restart the Central Collector to apply the changes.
Troubleshooting
- Ensure Event Hub is receiving data (check message count/metrics in Event Hub).
- Verify the Central Collector is running and has the correct
connection_string
. - Make sure the SigNoz collector endpoint is accessible and listening.
- Check for errors in Central Collector logs for misconfigurations.
Last updated: April 24, 2025