Serve
Features
Monitoring/Tracing
OpenTelemetry

Open Telemetry

đź’ˇ

This page is currently under construction and expected to change. Please feel free to reach out to us directly in case you are having any troubles.

This plugins integrates Open Telemetry tracing with your GraphQL execution. It also collects GraphQL execution errors and reports it as Exceptions.

You can use this plugin with any kind of Open Telemetry tracer, and integrate it to any tracing/metric platform that supports this standard.

Getting Started

npm i @envelop/opentelemetry

Usage Example

By default, this plugin prints the collected telemetry to the console:

mesh.config.ts
import { defineConfig  } from '@graphql-mesh/serve-cli'
import { useOpenTelemetry } from '@envelop/opentelemetry'
 
export const serveConfig = defineConfig({
  plugins: pluginCtx: => [
    useOpenTelemetry({
      ...pluginCtx,
      resolvers: true, // Tracks resolvers calls, and tracks resolvers thrown errors
      variables: true, // Includes the operation variables values as part of the metadata collected
      result: true // Includes execution result object as part of the metadata collected
    })
  ]
})

Integration with @opentelemetry packages

By default, this plugin is creating a console exporter for exporting the Spans.

If you wish to use custom tracer/exporter, create it and pass it to the plugin factory function.

The following example is taking the current global tracer:

mesh.config.ts
import { defineConfig } from '@graphql-mesh/serve-cli'
import { useOpenTelemetry } from '@envelop/opentelemetry'
 
import { trace } from '@opentelemetry/api'
import { BasicTracerProvider, SimpleSpanProcessor } from '@opentelemetry/sdk-trace-base'
 
export const serveConfig = defineConfig({
  plugins: pluginCtx: => [
    useOpenTelemetry({
      ...pluginCtx,
      resolvers: true, // Tracks resolvers calls, and tracks resolvers thrown errors
      variables: true, // Includes the operation variables values as part of the metadata collected
      result: true // Includes execution result object as part of the metadata collected
    },
      trace.getTracerProvider()
    )
  ]
})

This example integrates Jaeger tracer. To use this example, start by running Jaeger locally in a Docker container (or, follow other options to run Jaeger locally):

docker run -d --name jaeger \
  -e COLLECTOR_ZIPKIN_HTTP_PORT=9411 \
  -p 5775:5775/udp \
  -p 6831:6831/udp \
  -p 6832:6832/udp \
  -p 5778:5778 \
  -p 16686:16686 \
  -p 14268:14268 \
  -p 9411:9411 \
  jaegertracing/all-in-one:latest
mesh.config.ts
import { defineConfig } from '@graphql-mesh/serve-cli'
import { useOpenTelemetry } from '@envelop/opentelemetry'
 
import { JaegerExporter } from '@opentelemetry/exporter-jaeger'
import { BasicTracerProvider, SimpleSpanProcessor } from '@opentelemetry/sdk-trace-base'
 
// Create your exporter
const exporter = new JaegerExporter({
  serviceName: 'my-service-name',
  host: 'localhost',
  port: 6832
})
 
// Configure opentelmetry to run for your service
const provider = new BasicTracerProvider()
provider.addSpanProcessor(new SimpleSpanProcessor(exporter))
provider.register()
 
export const serveConfig = defineConfig({
  plugins: pluginCtx: => [
    useOpenTelemetry({
      ...pluginCtx,
      resolvers: true, // Tracks resolvers calls, and tracks resolvers thrown errors
      variables: true, // Includes the operation variables values as part of the metadata collected
      result: true // Includes execution result object as part of the metadata collected
    },
      provider
    )
  ]
})
New RelicSentry