---
title: APM Agent Central Configuration
description: APM Agent Central Configuration allows you to fine-tune your APM agents from within the Applications UI. Changes are automatically propagated to your...
url: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/solutions/observability/apm/apm-agents/central-configuration
products:
  - APM
  - Elastic Observability
---

# APM Agent Central Configuration
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.
![APM central configuration in Kibana](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/solutions/images/observability-apm-agent-configuration.png)

<important>
  To configure EDOT SDKs through APM Agent Central Configuration, refer to [EDOT SDKs Central Configuration](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/solutions/observability/apm/opentelemetry/edot-sdks-central-configuration).
</important>


## Precedence

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.

## Supported configurations

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 ![dynamic config](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/solutions/images/observability-dynamic-config.svg) badge in each APM agent’s configuration reference:
<definitions>
  <definition term="Android agent">
    [Configuration reference](https://docs-v3-preview.elastic.dev/elastic/apm-agent-android/tree/main/reference/edot-android/configuration)
  </definition>
  <definition term="Go agent">
    [Configuration reference](https://docs-v3-preview.elastic.dev/elastic/apm-agent-go/tree/main/reference/configuration)
  </definition>
  <definition term="iOS agent">
    [Configuration reference](https://docs-v3-preview.elastic.dev/elastic/apm-agent-ios/tree/main/reference/edot-ios/configuration)
  </definition>
  <definition term="Java agent">
    [Configuration reference](https://docs-v3-preview.elastic.dev/elastic/apm-agent-java/tree/main/reference/configuration)
  </definition>
  <definition term=".NET agent">
    [Configuration reference](https://docs-v3-preview.elastic.dev/elastic/apm-agent-dotnet/tree/main/reference/configuration)
  </definition>
  <definition term="Node.js agent">
    [Configuration reference](https://docs-v3-preview.elastic.dev/elastic/apm-agent-nodejs/tree/main/reference/configuration)
  </definition>
  <definition term="PHP agent">
    [Configuration reference](https://docs-v3-preview.elastic.dev/elastic/apm-agent-php/tree/main/reference/configuration)
  </definition>
  <definition term="Python agent">
    [Configuration reference](https://docs-v3-preview.elastic.dev/elastic/apm-agent-python/tree/main/reference/configuration)
  </definition>
  <definition term="Ruby agent">
    [Configuration reference](https://docs-v3-preview.elastic.dev/elastic/apm-agent-ruby/tree/main/reference/configuration)
  </definition>
  <definition term="Real User Monitoring (RUM) agent">
    [Configuration reference](https://docs-v3-preview.elastic.dev/elastic/apm-agent-rum-js/tree/main/reference/configuration)
  </definition>
</definitions>


## APM Server configuration

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](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/solutions/observability/apm/apm-server/apm-agent-central-configuration) to learn how to configure APM Server to avoid these problems.
<note>
  You can't configure APM agents through the EDOT Collector. Use APM Server for that purpose.
</note>