Node.js Collector Configuration

For most use cases it is sufficient to just initialize the Instana Node.js collector with require('@instana/collector')(); and leave the default configuration options in place. You can also pass in a configuration object when initializing the Instana Node.js collector:

  // configuration options, see below

Additionally, you can configure the Node.js collector via environment variables.

Agent Communication

Agent Host

The collector tries to communicate with the Instana agent via IP and as a fallback via the host's default gateway. Should the agent not be available under either of these IPs, you can use the agentHost option to use a custom IP.

  agentHost: '::1' // use IPv6 to contact via localhost

Or leverage an environment variable.

  agentHost: process.env.HOST_IP

If not configured, the Instana collector will look for an environment variable called INSTANA_AGENT_HOST and use what is defined in this environment variable to communicate with the agent. If there is no such environment variable, it will try to contact the agent first on localhost and then on the default gateway.

Agent Port

The collector tries to communicate with the Instana Agent via port 42699. Should the port have been changed, you can use the agentPort option to change the port.

  agentPort: 42699

If not configured, the Instana collector will look for an environment variable called INSTANA_AGENT_PORT and use what is defined in this environment variable to communicate with the agent. If there is no such environment variable, it will fall back to the default port 42699.

Kubernetes & OpenShift

If your Node.js application and the Instana agent run in a Kubernetes cluster, please check the documentation on Kubernetes network access for information about the required configuration in this setup.


