0.1.1

Version 0.1.1

Fixes:

1. Subspan attributes 012af0d

Additions:

1. Add GraphQL schema hash to span attributes f76d391

0.1.0

This release increases open telemetry spec support by updating the span and attribute names to follow the suit of the specification:

https://opentelemetry.io/docs/specs/otel/trace/semantic_conventions/instrumentation/graphql/

graphql-otel offers the ability to record the args, result, and context and so we added some additions to the specification to support those needs:

open-telemetry/opentelemetry-specification#3668

0.0.10

Bumps the open telemetry packages to the latest versions.

Adds the ability to include the resolver result in the span attributes:

const context = {
  GraphQLOTELContext: new GraphQLOTELContext({
    includeResult: true, // If true will add the result in the span attributes
  }),
};

0.0.9

This adds the ability to exclude keys from the span context attribute.

const context = {
  GraphQLOTELContext: new GraphQLOTELContext({
    includeContext: true,
    includeVariables: true,
    excludeKeysFromContext: ["database", 'headers', "token"], <--- large objects, sensitive information
  }),
};

0.0.8

This release adds the ability to append the GraphQL context and variables onto the trace attributes.

You can do this by setting either or both options:

new GraphQLOTELContext({
  includeContext: true,
  includeVariables: true,
});

You will then see the JSON string of variables and context in your trace attributes.

Commits

• e537b3b
• 0d9d08b
• 0d9d08b

0.0.7

Version 0.0.6 of graphql-otel, span events were introduced to propagate errors. However, at that time, the span status was not being set to error. Now, with the latest changes, you can filter queries that have resulted in errors using the status filter for GraphQL.

Commits:

• 7e82050

0.0.6

This release propagates the errors that happen in the GraphQL resolver and appends them as an event on the trace.

This will better help users debug their GraphQL API.

• a3f316f