Configuration

While initializing the agent you can provide the following configuration options:

The Elastic APM service name is used to differentiate data from each of your services. Can only contain alphanumeric characters, spaces, underscores, and dashes (must match ^[a-zA-Z0-9 _-]+$).

The URL used to make requests to the APM Server.

The server prefix URL used to make requests to the APM Server. Some ad blockers block outgoing requests from the browser if the default server prefix URL is being used. Using a custom server prefix URL can be used to evade the ad blocker.

The version of the app. This could be the version from your package.json file, a git commit reference, or any other string that might help you reference a specific version. This option is used on the APM Server to find the right sourcemap file to apply to the stack trace.

A Boolean value that specifies if the agent should be active or not. If active, the agent will send APM transactions and track errors. This option can be used to deactivate the agent in your staging environment. It can also be used to sample a number of clients. Below is an example to sample 10% of the page loads:

var options = {
  active: Math.random() < 0.1
}

A Boolean value that specifies if the agent should automatically instrument the application to collect performance metrics for the application.

A list of instrumentations which can be disabled. When disabled, no transactions or spans will be created for that type. The valid options are:

The environment where the service being monitored is deployed, e.g. "production", "development", "test", etc.

Environments allow you to easily filter data on a global level in the APM app. It’s important to be consistent when naming environments across agents. See environment selector in the APM app for more information.

Set the verbosity level for the agent. This does not have any influence on the types of errors that are sent to the APM Server. This option is useful when you want to report an issue with the agent to us.

Possible levels are: trace, debug, info, warn, and error.

This denotes the version of APM Server’s intake API. Setting this value to any number above 2 will compress the events (transactions and errors) payload sent to the server.

Enable or disable the tracking and collection of breakdown metrics for the transaction.

The agent maintains a single queue to record transaction and error events when they are added. This option sets the flush interval in milliseconds for the queue.

This option overrides the page load transactions trace ID.

This option overrides the page load transactions sampled property. It is only applicable to page-load transactions.

This option overrides the ID of the span that is generated for receiving the initial document.

This option sets the name for the page load transaction. By default, transaction names for hard (page load) and soft (route change) navigations are inferred by the agent based on the current URL. Check the custom initial page load transaction names documentation for more details.

Distributed tracing is enabled by default. Use this option to disable it.

This option can be set to an array containing one or more Strings or RegExp objects and determines which origins should be monitored as part of distributed tracing. This option is consulted when the agent is about to add the distributed tracing HTTP header (traceparent) to a request. Please note that each item in the array should be a valid URL containing the origin (other parts of the url are ignored) or a RegExp object. If an item in the array is a string, an exact match will be performed. If it’s a RegExp object, its test function will be called with the request origin.

var options = {
  distributedTracingOrigins: ['https://example.com', /https?:\/\/example\.com:\d{4}/]
}

When distributed tracing is enabled, this option can be used to propagate the tracestate HTTP header to the configured origins. Before enabling this flag, make sure to change your server configuration to avoid Cross-Origin Resource Sharing errors.

Throttle the number of events sent to APM Server.

By default, the agent can only send up to 80 events every 60000 milliseconds (one minute).

A number between 0.0 and 1.0 that specifies the sample rate of transactions. By default, all transactions are sampled.

This option activates APM Agent Configuration via Kibana. When set to true, the agent starts fetching configurations via the APM Server during the initialization phase. These central configurations are cached in sessionStorage, and will not be fetched again until the session is closed and/or sessionStorage is cleared. In most cases, this means when the tab/window of the page is closed.

An array containing a list of transaction names that should be ignored when sending the payload to the APM server. It can be set to an array containing one or more Strings or RegExp objects. If an element in the array is a String, an exact match will be performed. If an element in the array is a RegExp object, its test function will be called with the name of the transation.

const options = {
  ignoreTransactions: [/login*/, '/app']
}

Instructs the agent to start monitoring for browser tasks that block the UI thread and might delay other user inputs by affecting the overall page responsiveness. Learn more about long task spans and how to interpret them.

apm.init({ apmRequest: (requestParams) => true})

Arguments:

apmRequest can be used to change or reject requests that are made to the APM Server. This config can be set to a function, which is called whenever the agent needs to make a request to the APM Server.

The callback function is called with a single argument and is expected to return an output synchronously. If the return value is true then the agent continues with making the (potentially modified) request to the APM Server.

If this function returns a falsy value the request is discarded with a warning in the console.

The following example adds a header to the HTTP request:

apm.init({
  apmRequest({ xhr }) {
    xhr.setRequestHeader('custom', 'header')
    return true
  }
})

This example instructs the agent to discard the request, since it’s handled by the user:

apm.init({
  apmRequest({ url, method, headers, payload }) {
    // Handle the APM request here or at some later point.
    fetch(url, {
      method,
      headers,
      body: payload
    });
    return false
  }
})

This allows the agent to send cookies when making requests to the APM server. This is useful on scenarios where the APM server is behind a reverse proxy that requires requests to be authenticated.