Troubleshooting: Azure Monitoring and Alerts Basic
Use this topic to answer FAQs about Azure Monitoring and Alerts Basic.
This topic answers frequently asked questions to help troubleshoot the Sitecore Azure Monitoring and Alerts Basic dashboards and alerts in your Log Analytics Operations Management Suite (OMS).
Data starts streaming into the Log Analytics OMS ten minutes after provisioning the Sitecore Azure Monitoring and Alerts Basic module.
If you cannot see any data after ten minutes, verify the connection between Log Analytics OMS data sources and your Azure resources.
 |
If all resources are connected (excluding master) then refer to the following section.
 |
This is a known issue. If your connection is good then the resource infrastructure might not be providing any status to the Log Analytics OMS. The cause of this might be because the Log Analytics OMS is located a long distance from the resource location.
To workaround this issue: Delete your existing Log Analytics OMS and re-provision the Azure Monitoring and Alerts Basic module with the same location or a location that is closer to the resource group.
 |
If, after provisioning, you do not see the overview tiles that you were expecting, recheck all configuration options to locate any potential issues.
If the expected overview tiles are still not showing: In the Azure Resource Group delete the existing Log Analytics OMS, then re-provision the Azure Monitoring and Alerts Basic module with the correct configuration options.
 |
Alternatively you can use the following workaround:
In the resource group, delete all of the Availability tests in the resource.
Exit the OMS then re-run the deployment script.
Note
You may have to repeat this process multiple times to achieve your expected result.
This is a known issue. To work around this issue:
Click the line graph, then click Edit. Without changing any configuration, click Apply.
 |
Consider which tier you are using for your solution (tier 1, 2, 3, or 4).
Enable email notifications for alert tiers 1, 2, and 3
By default only Critical alerts generate email notifications for alert tiers 1, 2, and 3.
To enable email notifications for non-critical alerts:
In the Microsoft Azure Menu, click Monitor, Alerts, Manage action groups.
Under Action name, click the alert action group, that you want to update.
In Actions, under Details, click Edit details. In the Email/SMS/Push/Voice pane, you can edit the notification details for that alert group, including the email address of the alert recipient.
Enable email notifications for alert tier 4
For alert tier 4 (ping test), you must customize an alert specifically for it.
To enable email notifications for alert tier 4:
In Application Insights, in the menu on the left, click Availability.
On the ribbon, click Details.
Click on the edit icon of the alert.
The Edit test panel shows on the right of the page.
Under Alerts, in the Send alert emails to these email addresses: field, update your email address details.
Note
For multiple recipients, use a semicolon [;] to separate addresses.
You must use Application Insights for Azure Monitoring and Alerts Basic to be fully functional. If you do not use Application Insights then some of the Azure Monitoring alerts will not work.
After August 31st, 2019, the Metric alerts platform replaces the Alerts (classic) platform. The migration process is straightforward and Microsoft Azure has developed a migration tool to assist you.
 |
Note
You must carry out migration for each individual subscription. After you have migrated all of your subscriptions over to the new Metric alerts platform, you will not be able to revert back to the old Alerts (classic), nor will you be able to create a classic alert.
The alert rules that you migrate over to the new Metric alerts platform provide primarily the same monitoring coverage as before and all email addresses, webhook endpoints, or logic application links associated with the old classic alert rule are carried over. However, because the alert payload in the new Metric alerts platform is different, ensure you prepare for your alerts migration as they might not behave correctly. If you require assistance, contact the Microsoft Azure Classic Alert Retirement channel: classicalertsretire@microsoft.com.
After August 31st 2019, Azure automatically migrates all rules that have not already been migrated over to the new Metric alerts platform. If you have an alert rule that Microsoft Azure cannot migrate over automatically, then you have until June 2020 to migrate those alert rules over manually.
There are some alert rules that you cannot migrate over, either manually with the Microsoft Azure migration tool, or automatically with Microsoft Azure. Instead, you must manually create an equivalent alert. The old classic alerts in the meantime remain functional until June 2020, but you will not be able to modify them.