Join us from October 8-10 in New York City to learn the latest tips, trends, and news about GraphQL federation and API platform engineering.Join us for GraphQL Summit 2024 in NYC
Start for Free
Apollo Server 2 is officially end-of-life as of 22 October 2023. Learn more about upgrading.

API Reference: Inline trace plugin

Using the plugin

This API reference documents the ApolloServerPluginInlineTrace plugin.

This plugin enables your to include encoded performance and usage traces inside responses. This is primarily designed for use with Apollo Federation. Federated use this plugin and include a trace in the ftv1 response extension if requested to do so by the Apollo gateway. The gateway requests this trace by passing the HTTP header apollo-federation-include-trace: ftv1.

installs this plugin by default in all federated subgraphs, with its default configuration. (Apollo Server decides that it is a federated subgraph if the schema it is serving includes a _Service.sdl: String.) You typically do not have to install this plugin yourself; you only need to do so if you want to provide non-default configuration.

If you want to configure this plugin (or if you want to use it in a that is not a federated ), import it from the apollo-server-core package and pass it to your ApolloServer in the plugins array:

import { ApolloServer } from "apollo-server";
import { ApolloServerPluginInlineTrace } from "apollo-server-core";
const server = new ApolloServer({
plugins: [
rewriteError: (err) => err.message.match(SENSTIVE_REGEX) ? null : err,

If you don't want to use the inline trace plugin even though your schema defines _Service.sdl: String, you can explicitly disable it with the ApolloServerPluginInlineTraceDisabled plugin:

import { ApolloServer } from "apollo-server";
import { ApolloServerPluginInlineTraceDisabled } from "apollo-server-core";
const server = new ApolloServer({
plugins: [ApolloServerPluginInlineTraceDisabled()],

Note that when this plugin is installed in your app, any client can request a trace for any they run, which may reveal information about your server that you consider sensitive (such as how long each individual field takes to execute). Federated subgraphs generally should not be directly exposed to the public Internet.

(Note: in addition to this plugin (which adds a base64-encoded trace to the ftv1 extension of responses), Apollo Server also contains support for an older JSON-based format which is enabled if you pass tracing: true to the ApolloServer constructor. This format was designed for use with a no longer supported tool called engineproxy, and also is recognized by -playground. This format was more verbose due to its use of JSON and the way that it represented trace node IDs. Enabling it is not recommended.)

This plugin was introduced in Apollo Server 2.18. In previous versions, inline tracing was configured using the engine option to the ApolloServer constructor. That option continues to work; see the migration guide for details.


Name /


By default, all errors from this service get included in the trace. You can specify a filter function to exclude specific errors from being reported by returning an explicit null, or you can mask certain details of the error by modifying it and returning the modified error. This function has type (GraphQLError) => GraphQLError | null.

Schema reporting plugin
Rate articleRateEdit on GitHubEditForumsDiscord

© 2024 Apollo Graph Inc.

Privacy Policy