If you notice that one or more of your Azure Storage object monitors have been terminated or are no longer active in Site24x7, this is expected behaviour under certain conditions.
How termination works
Azure Storage object monitors in Site24x7 remain active only as long as at least one active resource exists within the associated Storage Account. An active resource refers to any of the following: a File Share, a Blob Container, a Table, or a Queue.
If none of these resource types have an active resource under the Storage Account, Site24x7 will automatically terminate the corresponding Azure Storage object monitors. This behaviour is by design and helps reduce the number of unnecessary API calls made to the Azure portal.
Termination of an Azure Storage object monitor does not indicate a failure in your configuration. It is an automatic cleanup action taken when no active resources are found within the Storage Account.
Which monitors are affected
The following Azure Storage object monitor types are subject to automatic termination when no active resources are found in their parent Storage Account:
- Azure File Storage: Terminated when no active File Shares exist
- Azure Blob Storage: Terminated when no active Blob Containers exist
- Azure Table Storage: Terminated when no active Tables exist
- Azure Queue Storage: Terminated when no active Queues exist
What happens to the parent monitor
When an Azure Storage monitor is terminated due to the absence of active resources, the parent Azure Storage Account monitor is not affected. It will remain in an active state, ensuring that your Storage Account-level metrics and monitoring continue uninterrupted.
Once active resources are added back to the Storage Account and discovered by Site24x7, the corresponding Azure Data Storage monitors will be re-created automatically.