If you use the default Application Insights configuration to monitor your GraphQL endpoint, there is not that much information you’ll get. For example, when a GraphQL request fails, it still results in a 200 response. Application Insights isn’t aware that you are using GraphQL and don’t flag this request as an exception.
Let’s see how we can improve our Application Insights logging by integrating it with Hot Chocolate.
Disclaimer: the code below has been written for Hot Chocolate 10. In Hot Chocolate 11, the diagnostics system is rewritten. I’ll write an update post when I have the chance to update one of my applications to Hot Chocolate 11.
- First thing we need to do is to create a class that implement the IDiagnosticObserver marker interface and inject the Application Insights TelemetryClient:
- For every event that we want to track, we need to add a method and specify the corresponding Hot Chocolate event through the DiagnosticName attribute:
- We create a dictionary to hold all ongoing requests. This is necessary to update the correct TelemetryClient instance:
- Now we can see if our GraphQL request has errors and in that case mark the request as an exception:
- As a last step we need to register our Observer on the ServiceCollection through the AddDiagnosticObserver extension method:
Here is the complete code: