Download PDF
Download page Azure Database for MariaDB.
Azure Database for MariaDB
Microsoft Azure Database services provide fully managed relational, NoSQL, and in-memory databases with automated infrastructure management. Azure Database for MariaDB is a relational database service based on the open-source MariaDB Server engine.
In Cisco Cloud Observability, Azure Database for MariaDB is categorized as a database instance, or a collection of databases. Metrics are collected for the single database instance.
You must configure cloud connections to monitor this entity. See Configure Azure Cloud Connection. For detailed visibility, such as query profiling and streamlined troubleshooting, install Database Monitoring.
Cisco Cloud Observability displays Azure entities on the Observe page. Metrics are displayed for specific entity instances in the list and detail views.
This document contains references to third-party documentation. Splunk AppDynamics does not own any rights and assumes no responsibility for the accuracy or completeness of such third-party documentation.
Detail View
To display the detail view for an Azure Database for MariaDB entity:
- Navigate to the Observe page.
- Under Database & Storage, click SQL Database Instances.
The list view now displays. - Click the Azure button to display only Azure database entities.
- From the list, click a database Name to display the detail view.
The detail view displays metrics, key performance indicators, and properties (attributes) related to the database you selected.
Metrics and Key Performance Indicators
Cisco Cloud Observability displays the following metrics and key performance indicators (KPIs) for Azure Database for MariaDB. See Monitoring in Azure Database for MariaDB.
Display Name | Source Metric | Description |
Database Connections
|
| The number of failed connections to the server. |
active_connections | The number of active connections to the server. | |
Replica Lag (Seconds) | seconds_behind_master | The number of seconds the replica server is lagging against the source server. (Not applicable for Basic tier servers) |
Backup Storage Used (Bytes) | backup_storage_used | The amount of backup storage used. This metric represents the sum of storage consumed by all the full database backups, differential backups, and log backups retained based on the backup retention period set for the server. The frequency of the backups is service managed and explained in the concepts article. For geo-redundant storage, backup storage usage is twice that of the locally redundant storage. |
CPU Utilization (%) |
| The percentage of CPU in use. |
IO Utilization (%) |
| The percentage of IO in use. (Not applicable for Basic tier servers) |
Memory Utilization (%) |
| The percentage of memory in use. |
Server Log Storage
| serverlog_storage_limit | The maximum server log storage for this server. |
| The percentage of server log storage used out of the server's maximum server log storage. | |
serverlog_storage_usage | The amount of server log storage used. | |
Storage
| storage_limit | The maximum storage for this server. |
| The percentage of storage used out of the server's maximum. | |
storage_used | The amount of storage in use. The storage used by the service may include the database files, transaction logs, and the server logs. | |
Network Traffic (Bytes)
|
| Network In across active connections. |
| Network Out across active connections. |
Properties (Attributes)
Cisco Cloud Observability displays the following properties for MariaDB.
Display Name | Property Name | Description |
Storage Encrypted |
| Defines if infrastructure encryption is enabled. When infrastructure encryption is enabled, the data at rest is encrypted twice using FIPS 140-2 compliant Microsoft managed keys. |
Created At |
| The earliest restore point creation time (ISO8601 format). |
Size (MB) |
| The max storage allowed for a server. |
Backup Retention Days |
| The backup retention days for the server. |
State |
| A state of a server that is visible to the user. |
ID |
| Fully qualified resource ID for the resource. Example: /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/{resourceProviderNamespace}/{resourceType}/{resourceName} |
SKU Name |
| The name of the sku, e.g. Standard_D32s_v3. |
SKU Tier |
| The tier of the particular SKU, e.g. GeneralPurpose. |
Replication Role |
| The replication role of the server. |
Geo Redundant Backup |
| Defines whether or not geo redundant backup is enabled. |
Version |
| The server version. |
Name |
| The resource name. |
Type |
| The type of managed service identity. |
Host |
| The fully qualified domain name of a server. |
Location | location | The location the resource resides in. |
Subscription ID | N/A | The cloud account ID where the resource is assigned. |
Resource Group | N/A | The name of the resource group. |
Storage Auto Grow |
| Gets or enables Storage Auto Grow. Possible values include: Enabled , Disabled . |
Master Server ID |
| The master server id of a replica server. |
Retention and Purge Time-To-Live (TTL)
For all cloud and infrastructure entities, the retention TTL is 180 minutes (3 hours) and the purge TTL is 525,600 minutes (365 days).
Microsoft Azure, the Microsoft Azure logo, Azure, and any other Microsoft Azure Marks used in these materials are trademarks of Microsoft Corporation or its affiliates in the United States and/or other countries.