To investigate what’s going on inside your GraphQL backend I would recommend to enable Apollo tracing. You can always enable this but as this has a (small) performance impact, a better way is to enable it on demand.
In HotChocolate you can specify this through the QueryExecutionOptions:
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
services.AddGraphQL(services=> | |
SchemaBuilder.New() | |
.AddQueryType<QueryType>() | |
//Removed other types | |
.AddType<IdentificatieType>().Create(), | |
new QueryExecutionOptions() | |
{ | |
TracingPreference = TracingPreference.OnDemand | |
}); |
After doing that, tracing will be activated when ad GraphQL-Tracing HTTP header with a value of 1 is added to the request.
Now your GraphQL result will not only contain the data but also tracing information. GraphQL tools like GraphQL Playground can visualize this data:
If the tracing information is not shown, check your GraphQL Playground settings and see if "tracing.hideTracingResponse" is set to false.