New Relic's integrations include an integration for reporting your Microsoft Azure Database for MariaDB metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported.
New Relic gathers data from the Azure Database for MariaDB service, which provides a fully managed, enterprise-ready database as a service. MariaDB provides predictable performance and scalability for applications using open-source tools and platforms.
Using New Relic, you can:
- View Azure Database for MariaDB data in pre-built dashboards.
- Run custom queries and visualize the data in the New Relic UI.
- Create alert conditions to notify you of changes in data.
Follow standard procedures to activate your Azure service in New Relic Infrastructure, using the generic Reader role.
New Relic queries your Azure Database services according to a default polling interval, which varies depending on the integration. For Azure Database for PostgreSQL integrations:
- Polling interval: 5 minutes (maximum recommended polling frequency: 1 hour)
- Resolution: 1 data point per minute
You can change the polling frequency and filter data using configuration options.
In New Relic, data about a single database is attached to the
AzureMariaDbServerSample event type, with a provider value of
This integration collects the following metric data.
Count of active connections.
Backup storage used, in bytes.
Count of failed connections.
Percentage of CPU used.
Percentage of I/O consumption used.
Percentage of memory used.
Network Out across active connections, in bytes.
Network In across active connections, in bytes.
Replication lag, in seconds.
Server log storage limit, in bytes.
Percentage of server log storage used.
Server log storage used, in bytes.
Amount of storage available, in bytes.
Percentage of available storage used.
Amount of storage used, in bytes.
After March 2022, we're discontinuing support for several capabilities, including inventory data for cloud integrations. For more details, including how you can easily prepare for this transition, see our Explorers Hub post.
masterServerId(only for a replica server)
replicaCapacity(only for a replica server)
replicationRole(only for a replica server)