OpenTelemetry SDK
    Preparing search index...

    Interface HttpInstrumentationConfig

    Options available for the HTTP instrumentation (see documentation)

    interface HttpInstrumentationConfig {
        applyCustomAttributesOnSpan?: HttpCustomAttributeFunction;
        disableIncomingRequestInstrumentation?: boolean;
        disableOutgoingRequestInstrumentation?: boolean;
        enabled?: boolean;
        enableSyntheticSourceDetection?: boolean;
        headersToSpanAttributes?: {
            client?: { requestHeaders?: string[]; responseHeaders?: string[] };
            server?: { requestHeaders?: string[]; responseHeaders?: string[] };
        };
        ignoreIncomingRequestHook?: IgnoreIncomingRequestFunction;
        ignoreOutgoingRequestHook?: IgnoreOutgoingRequestFunction;
        redactedQueryParams?: string[];
        requestHook?: HttpRequestCustomAttributeFunction;
        requireParentforIncomingSpans?: boolean;
        requireParentforOutgoingSpans?: boolean;
        responseHook?: HttpResponseCustomAttributeFunction;
        serverName?: string;
        startIncomingSpanHook?: StartIncomingSpanCustomAttributeFunction;
        startOutgoingSpanHook?: StartOutgoingSpanCustomAttributeFunction;
    }

    Hierarchy (View Summary)

    Index

    Properties

    applyCustomAttributesOnSpan? disableIncomingRequestInstrumentation? disableOutgoingRequestInstrumentation? enabled? enableSyntheticSourceDetection? headersToSpanAttributes? ignoreIncomingRequestHook? ignoreOutgoingRequestHook? redactedQueryParams? requestHook? requireParentforIncomingSpans? requireParentforOutgoingSpans? responseHook? serverName? startIncomingSpanHook? startOutgoingSpanHook?

    Properties

    applyCustomAttributesOnSpan?: HttpCustomAttributeFunction

    Function for adding custom attributes after response is handled

    disableIncomingRequestInstrumentation?: boolean

    If set to true, incoming requests will not be instrumented at all.

    disableOutgoingRequestInstrumentation?: boolean

    If set to true, outgoing requests will not be instrumented at all.

    enabled?: boolean

    Whether to enable the plugin.

    true
    enableSyntheticSourceDetection?: boolean

    Enable automatic population of synthetic source type based on the user-agent header

    headersToSpanAttributes?: {
        client?: { requestHeaders?: string[]; responseHeaders?: string[] };
        server?: { requestHeaders?: string[]; responseHeaders?: string[] };
    }

    Map the following HTTP headers to span attributes.

    ignoreIncomingRequestHook?: IgnoreIncomingRequestFunction

    Do not trace incoming requests for which this function returns true.

    ignoreOutgoingRequestHook?: IgnoreOutgoingRequestFunction

    Do not trace outgoing requests for which this function returns true.

    redactedQueryParams?: string[]

    [Optional] Additional query parameters to redact. Use this to specify custom query strings that contain sensitive information. These will replace/overwrite the default query strings that are to be redacted.

    default strings ['sig','Signature','AWSAccessKeyId','X-Goog-Signature']
    @experimental
    requestHook?: HttpRequestCustomAttributeFunction

    Function for adding custom attributes before request is handled

    requireParentforIncomingSpans?: boolean

    Require parent to create span for incoming requests

    requireParentforOutgoingSpans?: boolean

    Require parent to create span for outgoing requests

    responseHook?: HttpResponseCustomAttributeFunction

    Function for adding custom attributes before response is handled

    serverName?: string

    The primary server name of the matched virtual host.

    startIncomingSpanHook?: StartIncomingSpanCustomAttributeFunction

    Function for adding custom attributes before a span is started in incomingRequest

    startOutgoingSpanHook?: StartOutgoingSpanCustomAttributeFunction

    Function for adding custom attributes before a span is started in outgoingRequest

    Settings

    Member Visibility

    On This Page

    Properties