---
id: troubleshoot-log-collection
title: Troubleshoot Azure Storage Log Collection
sidebar_label: Troubleshooting
description: Follow these steps to learn why log data is not flowing into Sumo Logic from Azure Blob Storage.
slug: /help/docs/send-data/collect-from-other-data-sources/azure-blob-storage/troubleshoot-log-collection/
canonical: https://www.sumologic.com/help/docs/send-data/collect-from-other-data-sources/azure-blob-storage/troubleshoot-log-collection/
---
import useBaseUrl from '@docusaurus/useBaseUrl';
If logs do not start flowing into Sumo Logic after you perform the procedure to collect logs from Azure blob storage (using [block blobs](/docs/send-data/collect-from-other-data-sources/azure-blob-storage/block-blob/collect-logs/) or [append blobs](/docs/send-data/collect-from-other-data-sources/azure-blob-storage/append-blob/collect-logs/)), see the troubleshooting tips below.
## Error while deploying the ARM template
If you received the following error while deploying the ARM template: **The Resource 'X' under resource group 'Y' was not found.**
})
To redeploy, do the following steps:
1. Go to the resource group where the deployment failed.
1. Click on **Deployments** under **Settings**, and then click on **Microsoft.Template**(last deployment) in the next window.
1. Click **Redeploy**, provide the required fields, and click **Purchase**. You should see the successful deployment notification.
})
If you get namespace invalid error make sure it follows the naming convention specified in this [doc](https://docs.microsoft.com/en-us/rest/api/servicebus/create-namespace).
```
{
"code": "DeploymentFailed",
"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",
"details": [
{
"code": "BadRequest",
"message": "{\r\n \"error\":
{\r\n \"message\": \"The specified service namespace is invalid. CorrelationId: fb6a08d9-fc78-4540-a79e-861f1d81fe2e\",\r\n \"code\": \"BadRequest\"\r\n }
\r\n}"
},
{
"code": "BadRequest",
"message": "{\r\n \"error\":
{\r\n \"message\": \"The specified service namespace is invalid. CorrelationId: fb6a08d9-fc78-4540-a79e-861f1d81fe2e\",\r\n \"code\": \"BadRequest\"\r\n }
\r\n}"
}
]
```
For common deployment errors, refer to [Troubleshoot common Azure deployment errors](https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/common-deployment-errors).
## AutoScaling producer function to handle huge load on creating tasks for consumer function
1. Go to the Producer function app.
1. Under **Settings** blade, select **Scale out (App Service plan)**.
1. Select **Rule Based Scaling**.
1. Add your rules based scaling configuration as defined in [Create your first autoscale setting](https://learn.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-get-started#create-your-first-autoscale-setting).
})
## Verify configurations
Make sure that the resources you created in the Collect Logs from Azure Blob Storage procedure were successfully created.
1. Go to Resource groups, and select the resource group you created or selected in Configure Azure resources using ARM Template. You should see resources you created:
* Two App Service plans.
* Three App Services.
* A Service Bus Namespace.
* An Event Hubs Namespace.
* A Storage account.
1. In the left pane of the Azure Portal, click **AppServices**, and search for “SUMOBRTaskConsumer”. You should find the `“SUMOBRTaskConsumer\”` Function App and click it.
1. Click the **Application settings** link. Check that the value of the **SumoLogEndpoint** field matches the HTTP source URL.
## Verify Blob Create Events are getting published
1. Click **All Services**. Go to Event Grid Subscription services.
1. Select Storage Account and region from the dropdown.
1. Select the Event Subscription created in Step 3 from the list.
1. Click **Metrics.**
1. On the Event Grid Metrics page, check that the **Publish Succeeded** and **Delivery Succeeded** counts are greater than zero.
})
## Verify Event Hub is receiving log messages
To verify that events are appearing in your event hub:
1. In the left pane of Azure Portal, Click **Eventhub**.
1. Search for `“SUMOBREventHubNamespace”`. You should find the `“SUMOBREventHubNamespace\”` Event Hub Namespace and click it.
1. Click the **Messages** link.
1. Message summary information appears below the chart. Check that the **Incoming Messages** count is greater than zero.
})
## Verify Service Bus Queue is receiving tasks
Go to Service Bus Service from the Azure portal and click on `SUMOBRTaskQueueNamespace\` Service Bus Namespace. Check that the incoming messages count is greater than zero.
})
## Verify Azure Function is not getting Failed
1. Go to Function App.
1. Go to Application Insights.
})
1. Go to Failures section.
})
1. Click on the Function Name under Operation Name
1. In the top 3 exception types, click on the count it will open a sample exception.
1. Click on any exception it will open an end to end transaction details page where you can click on View all telemetry to view all the logs for that execution.
})
## Verify with Live Tail
In Sumo Logic, open a Live Tail tab and run a search to verify Sumo Logic is receiving events. Search by the source category you assigned to the HTTP Source that receives the log data, for example: `_sourceCategory="azure/ad"`
For more information about using Live Tail, see [Sumo Logic Live Tail](/docs/search/live-tail).
## Common Azure function errors
For common error messages, refer [Blob Reader error messages](/docs/send-data/collect-from-other-data-sources/azure-monitoring/arm-integration-faq/#blob-reader-error-messages) section.