You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/send-data/collect-from-other-data-sources/azure-blob-storage/troubleshoot-log-collection.md
+8-61Lines changed: 8 additions & 61 deletions
Original file line number
Diff line number
Diff line change
@@ -69,7 +69,7 @@ Make sure that the resources you created in the Collect Logs from Azure Blob Sto
69
69
1. In the left pane of the Azure Portal, click **AppServices**, and search for “SUMOBRTaskConsumer”. You should find the `“SUMOBRTaskConsumer\<random-string\>”` Function App and click it.
70
70
1. Click the **Application settings** link. Check that the value of the **SumoLogEndpoint** field matches the HTTP source URL.
71
71
72
-
## Verify Block Blob Create Events are getting published
72
+
## Verify Blob Create Events are getting published
73
73
74
74
1. Click **All Services**. Go to Event Grid Subscription services.
75
75
1. Select Storage Account and region from the dropdown.
@@ -88,17 +88,11 @@ To verify that events are appearing in your event hub:
88
88
89
89
## Verify Service Bus Queue is receiving tasks
90
90
91
-
Go to Service Bus Service from the Azure portal and click on `SUMOBRTaskQueueNamespace\<unique string>` Service Bus Namespace. Check that the incoming messages count is greater than zero.
91
+
Go to Service Bus Service from the Azure portal and click on `SUMOBRTaskQueueNamespace\<unique string>` Service Bus Namespace. Check that the incoming messages count is greater than zero.
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"`
98
-
99
-
For more information about using Live Tail, see [Sumo Logic Live Tail](/docs/search/live-tail).
100
-
101
-
### Verify Azure Function is not getting Failed
95
+
## Verify Azure Function is not getting Failed
102
96
103
97
1. Go to Function App.
104
98
1. Go to Application Insights.<br/> 
@@ -107,60 +101,13 @@ For more information about using Live Tail, see [Sumo Logic Live Tail](/docs/sea
107
101
1. In the top 3 exception types, click on the count it will open a sample exception.
108
102
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.<br/> 
109
103
110
-
### Common Azure function errors
111
-
112
-
`ExitCode C0000005
113
-
114
-
ExitCodeString NATIVE ACCESS VIOLATION
115
-
116
-
Managed Exception = System.AccessViolationException:Attempted to read or
117
-
write protected memory. This is often an indication that other memory is corrupt.
118
-
119
-
CallStack - Managed Exception`
120
-
121
-
The above error occurs in certain situations the runtime initiates a host shutdown via `HostingEnvironment.InitiateShutdown`, for example, when an unhandled global exception occurs, when a function `TimeoutException` is thrown, or when performance counter thresholds are exceeded
122
-
(`HostHealthMonitor`).
104
+
## Verify with Live Tail
123
105
124
-
If you're using this function for quite some time then we recommend redeploying the solution with new ARM templates.
106
+
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"`
125
107
126
-
If the error still persists, then
108
+
For more information about using Live Tail, see [Sumo Logic Live Tail](/docs/search/live-tail).
127
109
128
-
1. If you want to collect metrics only you can migrate from Consumption plan to Premium plan by making changes in the ARM template.
2. If you want to collect only logs from Azure Monitor, we recommend switching to new [Cloud-to-Cloud collection for Event hub](../../hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source.md)
159
-
```
160
-
Exception while executing function: Functions.BlobTaskProducer
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.
165
113
166
-
This error occurs when the FileOffsetMap table is not created inside Table service.
0 commit comments