Monitoring Azure Storage

Unlock the full potential of your Azure Storage with Nodinite. This guide shows how you monitor and manage Azure Storage resources (File Shares, Blob Containers, Queues, and Storage Accounts) efficiently and securely, 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, with 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:

• Storage Account
• File Shares
• Blob Containers
• Queues

Nodinite lets you monitor Azure Storage from one or more role-based Monitor Views. The Azure Monitoring Agent evaluates the state of your Azure Storage content using user-defined thresholds, set globally or specifically, and alerts you through Alarm Plugins. Use Remote Actions to resolve issues quickly; see Managing Azure Storage.

This image shows monitored Azure Storage resources in a Nodinite Monitor View.

Diagram: The agent evaluates each Azure Storage Resource into OK (green), Warning (yellow), or Error and Unavailable (red) by the age of files, blobs, or messages; Warning and Error raise alerts, and you resolve problems with Remote Actions.

Monitoring Features

• State Evaluation — Instantly see if your storage is healthy, based on your own thresholds.
  • Time-based Monitoring — Prevent stockpiling by tracking file and message age.

  If Nodinite can't check your Azure Storage items' state, no one else can use them either.

• Automatic Queue Discovery — The Nodinite Azure Agent uses the Azure REST API to manage queues dynamically.
• Category-based Monitoring — Organize and group your monitored resources using Nodinite Categories.
• Role-based Access — Share access to individual items securely with Users through Monitor Views.

State Evaluation for Azure Storage Items

Nodinite creates a Resource for each monitored Azure Storage item. For example, if you monitor one queue, two file shares, and three blob containers, you see six Resources in Nodinite.

• The Resource name matches the user-defined configuration name (for files and blob containers) or the deployed Azure Storage Queue name.
• Nodinite groups monitored Azure Storage items into these 'Azure Storage' Categories:
  • File Shares
  • Blob Containers
  • Queues
  • Storage

This image shows the list of monitored Azure Storage 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), and the Monitoring Service collects the result. You can override the evaluation by configuring the Expected State for any Nodinite Resource.

File Shares

For File Shares, Nodinite evaluates state as follows:

For example, if you configure a business-critical file share for monitoring and someone removes it (for example, after 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:

For example, if you monitor a Blob Container and content is added but never removed (such as unprocessed orders), Nodinite alerts you before stockpiling becomes a problem. If you also log to Blob Storage, see Azure Costs for Blob Storage and Event Hub.

This image shows old files detected according to the 'Warning' threshold.

Queues

For Queues, Nodinite evaluates state as follows:

For example, if you monitor a queue and messages are never removed, Nodinite alerts you before stockpiling impacts your business. For Azure Service Bus queues, see Azure Service Bus.

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.

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 Add Azure Storage section of the Configuration 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.

Next Steps

• Managing Azure Storage
• Configure the Azure Monitoring Agent
• Add or manage Monitor View - Share Azure Storage monitoring with your teams

Related Topics

• Azure Monitoring Agent Overview
• Azure Logging and Monitoring Overview
• Prerequisites
• Resources
• Categories
• Applications
• Azure Service Bus
• Azure Costs for Blob Storage and Event Hub