An Azure App Service Environment is an Azure App Service feature that provides a fully isolated and dedicated environment for running App Service apps securely at high scale. This integration helps in monitoring your environments operational events such as upgrades, scaling, and suspensions.
The below instructions applies to App Service Environment v3.
Log and Metric types
For Azure App Service Environment, you can collect the following logs:
- App Service Environment Platform Logs. Logs are only emitted when your App Service Environment has an event (for example, a scale operation with an App Service plan) that triggers the logs. To know more about the different situations and messages collected for Azure App Service Environment, 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 App Service Environment 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 App Service Environment that you want to monitor.
Stream to an event hubas the destination.
App Service Environment Platform Logs.
- 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.
Azure Event Hubs Source
Common error types are described here.
You can try restarting the source for