# apollo-opentracing > Trace your GraphQL server with Opentracing Latest version **3.0.45** (published 2023-03-14) · MIT license · 0 weekly downloads ## Install ```sh npm install apollo-opentracing pnpm add apollo-opentracing yarn add apollo-opentracing bun add apollo-opentracing ``` ## Health **Score 40/100 (D)** — status: abandoned. Positive: has types; no vulnerabilities; high maintenance score; high quality score. Warnings: low downloads; no esm support. Negative: abandoned. ## Facts | | | |---|---| | Version | 3.0.45 | | Published | 2023-03-14 | | First published | 2018-08-19 | | Weekly downloads | 0 | | License | MIT | | TypeScript types | bundled | | Module format | CommonJS | | Dependencies | 2 | | Unpacked size | 58.6 KB | | Known vulnerabilities | 0 | | Install scripts | no | | GitHub stars | 182 | | Author | Daniel Schmidt | | Maintainers | dschmidt | ## Links - npm: https://www.npmjs.com/package/apollo-opentracing - Repository: https://github.com/DanielMSchmidt/apollo-opentracing - Homepage: https://github.com/DanielMSchmidt/apollo-opentracing#readme - Issues: https://github.com/DanielMSchmidt/apollo-opentracing/issues - npm.io page: https://npm.io/package/apollo-opentracing ## Dependencies (2) - [apollo-server-types](https://npm.io/package/apollo-server-types.md) ^3.0.0 - [apollo-server-plugin-base](https://npm.io/package/apollo-server-plugin-base.md) ^3.0.0 ## Recent versions - 3.0.45 (latest) — 2023-03-14 - 0.0.2-7 (next) — 2018-08-19 - 3.0.44 — 2023-03-03 - 3.0.43 — 2023-03-02 - 3.0.42 — 2023-01-31 - 3.0.41 — 2022-12-26 - 3.0.40 — 2022-12-17 - 3.0.39 — 2022-12-08 - 3.0.38 — 2022-12-01 - 3.0.37 — 2022-11-15 - 3.0.36 — 2022-11-03 - 3.0.35 — 2022-11-02 - 3.0.34 — 2022-11-01 - 3.0.33 — 2022-10-27 - 3.0.32 — 2022-10-11 - … 140 more at https://npm.io/package/apollo-opentracing/versions ## README # Apollo Opentracing [![npm version](https://badge.fury.io/js/apollo-opentracing.svg)](https://badge.fury.io/js/apollo-opentracing) [![Build Status](https://travis-ci.com/DanielMSchmidt/apollo-opentracing.svg?branch=master)](https://travis-ci.com/DanielMSchmidt/apollo-opentracing) [![semantic-release](https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg)](https://github.com/semantic-release/semantic-release) [![All Contributors](https://img.shields.io/badge/all_contributors-4-orange.svg?style=flat-square)](#contributors) Apollo Opentracing allows you to integrate open source baked performance tracing to your Apollo server based on industry standards for tracing. - 🚀 Request & Field level resolvers are traced out of the box - 🔍 Queries and results are logged, to make debugging easier - ⚙️ Select which requests you want to trace - 🔗 Spans transmitted through the HTTP Headers are picked up - 🔧 Use the opentracing compatible tracer you like, e.g. - [jaeger](https://www.jaegertracing.io/) - [zipkin](https://github.com/DanielMSchmidt/zipkin-javascript-opentracing) - 🦖 Support from node 6 on ## Installation Run `npm install --save apollo-opentracing` given that you already setup an opentracing tracer accordingly. ## Setup We need two types of tracer (which could be identical if you like): - server: Only used for the root (the first span we will start) - local: Used to start every other span ```diff const { graphqlExpress } = require("apollo-server-express"); const {serverTracer, localTracer} = require("./tracer"); +const OpentracingPlugin = require("apollo-opentracing").default; app.use( "/graphql", bodyParser.json(), graphqlExpress({ schema, + plugins: [OpentracingPlugin({ + server: serverTracer, + local: localTracer, + })] }) ) ``` ## Connecting Services ![example image](demo.png) To connect other services you need to use the opentracing [inject](http://opentracing.io/documentation/pages/api/cross-process-tracing.html) function of your tracer. We pass the current span down to your resolvers as `info.span`, so you should use it. You can also make use of it and add new logs or tags on the fly if you like. This may look something like this: ```js myFieldResolver(source, args, context, info) { const headers = {...}; const parentSpan = info.span; // please use the same tracer you passed down to the extension const networkSpan = tracer.startSpan("NetworkRequest:" + endpoint, { childOf: parentSpan }); // Let's transfer the span information to the headers tracer.inject( networkSpan, YourOpentracingImplementation.FORMAT_HTTP_HEADERS, headers ); return doNetworkRequest(endpoint, headers).then(result => { networkSpan.finish() return result; }, err => { networkSpan.log({ error: true, errorMessage: err }); networkSpan.finish(); return err; }); } ``` ## Selective Tracing Sometimes you don't want to trace everything, so we provide ways to select if you want to start a span right now or not. ### By Request If you construct the extension with `shouldTraceRequest` you get the option to opt-in or out on a request basis. When you don't start the span for the request the field resolvers will also not be used. The function is called with the same arguments as the `requestDidStart` function extensions can provide, which is documented [here](https://github.com/apollographql/apollo-server/blob/master/packages/graphql-extensions/src/index.ts#L35). When the request is not traced there will also be no traces of the field resolvers. ### By Field There might be certain field resolvers that are not worth the tracing, e.g. when they get a value out of an object and need no further tracing. To control if you want a field resolver to be traced you can pass the `shouldTraceFieldResolver` option to the constructor. The function is called with the same arguments as your field resolver and you can get the name of the field by `info.fieldName`. When you return false no traces will be made of this field resolvers and all underlying ones. ## Modifying span metadata If you'd like to add custom tags or logs to span you can construct the extension with `onRequestResolve`. The function is called with two arguments: span and infos `onRequestResolve?: (span: Span, info: RequestStart)` ## Using your own request span If you need to take control of initializing the request span (e.g because you need to use it during context initialization) you can do so by having creating it as `context.requestSpan`. ## Options - `server`: Opentracing Tracer for the incoming request - `local`: Opentracing Tracer for the local and outgoing requests - `onFieldResolve(source: any, args: { [argName: string]: any }, context: SpanContext, info: GraphQLResolveInfo)`: Allow users to add extra information to the span - `onFieldResolveFinish(error: Error | null, result: any, span: Span)`: Callback after a field was resolved - `shouldTraceRequest` & `shouldTraceFieldResolver`: See [Selective Tracing](#selective-tracing) - `onRequestResolve(span: Span, info: GraphQLRequestContext)`: Add extra information to the request span - `createCustomSpanName(name: String, info: GraphQLResolveInfo)`: Allow users to provide customized span name - `onRequestError(rootSpan: Span, info: GraphQLRequestContextDidEncounterErrors)`: Callback when a request errors ## Contributing Please feel free to add issues with new ideas, bugs and anything that might come up. Let's make performance measurement to everyone <3 ## Contributors Thanks goes to these wonderful people ([emoji key](https://github.com/kentcdodds/all-contributors#emoji-key)):

Daniel Schmidt
💻 🤔
Ciaran Liedeman
🐛 💻 ⚠️
Jens Ulrich Hjuler Pedersen
🐛 🤔 👀
Francesca
💻
Ricardo Casares
💻
Michał Wieczorek
💻
Koen Punt
💻

Zeke Nierenberg
💻
Tomáš Voslař
💻
Ben Kimball
💻
Jiapei Liang
💻
Richard W
🤔 🔬
Lee Weisberger
💻
Dustin Deus
🐛
This project follows the [all-contributors](https://github.com/kentcdodds/all-contributors) specification. Contributions of any kind welcome! ## License [MIT](LICENSE) --- _Source: https://npm.io/package/apollo-opentracing · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._