Graphweaver comes with OpenTelemetry support built in. This means that you can see traces of requests as they come in to the GraphQL server.
By default OpenTelemetry is disabled, this guide will help you configure it for your app.
To start there are two modes supported, external or internal mode.
External mode sends all trace requests to an external OpenTelemetry collector. This is the best mode for running in production as the processing of traces is handled by a secondary process and can be stored in a tracing platform such as https://www.jaegertracing.io/ or a hosted platform like https://signoz.io/.
Integrated mode shows traces within the AdminUI and sends trace data to a data provider of your choice. This mode is quick to enable and see results and does not rely on any external services. However, trace processing is handled in the same thread as your app logic and this will slow down performance.
Let’s look at how to implement both modes in detail next.
This mode is best for a production instance of Graphweaver as all trace processing will happen in an external process improving the performance of Graphweaver.