Azure Blob Storage is Azure's object storage service for unstructured data such as documents, images, logs, and backups. Cloudmon monitors capacity, container counts, transaction volume, and latency across all your Blob Storage resources.
Azure Blob Storage stores large volumes of unstructured data and is commonly used for backups, media files, logs, and application data. Cloudmon automatically discovers all Blob Storage resources linked to your monitored Azure account. Navigate to Cloud → Azure → [Select Account] → Azure Blob Storage to view the full list. Click any resource name to open its detailed monitoring view.
The list displays all discovered Blob Storage resources with the following details:
| Column | Description |
| Name | The name of the resource as configured in Azure. |
| Kind | The storage account type, for example StorageV2. |
| Resource Group | The Resource Group this resource belongs to. |
| Location | The Azure region where the resource is deployed. |
| Creation Time | The date and time the resource was created. |
| Size | The replication and performance tier, for example Standard_LRS or Standard_GZRS. |
| Actions | Toggle to enable or disable monitoring, and an edit icon to update the configuration. |
Selecting a Blob Storage resource opens its detail page. The overview displays the Primary Location, SKU, Public Network Access status, Location, Resource Group, Subscription, Creation Time, Status, Monitoring Status, Polling Interval, and last Updated At timestamp.
Cloudmon collects key metrics such as Blob Capacity, Blob Count, Container Count, Transactions, Ingress, and Egress, among other performance indicators, including latency and availability. These are displayed as time-series charts for the selected time period.
Lists all containers within the selected resource. Each entry shows the container name, Lease Status, Lease State, Legal Hold status, and Last Modified timestamp.
Surfaces actionable insights from Azure Advisor specific to this Blob Storage resource. Recommendations may include enabling soft delete to protect against accidental data loss, configuring lifecycle management policies to move unused blobs to cooler storage tiers, enabling blob versioning for data protection, or restricting anonymous public access to containers. Each recommendation shows its impact level and category across Cost, Security, High Availability, Performance, and Operational Excellence.
| Symptom | Likely Cause | Fix |
| Resource not appearing in the list | Discovery has not run since the resource was created, or the service was not selected during Azure account setup | Trigger a manual rediscovery from Settings → Monitoring → Probes → Azure, or edit the account to enable the missing service |
| Metrics showing no data | The resource may have had no activity during the selected time window, or polling has not completed yet | Wait for the next polling cycle or reduce the selected time range to a period with known activity |
| Availability dropping below 100% | The storage service experienced a transient error or outage during the monitored period | Review the metric timeline to identify when the drop occurred and cross-reference with Azure Service Health |
| Alarms not triggering as expected | Alarm thresholds may not be configured for this resource | Go to Settings and add or review alarm triggers |
| Blob Count is growing unexpectedly | Automated processes may be creating blobs without a cleanup or lifecycle policy | Review the Blob Containers section to identify the affected container and check for missing lifecycle management policies in the Azure portal |
| High Ingress with no expected uploads | A misconfigured application may be writing data in an uncontrolled loop | Cross-reference the Ingress spike time with application logs to identify the source |