1 | interface GraphqlOptions {
|
2 | /**
|
3 | * Do not create spans for resolvers.
|
4 | *
|
5 | * Defaults to true.
|
6 | */
|
7 | ignoreResolveSpans?: boolean;
|
8 | /**
|
9 | * Don't create spans for the execution of the default resolver on object properties.
|
10 | *
|
11 | * When a resolver function is not defined on the schema for a field, graphql will
|
12 | * use the default resolver which just looks for a property with that name on the object.
|
13 | * If the property is not a function, it's not very interesting to trace.
|
14 | * This option can reduce noise and number of spans created.
|
15 | *
|
16 | * Defaults to true.
|
17 | */
|
18 | ignoreTrivialResolveSpans?: boolean;
|
19 | /**
|
20 | * If this is enabled, a http.server root span containing this span will automatically be renamed to include the operation name.
|
21 | * Set this to `false` if you do not want this behavior, and want to keep the default http.server span name.
|
22 | *
|
23 | * Defaults to true.
|
24 | */
|
25 | useOperationNameForRootSpan?: boolean;
|
26 | }
|
27 | export declare const instrumentGraphql: ((options?: GraphqlOptions | undefined) => void) & {
|
28 | id: string;
|
29 | };
|
30 | /**
|
31 | * GraphQL integration
|
32 | *
|
33 | * Capture tracing data for GraphQL.
|
34 | */
|
35 | export declare const graphqlIntegration: (options?: GraphqlOptions | undefined) => import("@sentry/types").Integration;
|
36 | export {};
|
37 | //# sourceMappingURL=graphql.d.ts.map |
\ | No newline at end of file |