Skip to main content

GraphQL Hot Chocolate–Application Insights monitoring

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:
public class ApplicationInsightsDiagnosticObserver:IDiagnosticObserver {
private readonly TelemetryClient _telemetryClient;
public ApplicationInsightsDiagnosticObserver(TelemetryClient telemetryClient)
{
_telemetryClient = 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:
[DiagnosticName("HotChocolate.Execution.Query.Start")]
public void BeginQueryExecute(IQueryContext context)
{
}
  • We create a dictionary to hold all ongoing requests. This is necessary to update the correct TelemetryClient instance:
private readonly TelemetryClient _telemetryClient;
private Dictionary<string, IOperationHolder<RequestTelemetry>> _inFlightOperations = new Dictionary<string, IOperationHolder<RequestTelemetry>>();
[DiagnosticName("HotChocolate.Execution.Query.Start")]
public void BeginQueryExecute(IQueryContext context)
{
var httpContext = GetHttpContextFrom(context);
if (httpContext == null) return;
// Create a new request
var requestTelemetry = new RequestTelemetry()
{
Name = $"{httpContext.Request.Method} {httpContext.Request.GetUri().GetLeftPart(UriPartial.Path)}",
Url = new Uri(httpContext.Request.GetUri().AbsoluteUri)
};
requestTelemetry.Context.Operation.Id = GetOperationIdFrom(httpContext);
requestTelemetry.Context.Operation.ParentId = GetOperationIdFrom(httpContext);
requestTelemetry.Properties.Add("GraphQL Query", context.Request.Query.ToString());
// Start the operation, and store it in the dictionary
var operation = _telemetryClient.StartOperation(requestTelemetry);
_inFlightOperations.Add(GetOperationIdFrom(httpContext), operation);
}
  • Now we can see if our GraphQL request has errors and in that case mark the request as an exception:
[DiagnosticName("HotChocolate.Execution.Query.Stop")]
public void EndQueryExecute(IQueryContext context, IExecutionResult result)
{
var httpContext = GetHttpContextFrom(context);
if (httpContext == null) return;
if (_inFlightOperations.ContainsKey(GetOperationIdFrom(httpContext)))
{
var operation = _inFlightOperations[GetOperationIdFrom(httpContext)];
_inFlightOperations.Remove(GetOperationIdFrom(httpContext));
// handle any final request logging here (GraphQL query errors, success, etc)
if (result.Errors.Count == 0)
{
operation.Telemetry.Success = true;
operation.Telemetry.ResponseCode = "200";
}
else
{
HandleErrors(result.Errors);
operation.Telemetry.Success = false;
operation.Telemetry.ResponseCode = "500";
}
// Then stop the operation. This completes the request.
_telemetryClient.StopOperation(operation);
}
}
private void HandleErrors(IReadOnlyCollection<IError> errors)
{
foreach(var error in errors)
{
string path = string.Join("/",
error.Path.Select(t => t.ToString()));
if (error.Exception == null)
{
var exceptionTelemetry = new ExceptionTelemetry();
exceptionTelemetry.Message = error.Message;
_telemetryClient.TrackException(exceptionTelemetry);
}
else
{
_telemetryClient.TrackException(error.Exception);
}
}
}
  • As a last step we need to register our Observer on the ServiceCollection through the AddDiagnosticObserver extension method:
public void ConfigureServices(IServiceCollection services)
{
services.AddDiagnosticObserver<ApplicationInsightsDiagnosticObserver>();
services.AddApplicationInsightsTelemetry();
}

Here is the complete code:

public class ApplicationInsightsDiagnosticObserver:IDiagnosticObserver {
private readonly TelemetryClient _telemetryClient;
private Dictionary<string, IOperationHolder<RequestTelemetry>> _inFlightOperations = new Dictionary<string, IOperationHolder<RequestTelemetry>>();
public ApplicationInsightsDiagnosticObserver(TelemetryClient telemetryClient)
{
_telemetryClient = telemetryClient;
}
[DiagnosticName("HotChocolate.Execution.Query.Start")]
public void BeginQueryExecute(IQueryContext context)
{
var httpContext = GetHttpContextFrom(context);
if (httpContext == null) return;
// Create a new request
var requestTelemetry = new RequestTelemetry()
{
Name = $"{httpContext.Request.Method} {httpContext.Request.GetUri().GetLeftPart(UriPartial.Path)}",
Url = new Uri(httpContext.Request.GetUri().AbsoluteUri)
};
requestTelemetry.Context.Operation.Id = GetOperationIdFrom(httpContext);
requestTelemetry.Context.Operation.ParentId = GetOperationIdFrom(httpContext);
requestTelemetry.Properties.Add("GraphQL Query", context.Request.Query.ToString());
// Start the operation, and store it in the dictionary
var operation = _telemetryClient.StartOperation(requestTelemetry);
_inFlightOperations.Add(GetOperationIdFrom(httpContext), operation);
}
[DiagnosticName("HotChocolate.Execution.Query.Stop")]
public void EndQueryExecute(IQueryContext context, IExecutionResult result)
{
var httpContext = GetHttpContextFrom(context);
if (httpContext == null) return;
if (_inFlightOperations.ContainsKey(GetOperationIdFrom(httpContext)))
{
var operation = _inFlightOperations[GetOperationIdFrom(httpContext)];
_inFlightOperations.Remove(GetOperationIdFrom(httpContext));
// handle any final request logging here (GraphQL query errors, success, etc)
if (result.Errors.Count == 0)
{
operation.Telemetry.Success = true;
operation.Telemetry.ResponseCode = "200";
}
else
{
HandleErrors(result.Errors);
operation.Telemetry.Success = false;
operation.Telemetry.ResponseCode = "500";
}
// Then stop the operation. This completes the request.
_telemetryClient.StopOperation(operation);
}
}
private void HandleErrors(IReadOnlyCollection<IError> errors)
{
foreach(var error in errors)
{
string path = string.Join("/",
error.Path.Select(t => t.ToString()));
if (error.Exception == null)
{
var exceptionTelemetry = new ExceptionTelemetry();
exceptionTelemetry.Message = error.Message;
_telemetryClient.TrackException(exceptionTelemetry);
}
else
{
_telemetryClient.TrackException(error.Exception);
}
}
}
private HttpContext GetHttpContextFrom(IQueryContext context)
{
// This method is used to enable start/stop events for query.
if (!context.ContextData.ContainsKey("HttpContext"))
return null;
return context.ContextData["HttpContext"] as HttpContext;
}
private string GetOperationIdFrom(HttpContext context)
{
return context.TraceIdentifier;
}
}

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Col...