First let’s ensure we understand what your databases need alerted on. Generally, items like CPU and Memory can impact performance, but do you have any logs you need to alert on as well? If you are not sure, that’s okay, we are here to help you!
Below are great resources from Microsoft regarding their journey for adopting Azure Monitor as well as a GitHub toolkit to get you started with configuring your alerts:
As you can see there are various alerts that could be configured quickly utilizing Log Analytics and Kusto Query Language (KQL). Specifically, there is a configuration outlining the KQL required to alert on various potential SQL Database issues. Now we have a starter pack for you to begin your Azure Monitoring!
Next, we need to decide where to send these alerts. We don’t want to miss these important alert notifications. We recommend enabling the responsible team for the resource to monitor their implementation(s). Alerts should be actionable when we configure them. If we just need to be aware, we could use Workbooks, Insights, or Dashboards. It is a clever idea to create alerts that correspond with your reporting needs as well.