Operational Insights

So what this community based MP does:

• It discovers your Azure AD tenants, the authority used to authenticate to OMS, starting from a preconfigured configuration file
• It discovers all the Azure subscriptions for those tenants
• It discovers all the OMS workspaces for every Azure subscriptions
• It monitors the reachability of every OMS workspace
• It monitors the last data point collected for every OMS connected system and alerts accordingly a preset threshold

The discovering schedule (once a day to every 4 hours) and the monitoring scheduling (once every hour) are loose enough so that they don’t burden the service. The only caveat is that today I choose to discover every single managed system, this scale well if the systems are in the few hundreds, not if in the thousands. I took this decision ‘cause I wanted to have an inventory and an health model for every managed system. If you’re in the thousands of systems and still want to monitor the overall status a simple addition can achieve the same result without discovering every single system