Azure SQL Managed Instance is a scalable cloud database service that's always running on the latest stable version of the Microsoft SQL Server database engine and a patched OS with 99.99% built-in high availability, offering close to 100% feature compatibility with SQL Server. This integration helps in monitoring resource usage and tracking database events of your managed instances.
Log and Metric types
For Azure SQL Managed Instance, you can collect the following logs and metrics:
- Resource Usage Statistics. To know more about the different log category types and schemas collected for Azure SQL Managed Instances, refer to the Azure documentation.
- Audit Logs. These logs include database events and Microsoft Support operations for your instances. To know more about the log schema, refer to the Azure documentation.
Azure service sends monitoring data to Azure Monitor, which can then stream data to Eventhub. Sumo Logic supports:
You must explicitly enable diagnostic settings for each Azure SQL Managed Instance you want to monitor. You can forward logs to the same event hub provided they satisfy the limitations and permissions as described here.
When you configure the event hubs source or HTTP source, plan your source category to ease the querying process. A hierarchical approach allows you to make use of wildcards. For example:
Configure logs collection
In this section, you will configure a pipeline for shipping diagnostic logs from Azure Monitor to an Event Hub.
- To set up the Azure Event Hubs cloud-to-cloud source in Sumo Logic portal, refer to our Azure Event Hubs source documentation.
- To create the Diagnostic settings in Azure portal, refer to the Azure documentation. Perform below steps for each Azure SQL Managed Instance that you want to monitor.
Stream to an event hubas the destination.
- Use the Event hub namespace and Event hub name configured in previous step in destination details section. You can use the default policy
RootManageSharedAccessKeyas the policy name.
- Enable the Server audit by following instructions after Step 7 as specified in Azure documentation.
Azure Event Hubs Source
Common error types are described here.
You can try restarting the source for