Azure Table Storage is a NoSQL key-value store for structured, non-relational data. Cloudmon monitors capacity, table and entity counts, transactions, and latency across all your Table Storage resources.
Azure Table Storage is used to store structured data that does not require complex joins or foreign keys and is commonly used for configuration data, user profiles, and application metadata. Cloudmon automatically discovers all Table Storage resources linked to your monitored Azure account. Navigate to Cloud → Azure → [Select Account] → Azure Table Storage to view the full list. Click any resource name to open its detailed monitoring view.
The list displays all discovered Table 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 Table Storage resource opens its detail page. The overview displays key details, including the Primary Location, SKU, Resource Group, Subscription, Status, and Monitoring Status, among other configuration and availability information.
Cloudmon collects key metrics such as Table Capacity, Table Count, Table Entity 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 tables within the selected resource by name. Use the search bar to filter by table name.
Surfaces actionable insights from Azure Advisor specific to this Table Storage resource. Recommendations may include enabling zone-redundant storage for improved availability, enforcing a minimum TLS version for secure connections, or restricting public network access to reduce the attack surface. 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 |
| Table Entity Count growing unexpectedly | An application may be inserting data without a retention or cleanup policy | Review the Tables section to identify the affected table and check application insert logic |
| High latency on table queries | Large numbers of small transactions or poorly partitioned data can increase query latency | Review Table Count and Transactions metrics together to identify heavy query patterns |