Loading

Central Configuration for Elastic OTel SDKs

APM Agent Central Configuration allows you to fine-tune your Elastic OTel SDKs from within the Applications UI. Changes are automatically propagated to your SDKs, 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 Elastic OTel SDKs have applied your configurations.

Configurations set from the Applications UI take precedence over configurations set locally in each Elastic OTel SDK. If Elastic Agent is offline, reports an error, or is slow to respond, Elastic OTel SDKs use local defaults until they’re able to update the configuration.

Each Elastic OTel SDK 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 dynamic config badge in each Elastic OTel SDK’s configuration reference:

Language/Platform Elastic OTel SDK Configuration Reference
Android Elastic OTel Android SDK Configuration reference
iOS Elastic OTel iOS SDK Configuration reference
Java Elastic OTel Java SDK Configuration reference
Node.js Elastic OTel Node.js SDK Configuration reference
PHP Elastic OTel PHP SDK Configuration reference
Python Elastic OTel Python SDK Configuration reference

Elastic OTel SDK configuration is an optional feature. To activate it, refer to Elastic OTel SDK Central Configuration.

Refer to the Elastic OpenTelemetry reference to learn how to activate central configuration for Elastic OTel SDKs.

Note

You can't configure APM agents through Elastic Agent. Use APM Server for that purpose. Refer to Configure APM agent configuration for more details.