Azure Batch

Azure Batch runs large-scale parallel and high-performance computing (HPC) batch jobs efficiently in Azure. This integration helps in monitoring health of the nodes; creation, update, and deletion events of individual Batch resources, such as a pool or task; and tracking the state (start/fail/complete) of jobs and tasks.

Log and metric types

For Azure Batch, you can collect the following logs and metrics:

• Service Logs. Events emitted by the Batch service during the lifetime of an individual resource such as a pool or task.
• Batch account metrics. Metrics at the Batch account level.

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 Batch 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/Batch/Logs.

In this section, you will configure a pipeline for shipping diagnostic logs from Azure Monitor to an Event Hub.

1. To set up the Azure Event Hubs source in Sumo Logic, refer to Azure Event Hubs Source for Logs.
2. To create the Diagnostic settings in Azure portal, refer to the Azure documentation.
   • Choose Stream to an event hub as the destination.
   • Select allLogs and audit.
   • Use the Event hub namespace and Event hub name configured in previous step in destination details section. You can use the default policy RootManageSharedAccessKey as the policy name.

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/Batch/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.