Central Configuration for EDOT SDKs
Stack ECH Serverless
APM Agent Central Configuration allows you to fine-tune your EDOT 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 EDOT SDKs have applied your configurations.
To configure EDOT SDKs through APM Agent Central Configuration, refer to EDOT SDKs Central Configuration.
Configurations set from the Applications UI take precedence over configurations set locally in each EDOT SDK. If the EDOT Collector is offline, reports an error, or is slow to respond, EDOT SDKs use local defaults until they’re able to update the configuration.
Each EDOT 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 
badge in each EDOT SDK’s configuration reference:
| Language/Platform | EDOT SDK | Configuration Reference |
|---|---|---|
| Android | EDOT Android SDK | Configuration reference |
| iOS | EDOT iOS SDK | Configuration reference |
| Java | EDOT Java SDK | Configuration reference |
| Node.js | EDOT Node.js SDK | Configuration reference |
| PHP | EDOT PHP SDK | Configuration reference |
| Python | EDOT Python SDK | Configuration reference |
EDOT SDK configuration is an optional feature. To activate it, refer to EDOT SDK Central Configuration.
Refer to the EDOT reference to learn how to activate central configuration for EDOT SDKs.
You can't configure APM agents through the EDOT Collector. Use APM Server for that purpose. Refer to Configure APM agent configuration for more details.