The tracing feature is enabled by default. To disable it, pass the following option to the initialization function:

  tracing: {
    enabled: false

You can also disable tracing by setting the environment variable INSTANA_DISABLE_TRACING=true.

When tracing is disabled, you can neither use the trace SDK nor the OpenTracing API, and automatic tracing will also be disabled. Calls using the SDK or OpenTracing will be silently ignored.

Disabling Automatic Tracing

Automatic tracing is also enabled by default. To disable only automatic tracing (leaving manual tracing via the SDK or openTracing enabled), pass the following option to the initialization function:

  tracing: {
    automaticTracingEnabled: false

The Node.js collector also still supports the previous name of this property:

  tracing: {
    disableAutomaticTracing: true

Finally, you can disable automatic tracing by setting the environment variable INSTANA_DISABLE_AUTO_INSTR=true.

When automatic tracing is disabled, you can still use the SDK or the OpenTracing API to create spans manually.

Capturing Stack Traces

By default, the collector captures the last ten call sites for every captured exit span. This value can be increased and decreased as necessary. (Note that the stack traces of HTTP entry spans are not collected – they would only show Node.js core code.) Use a value of 0 to disable stack trace capturing.

  tracing: {
    stackTraceLength: 10

You can also configure the stack trace length by setting the environment variable INSTANA_STACK_TRACE_LENGTH.

Disabling Individual Tracers

Since: 1.80.0

You can disable individual tracing instrumentations. This should only be used in special circumstances or for troubleshooting.

  tracing: {
    disabledTracers: ['graphql', 'grpc']

Alternatively, this can be archived by setting the environment variable INSTANA_DISABLED_TRACERS to a comma separated list of tracers you want to disable:


Possible values (case insensitive):

  • amqp: Disables instrumentation of the amqplib package for RabbitMQ/amqp tracing.
  • bunyan: Disables instrumentation of the bunyan package for Bunyan warn/error log message collection.
  • elasticsearchLegacy: Disables instrumentation of the elasticsearch package for Elasticsearch tracing (legacy client).
  • elasticsearchModern: Disables instrumentation of the @elastic/elasticsearch package for Elasticsearch tracing (modern client).
  • express: Disables instrumentation of the express package for Express path template collection.
  • fastify: Disables instrumentation of the fastify package for Fastify path template collection.
  • graphql: Disables instrumentation of the packages graphql and @apollo\/gateway for GraphQL tracing.
  • grpc: Disables instrumentation of the grpc package for GRPC traing.
  • hapi: Disables instrumentation of the @hapi/call package for path template collection for Hapi.
  • httpClient: Disables instrumentation of the core http and https modules for tracing of outgoing HTTP(S) calls (exits).
  • httpServer: Disables instrumentation of the core http and https modules for tracing of incoming HTTP(S) calls (entries).
  • ioredis: Disables instrumentation of the ioredis package for Redis tracing (also see option redis).
  • kafkaJs: Disables instrumentation of the kafkajs package for Kafka tracing (also see option kafkaNode).
  • kafkaNode: Disables instrumentation of the kafka-node package for Kafka tracing (also see option kafaJs).
  • koa: Disables instrumentation of the koa-router package for Koa path template collection.
  • log4js: Disables instrumentation of the log4js package for warn/error log message collection.
  • mongodb: Disables instrumentation of the mongodb/mongodb-core package for MongoDB tracing.
  • mssql: Disables instrumentation of the mssql package for MSSQL tracing.
  • mysql: Disables instrumentation of the mysql and `mysql2' packages for MySQL tracing.
  • nats: Disables instrumentation of the nats package for NATS (but not NATS streaming) tracing (also see option natsStreaming).
  • natsStreaming: Disables instrumentation of the node-nats-streaming package for NATS streaming (but not NATS) tracing (also see option nats).
  • pg: Disables instrumentation of the pg package for PostgreSQL tracing (also see option pgNative).
  • pgNative: Disables instrumentation of the pg-native package for PostgreSQL tracing (also see option (pg).
  • pino: Disables instrumentation of the pino package for warn/error log message collection.
  • redis: Disables instrumentation of the redis package for Redis tracing (also see option ioredis).
  • winston: Disables instrumentation of the winston package for warn/error log message collection.

Service Naming

Services are a central concept within Instana. Calls, spans and traces are closely associated to services. By default, the Node.js collector will use the name and version attribute from the main package.json file. To customize the service name, you can configure the serviceName property.

  serviceName: 'shop'

You can also configure a custom service name by setting the environment variable INSTANA_SERVICE_NAME.

Reporting Uncaught Exceptions

Note: This (opt-in) feature is deprecated as of version 1.112.0. If you had enabled this previously, consider disabling it and rely on the abnormal process termination detection feature (which is on by default) instead.

The Instana Node.js collector has the ability to report uncaught exceptions. By default, a Node.js process will be terminated by an uncaught exception (see Node.js docs). If uncaught exception reporting is enabled, the Instana Node.js collector will register a listener for the uncaughtException event and take the following actions when an uncaught exception occurs:

  • Report this as an incident to Instana, including the uncaught exception and its stack trace.
  • Finish the currently active span and mark it as an error (if tracing is enabled).

It will then rethrow the original exception to terminate the Node.js process. (Keeping a Node.js process running after an uncaught exception has occurred is strongly discouraged, as the process might be in an inconsistent state, see Node.js docs.)

Reporting uncaught exceptions is disabled by default. It can be enabled with the option reportUncaughtException, as follows:

  reportUncaughtException: true

The Node.js docs advise that the "correct use of 'uncaughtException' is to perform synchronous cleanup of allocated resources (e.g. file descriptors, handles, etc) before shutting down the process." Instana adheres to this and only executes synchronous actions before rethrowing the error.

The downside of this is that it might prolong the time it takes for the application process to finally terminate after the uncaught exception. Since the actions are synchronous, no other incoming requests will be accepted by your application during this time, that is, the process will be unresponsive to incoming request (HTTP, WebSockets, ...). This is an important safeguard, since the application might already be in an inconsistent state, so it would not be safe to accept/process any more requests in this process. However, this has two drawbacks:

  • If you have a mechanism in place that restarts the Node.js process once it has crashed, enabling uncaught exception tracking might lead to more failed requests, because the application process is kept alive for a bit longer (though only for a few milliseconds), delaying the automatic restart.
  • Since Instana rethrows the original exception synchronously from the uncaught exception handler, other handlers for the 'uncaughtException' event that have been registered after initialising Instana's Node.js collector are not executed. If you want to enable uncaught exception handling and also use your own handlers for this event, they should be registered before initialising Instana's Node.js collector.

Reporting Unhandled Promise Rejections

Note: While reporting uncaught exceptions is deprecated (see above), reporting unhandled promise rejections is not deprecated.

In addition to reporting uncaught exceptions, the Instana Node.js collector can also report unhandled promise rejections as issues to Instana. An unhandled promise rejection is a promise that is rejected but for which no rejection handler has been defined (that is, the promise chain does not have a .catch(...)).

This capability is disabled by default. If it is enabled and an unhandled promise rejection is detected, this is reported as an issue of severity "warning" to Instana.

Note that the call that is in progress while the promise is rejected is not marked as an error due to the unhandled rejection. The reason for this is twofold:

  1. Unhandled rejections do not cause an error in the Node.js runtime. Even if unhandled rejections occur during the processing of a request, the request can still be processed successfully.
  2. The Node.js runtime has no way of detecting unhandled rejections in the context of specific calls. In fact, unhandled rejections are only detected later, when the associated promise is about to be garbage collected. By that time, the request which triggered the unhandled rejection is already finished and has been responded to.

This capability can be enabled with the option reportUnhandledPromiseRejections, as follows:

  reportUnhandledPromiseRejections: true

Note that enabling reportUncaughtException implicitly enables reportUnhandledPromiseRejections. If required, you can enable reportUncaughtException and explicitly disable reportUnhandledPromiseRejections, like this:

  reportUncaughtException: true,
  reportUnhandledPromiseRejections: false

Starting with Node.js 12.0.0, there is a command line flag --unhandled-rejections that controls how unhandled promise rejections are handled. Reporting unhandled rejections is not supported with --unhandled-rejections=strict, because in this mode, Node.js will convert unhandled rejections to uncaught exceptions. Use the reportUncaughtException option instead of reportUnhandledPromiseRejections when running Node.js with --unhandled-rejections=strict.


Log Level Configuration

If you want to change the default log level, you can configure that via:

  level: 'debug'

You can also configure the log level by setting the environment variable INSTANA_LOG_LEVEL to either 'debug', 'info', 'warn' or 'error'. Finally, setting INSTANA_DEBUG to any non-empty string will set the log level to debug.

Custom (Parent) Logger

Not Recommended: The following way of setting a custom logger is deprecated. It might interfere with Instana's ability to capture log messages. Please see setting the logger for the recommended way to pass a custom logger to @instana/collector.

The Node.js collector uses the bunyan logging module. By default, the Node.js collector uses a standard bunyan logger with an INFO log level. If you are using Bunyan in your own app, you can define a parent logger for all loggers created by this module in the following way:

// Let's assume this is how you initialize your Bunyan (or any other logger) logger:
const bunyan = require('bunyan');
const myLogger = bunyan.createLogger({name: 'myapp'});

// Then you can pass in your logger:
  logger: myLogger

The Node.js collector will now create children of this logger with the same log level and target streams. This also works with Pino loggers.

Other logging modules are supported as long as they provide functions for the log levels debug, info, warn and error. In this case, the Node.js collector will not create child loggers but just use the given logger as is.


Since: 1.98.1. Requires at least Node.js 6.4.0

This feature is currently in beta testing phase.

To enable AutoProfile™ add autoProfile: true option when initializing the collector.

  autoProfile: true

You can also enable AutoProfile™ by setting the environment variable INSTANA_AUTO_PROFILE to true

Automatic Aggregation of Short Exit Calls

Since: 1.108.0.

The Node.js tracer supports automatic aggregation of very short (< 10 ms), high frequency database calls. This helps to keep the performance overhead of tracing at a minimum in scenarios where such calls are executed in rapid succession. At the moment this capability is opt-in and needs to be enabled explicitly. It will become the default behaviour in one of the next releases.

To enable it right away, any of the three following methods can be used:

  • Set the environment variable INSTANA_SPANBATCHING_ENABLED=true.
  • Use in-code configuration:

      tracing: {
        spanBatchingEnabled: true
  • Add this to the agent's configuration.yaml:

      span-batching-enabled: true

Note that these configuration options will be ignored once the behavior becomes on by default.

Due to the way this feature works, it is possible that enabling this option has an impact on endpoint extraction, changing the number of calls to some low latency database endpoints.

Full Configuration Reference

Here are all possible configuration values, with their default values:

  agentHost: '',
  agentPort: 42699,
  serviceName: null,
  // the log level:
  level: 'info',
  // deprecated way of setting a custom logger, use instana.setLogger(...) instead:
  logger: ... // Default: a new Bunyan logger
  tracing: {
    enabled: true,
    automaticTracingEnabled: true,
    // Spans are batched and sent to the agent once every second, or if ${forceTransmissionStartingAt} spans have been collected (whichever happens earlier)
    forceTransmissionStartingAt: 500,
    // If more than ${maxBufferedSpans} have been buffered and the collector has not been able to send them to the agent, it will start to drop spans to avoid causing memory issues.
    maxBufferedSpans: 1000,
    http: {
      // This is usually configured at the agent level (configuration.yaml).
      extraHttpHeadersToCapture: []
    // How many stack trace frames are to be captured. Can also be 0 to disable collecting stack traces.
    stackTraceLength: 10,
    // To disable individual tracing plug-ins.
    disabledTracers: [],
     // Can also be configured at the agent level (configuration.yaml).
    spanBatchingEnabled: false
  metrics: {
    timeBetweenHealthcheckCalls: 3000
  // This is usually configured at the agent level (configuration.yaml).
  secrets: {
    matcherMode: 'contains-ignore-case',
    keywords: ['key', 'pass', 'secret']
  autoProfile: false

The following is a list of all environment variables that the Node.js collector supports:

Environment Variable Equivalent Configuration Option
INSTANA_AGENT_HOST config.agentHost
INSTANA_AGENT_PORT config.agentPort
INSTANA_SERVICE_NAME config.serviceName
INSTANA_DISABLE_TRACING=true config.tracing.enabled = false
INSTANA_DISABLE_AUTO_INSTR=true config.tracing.automaticTracingEnabled = false
INSTANA_DISABLED_TRACERS config.tracing.disabledTracers
INSTANA_STACK_TRACE_LENGTH config.tracing.stackTraceLength
INSTANA_LOG_LEVEL config.level
INSTANA_DEBUG config.level = debug
INSTANA_AUTO_PROFILE=true config.autoProfile = true
INSTANA_SPANBATCHING_ENABLED=true config.tracing.spanBatchingEnabled = true

See Also