Interface HttpInstrumentationConfig

Options available for the HTTP instrumentation (see documentation)

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

Hierarchy (View Summary)

Properties

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

Properties

OptionalapplyCustomAttributesOnSpan

applyCustomAttributesOnSpan?: HttpCustomAttributeFunction

Function for adding custom attributes after response is handled

OptionaldisableIncomingRequestInstrumentation

disableIncomingRequestInstrumentation?: boolean

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

OptionaldisableOutgoingRequestInstrumentation

disableOutgoingRequestInstrumentation?: boolean

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

Optionalenabled

enabled?: boolean

Whether to enable the plugin.

Default

true

OptionalheadersToSpanAttributes

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

Map the following HTTP headers to span attributes.

OptionalignoreIncomingRequestHook

ignoreIncomingRequestHook?: IgnoreIncomingRequestFunction

Not trace all incoming requests that matched with custom function

OptionalignoreOutgoingRequestHook

ignoreOutgoingRequestHook?: IgnoreOutgoingRequestFunction

Not trace all outgoing requests that matched with custom function

OptionalrequestHook

requestHook?: HttpRequestCustomAttributeFunction

Function for adding custom attributes before request is handled

OptionalrequireParentforIncomingSpans

requireParentforIncomingSpans?: boolean

Require parent to create span for incoming requests

OptionalrequireParentforOutgoingSpans

requireParentforOutgoingSpans?: boolean

Require parent to create span for outgoing requests

OptionalresponseHook

responseHook?: HttpResponseCustomAttributeFunction

Function for adding custom attributes before response is handled

OptionalserverName

serverName?: string

The primary server name of the matched virtual host.

OptionalstartIncomingSpanHook

startIncomingSpanHook?: StartIncomingSpanCustomAttributeFunction

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

OptionalstartOutgoingSpanHook

startOutgoingSpanHook?: StartOutgoingSpanCustomAttributeFunction

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

Settings

Member Visibility

On This Page

Properties