Azure SQL

The plugin lists the SQL servers and databases of the subscription, or of a single Resource Group when discovery is narrowed to one, and reads their Azure Monitor metrics. A Discovery task creates one agent per database, named from the server and the database with an optional prefix, or a single target agent when per-database creation is disabled; in consolidated mode the server and the database are prepended to each module name. Generated agents report Azure as their operating system and inherit the task group and interval.

Each discovered database carries a reachability module, a database online module and one module per enabled metric family. The families are enabled independently: performance, storage, connections, TempDB and XTP, and deadlocks. The plugin reads the metrics from Azure Monitor and only creates a metric module when the database exposes that metric and supports the aggregation used.

Authentication uses a Microsoft Entra service principal stored as an Azure credential in the Pandora FMS credential store. Agent autodisable mode and a prefix for generated module names are configurable. A discovered database is cached, and a database that is no longer discoverable keeps its connection module at 0 until the cache is rebuilt. The plugin only reads state and metrics and never changes the Microsoft Azure configuration.

What it allows you to do

- Create Pandora FMS agents for the discovered Azure SQL Database resources through a Discovery task.
- Monitor CPU, DTU and I/O performance, storage usage and connections per database.
- Monitor TempDB and XTP usage and deadlock counts.
- Choose between one agent per database and a single consolidated agent.
- Keep a database that is no longer discoverable visible through its connection module.

What it monitors

- Database reachability and online state
- CPU, DTU and physical data read usage
- Log write, sessions and workers usage
- Storage used and allocated
- Successful, failed and firewall-blocked connections
- TempDB data and log usage
- XTP storage usage
- Deadlocks

How it works
A Discovery task runs the plugin with a stored Microsoft Entra credential. The plugin lists the SQL servers and databases of the subscription, or of the selected Resource Group, and reads their Azure Monitor metrics. With per-database creation enabled, each discovered database becomes an agent named from its server and database with an optional prefix; when it is disabled, every module is attached to a single target agent with the server and database prepended to the module names. A cached database list can be reused between runs, and a database that is no longer discoverable keeps its connection module at 0 until the cache is rebuilt. The generated agents and modules are returned for the Discovery task to create them.

Benefits

- Database state and performance become visible in the same platform as the rest of the monitored infrastructure.
- Removes the manual creation and maintenance of agents and modules for each database.
- Newly discovered databases are incorporated on the next task run without reconfiguring the task.
- Performance, storage, connection and TempDB data are consolidated into one view per database.

Use cases

- Database and cloud operations teams that monitor the health and performance of Azure SQL Database resources in Microsoft Azure.
- Environments where Azure databases are watched alongside other cloud and on-premise infrastructure.
- Teams that need to detect unavailable databases, storage growth or blocked connections before they affect users.

Requirements

- A Pandora FMS server with Discovery enabled and a console to define the task.
- A Microsoft Azure subscription containing Azure SQL databases.
- A Microsoft Entra service principal stored as an Azure credential in the Pandora FMS credential store, with read access to the subscription or Resource Group and its Azure Monitor metrics.
- A target agent group whose identifier is greater than 0; the `All` group cannot be used.
- A monitoring interval for the generated agents.

Compatibility
Plugin version 1.0. Communicates with the Microsoft Azure SQL management and Azure Monitor endpoints. Distributed as a self-contained Discovery application, so no additional runtime has to be installed for a normal run.

Limitations

- The resource group, server and database filters use exact, case-insensitive matches rather than regular expressions.
- Sovereign or custom Azure clouds are not validated; the public Azure endpoints are used by default.
- No host operating system compatibility has been validated.
- A metric module is created only when the database exposes the metric and supports the aggregation used.
- A database that is no longer discoverable keeps its agent and reports its connection module as 0 until the entity cache is rebuilt.
- The plugin only reads state and metrics and does not change the Microsoft Azure configuration.