Loading...

Azure Storage

Azure Storage

1.0

DiscoveryDiscovery » pandorafms.azure.storage
Last update: 2026-11-16 12:00:17
This addon download is limited to licensed users

Description

The Azure Storage Discovery addon lists the storage accounts of a Microsoft Azure subscription or a single Resource Group and turns their Azure Monitor metrics into Pandora FMS agents and modules. It covers account capacity, quota and occupancy, the Blob, File, Queue and Table services, per-file-share usage and optional per-container capacity. By default it creates one agent per storage account, and it can consolidate every account onto a single target agent.

Additional information

The addon runs as a Discovery task with a Microsoft Entra service principal stored as an Azure credential. It lists the storage accounts of the subscription, or of one exact Resource Group, reads their metrics from Azure Monitor and returns the generated agents and modules for Pandora FMS to create.

By default each storage account becomes an agent named with the account name and an optional prefix. When per-account creation is disabled, every module is attached to a single target agent and the account name is prepended to the module names. Each agent carries an Azure Storage Connection module and one module per enabled metric family.

Coverage is selected through independent switches for the storage account itself and the Blob, File, Queue and Table services. File share metrics add used capacity, quota and occupancy per share. Advanced container metrics add per-container used capacity, blob count and blob capacity percentage, but only when the ContainerLevelCapacityMetrics rule is enabled in Azure; the addon reports the rule state and never enables it. Capacity quota and occupancy modules are created for Standard accounts.

A task-scoped cache keeps the discovered accounts between runs, and an account that is no longer discoverable keeps its agent and reports its connection module as 0 until the cache is rebuilt. Allow and deny regular expressions filter the final module names, the container regular expression filters container names, and agents can be created in autodisable mode. The addon only reads account state and metrics and does not change the Microsoft Azure configuration.

What it allows you to do
- Create one Pandora FMS agent per storage account through a Discovery task, or consolidate every account onto one target agent.
- Monitor account capacity, quota, occupancy, traffic, latency and availability.
- Monitor Blob, File, Queue and Table service capacity, object counts, traffic, latency and availability.
- Monitor used capacity, quota and occupancy per file share.
- Add per-container capacity and blob count modules when advanced metrics are enabled in Azure.
- Filter discovered accounts, containers and generated modules.

What it monitors
- Storage account reachability
- Account used capacity, quota and occupancy percentage
- Account transactions, ingress, egress, latency and availability
- Blob capacity, object and container counts, index capacity, traffic, latency and availability
- File capacity, object, share and snapshot counts, quota, traffic, latency and availability
- Per-file-share used capacity, quota and occupancy
- Queue capacity, queue and message counts, traffic, latency and availability
- Table capacity, table and entity counts, traffic, latency and availability
- Per-container used capacity, blob count and blob capacity percentage
- Data Lake Storage Gen2 state

How it works
A Discovery task runs the addon with a Microsoft Entra service principal credential retrieved from the Pandora FMS credential store. The addon lists the storage accounts of the subscription, or of the selected Resource Group, through the Microsoft Azure Resource Manager API and reads their Azure Monitor metrics. With per-account creation enabled, each account becomes an agent named with an optional prefix; when it is disabled, every module is attached to a single target agent with the account name prepended to the module names. Metric families are enabled independently, and capacity quota and occupancy modules are created for Standard accounts. A task-scoped cache of the discovered accounts is reused between runs, and an account 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
- Account capacity, traffic and service health 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 storage account.
- New accounts in the selected scope are incorporated on the next task run without reconfiguring the task.
- Blob, File, Queue, Table and file-share data are consolidated into one view per storage account.

Use cases
- Cloud and platform operations teams that monitor storage capacity and traffic in Microsoft Azure.
- Environments where storage accounts are watched alongside other cloud and on-premise infrastructure.
- Teams that need to detect capacity growth, availability drops or latency increases before they affect applications.
- Teams that want one consistent monitoring layout across many storage accounts.

Requirements
- A Pandora FMS server with Discovery enabled and a console to define the task.
- A Microsoft Azure subscription containing the storage accounts to monitor.
- A Microsoft Entra service principal stored as an Azure credential in the Pandora FMS credential store, with the Reader and Monitoring Reader roles over the subscription or Resource Group.
- The ContainerLevelCapacityMetrics rule enabled in Azure for the accounts where per-container metrics are required.
- A target agent group whose identifier is greater than 0; the All group cannot be used.
- A monitoring interval for the generated agents.

Tags

Categories

No data available in table

Please apply a filter to display the data.

Loading

This addon download is limited to licensed users