Azure Automation
Azure Automation delivers a cloud-based automation, operating system updates, and configuration service that supports consistent management across your Azure and non-Azure environments. It includes process automation, configuration management, update management, shared capabilities, and heterogeneous features. This integration helps in monitoring create, update and delete operations for the Automation runbooks, jobs and automation assets like connection, credential, variable, and certificate. It also gives insights into the status of your Automation jobs.
Log and metric types
For Azure Automation, you can collect the following logs and metrics:
- Platform logs. To learn more about the different log category types and schemas collected for Azure Automation, refer to the Azure documentation.
- Platform Metrics for Azure Automation. These metrics are available in Microsoft.Automation/automationAccounts namespace.
Setup
Configure collector
Create a hosted collector if not already configured. Make sure you create the required sources in this collector.
Configure logs collection
Azure service sends monitoring data to Azure Monitor, which can then stream data to Eventhub. Sumo Logic supports collecting logs from Azure Monitor using our Azure Event Hubs source.
You must explicitly enable diagnostic settings for each Azure Automation account 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, plan your source category to ease the querying process. A hierarchical approach allows you to make use of wildcards. For example: Azure/Automation/Logs.
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 source in Sumo Logic, refer to Azure Event Hubs Source for Logs.
- To create the Diagnostic settings in Azure portal, refer to the Azure documentation. Perform the steps below for each Azure Automation account that you want to monitor.
- Choose
Stream to an event hubas the destination. - Select
allLogs. - 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.
- Choose
Configure metrics collection
When you configure the Azure Metrics Source, plan your source category to ease the querying process. A hierarchical approach allows you to make use of wildcards. For example: Azure/Automation/Metrics.
To set up the Azure Metrics source in Sumo Logic, refer to Azure Metrics Source.
Troubleshooting
Metrics collection via Azure Metrics Source
To troubleshoot metrics collection via Azure Metrics Source, follow the instructions in Troubleshooting Azure Metrics Source.