Monitoring Azure Storage
Unlock the full potential of your Azure Storage with Nodinite. This guide empowers you to monitor and manage Azure Storage resources—File Shares, Blob Containers, Queues, and Storage Accounts—efficiently and securely, all from a single pane of glass.
On this page, you will:
✅ Proactively monitor and receive real-time alerts for all Azure Storage types
✅ Control everything centrally—no need for direct Azure portal access
✅ Enable role-based access and self-service for your teams
✅ Automate discovery and dynamic management of Queues
✅ Reduce risk and human error with secure, delegated access
Nodinite monitors these Azure Storage types:
This page explains how Nodinite lets you monitor Azure Storage from one or more role-based Monitor Views. Nodinite evaluates the state of your Azure Storage content using user-defined thresholds—globally or specifically. You can manage your configured Azure Storage resources and use remote commands (Actions) to resolve issues quickly. For more on remote management, see Managing Azure Storage.
This image shows monitored Azure Storage resources in a Nodinite Monitor View.
Monitoring Features
- State Evaluation — Instantly see if your storage is healthy, based on your own thresholds.
- Time-based Monitoring — Prevent stockpiling by tracking file/message age.
If Nodinite can't check your Azure Storage items' state, no one else can use them either.
- Time-based Monitoring — Prevent stockpiling by tracking file/message age.
- Automatic Queue Discovery — Nodinite Azure Agent uses the Azure REST API to dynamically manage queues.
- Category-based Monitoring — Organize and group your monitored resources using Nodinite Categories.
- Role-based Access — Share access to individual items securely with Monitor Views.
State Evaluation for Azure Storage Items
Nodinite creates a Resources entry for each monitored Azure Storage. For example, if you monitor one queue, two file shares, and three blob containers, you will see six Resources in Nodinite.
The Resources name matches the user-defined configuration name (for files and blob containers) or the deployed Azure Storage Queue name.
Nodinite groups monitored Azure Storages into these 'Azure Storage' Categories:
This image shows the list of monitored categories
Explore many other Azure-related Categories in the Azure Logging and Monitoring Overview.
- The user-defined configuration name is the Application name:
This image shows the application path for a monitored resource
Nodinite evaluates each item (presented as a Resource) with a state (OK, Warning, Error, Unavailable).
You can override the evaluation process by configuring the Expected State option for any Nodinite [Resource][].
File Shares
For File Shares, Nodinite evaluates state as follows:
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available |
|
Review prerequisites | |
| Error | Error threshold breached |
|
Edit thresholds List Files |
|
| Warning | Warning threshold breached |
|
Edit thresholds List Files |
|
| OK | Within user-defined thresholds |
|
For example, if you configure a business-critical file share for monitoring and someone removes it (e.g., a failed DevOps deployment), Nodinite immediately alerts you.
This image shows an unavailable Azure Storage configuration
Blob Containers
For Blob Containers, Nodinite evaluates state as follows:
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available |
|
Review prerequisites | |
| Error | Error threshold breached |
|
Edit thresholds List Files |
|
| Warning | Warning threshold breached |
|
Edit thresholds List Files |
|
| OK | Within user-defined thresholds |
|
For example, if you monitor a Blob Container and content is added but never removed (e.g., unprocessed orders), Nodinite alerts you before stockpiling becomes a problem.
This image shows old files detected according to the 'Warning' threshold.
Queues
For Queues, Nodinite evaluates state as follows:
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available |
|
Review prerequisites | |
| Error | Error threshold breached |
|
Edit thresholds List Files |
|
| Warning | Warning threshold breached |
|
Edit thresholds List Files |
|
| OK | Within user-defined thresholds |
|
For example, if you monitor a queue and messages are never removed, Nodinite alerts you before stockpiling impacts your business.
This image shows old messages detected according to the 'Error' threshold.
Storage Account
The Storage Account Resource helps you quickly identify configuration issues—such as invalid connection strings or revoked access rights.
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available |
|
Review prerequisites | |
| OK | Connection and credentials are valid |
|
Alert History for Azure Storage
When you analyze root causes, you can review how often Azure Storage issues occur. If your Monitor View allows, search for historical state changes for all or individual Azure Storage resources. See Add or manage Monitor View for more details.
| Search | Resource history |
|---|---|
 |
 |
| This image shows search for alert history for all resources in the Monitor View | This image shows alert history for the selected Azure Storage item (in this case, a Blob Container) |
Frequently Asked Questions
Use the troubleshooting guide to find FAQs and answers to known problems.
How do I enable monitoring of Azure Storage
To monitor Azure Storage, check the Enable monitoring box (default is checked). See the 'Configuration' user guide for details.
The screenshot shows the remote configuration form, available from the Monitoring Agents administration page.
This image shows monitoring disabled for Azure Storage.