APM Agent Central Configuration

Stack

APM Agent Central Configuration allows you to fine-tune your APM agents from within the Applications UI. Changes are automatically propagated to your agents, so there’s no need to redeploy.

To get started, select the services and environments you want to configure. The Applications UI lets you know when your APM agents have applied your configurations.

×

Configurations set from the Applications UI take precedence over configurations set locally in each APM agent or EDOT SDK. However, if APM Server is slow to respond, is offline, reports an error, etc., agents and SDKs will use local defaults until they’re able to update the configuration. For this reason, it is still essential to set custom default configurations locally in each of your APM agents and EDOT SDKs.

Each APM agent has a list of supported configurations. After selecting a Service name and environment in the Applications UI, a list of all supported configuration options, including descriptions and default values, will be displayed.

Supported configurations are also tagged with the badge in each APM agent’s configuration reference:

Android agent

Configuration reference

Go agent

Configuration reference

iOS agent

Configuration reference

Java agent

Configuration reference

.NET agent

Configuration reference

Node.js agent

Configuration reference

PHP agent

Configuration reference

Python agent

Configuration reference

Ruby agent

Configuration reference

Real User Monitoring (RUM) agent

Configuration reference

For most users, APM agent configuration should work out-of-the-box. If you run into trouble, it may be because you’re not using the Elasticsearch output, or because your Elasticsearch credentials don’t have sufficient privileges.

Refer to configure APM agent configuration to learn how to configure APM Server to avoid these problems.