Overviewβ
When troubleshooting issues with Azure Event Grid, it's essential to follow a systematic approach to identify and resolve any problem efficiently. By examining the event source, subscriptions, and monitoring data, you can effectively troubleshoot issues with Azure Event Grid and identify the root causes of any event processing or delivery problems. This approach will allow you to address the specific issues and optimise the configuration and performance.
Systematic Approachβ
- Start by verifying the event source configuration and event publishing. Ensure that the event source (Apporetum) is correctly configured to publish events to the Event Grid. Check if the necessary permissions are granted, the endpoint URL is accurate, and any required authentication mechanisms are properly set up. Confirm that the events are being published correctly and that there are no errors or exceptions during the publishing process.
- Examine the Event Grid subscription and event handler configuration. Check if the subscribers are correctly registered with the Event Grid and if they are actively listening for the expected events. Verify the endpoint URLs and any authentication credentials or policies associated with the subscribers. It's also crucial to review the event filtering and routing rules to ensure that the events are being sent to the appropriate subscribers based on their interests and criteria.
- If the event publishing and subscription configurations appear to be correct, next inspect the logs and monitoring data provided by Azure Event Grid. Analyse the event delivery logs to identify any patterns or issues related to event drops, retries, or failures. Utilize Azure Monitor and Log Analytics or any other monitoring tools integrated with Event Grid to gather metrics and diagnostic information. This data can help pinpoint potential bottlenecks, network connectivity problems, or other issues affecting the event flow
Troubleshooting Azure Event Grid Eventsβ
Metricsβ
Permissionsβ
Application Event logsβ
Troubleshooting Event Gridβ
Microsoft documentation for troubleshooting Azure Event Grid issues can be found here
Enable Diagnostic Logs for Event Grid Domainsβ
Documentation for enabling diagnostic logs for event grid domains is located at the following here.
Note that the procedure in the documentation provides step-by-step instructions for enabling diagnostic logs for topics. Apporetum used an Event Grid domain so in step 2, navigate to the Event Grid domain in the Azure portal instead of the Event grid topic. The rest of the process is the same.
Retain Event Grid Logsβ
If you wish to retain the event grid logs select the Archive to storage account option. This will save the event grid diagnostics to the specified storage account. Once you enable a storage account as a capture destination, Event Grid starts emitting diagnostic logs. You should see new containers named insights-logs-deliveryfailures and insights-logs-publishfailures in the storage account.
Supported Event Grid Domain Metrics With Azure Monitorβ
You can use Azure portal to see metrics for Event Grid topics and subscriptions.
-
Mircosoft documentation for Event Grid/Domains can be found here.
-
Mircosoft documentation for Monitor Event Grid Message Delivery can be found here