VOOZH about

URL: https://docs.datadoghq.com/tracing/guide/remote_config/

⇱ Setting up Remote Configuration for Tracing

For AI agents: A markdown version of this page is available at https://docs.datadoghq.com/tracing/guide/remote_config.md. A documentation index is available at /llms.txt.

Setting up Remote Configuration for Tracing

This product is not supported for your selected Datadog site. ().

This guide covers setting up and using Remote Configuration with your SDKs. For more information on how Remote Configuration works, see Remote Configuration.

Prerequisites

  • Datadog Agent 7.47.0 or higher installed on your hosts or containers.
  • Upgrade your SDKs to a Remote Configuration-compatible version. For more information, see the Supported configuration options section.
  • Ensure your RBAC permissions include org_management, so you can enable Remote Configuration for your organization.
  • Ensure your RBAC permissions include api_keys_write, so you can create a new API key with the Remote Configuration capability, or add the capability to an existing API key. Contact your organization’s Datadog administrator to update your permissions if you don’t have it. A key with this capability allows you to authenticate and authorize your Agent to use Remote Configuration.
  • Ensure you have the APM Remote Configuration Read and APM Remote Configuration Write permissions. Note: If you don’t have these permissions, ask your Datadog Admin to update your permissions from your Organization Settings.

Set up Remote Configuration

  1. Ensure that Remote Configuration is enabled for your organization. This enables Datadog components across your organization to receive configurations from Datadog.

  2. Select an existing API key or create a new API key, and enable the Remote Configuration capability on the key if it is not already enabled.

  3. Restart your Agent.

Review Remote Configuration status of SDKs

You can gain visibility into the Remote Configuration status of your SDKs through the Remote Configuration UI.

The following table describes the meaning of each SDK status:

SDK StatusDescription
CONNECTEDThe SDK is successfully connected to the Remote Configuration service through the associated Agent. This is the optimal state you want your SDK to be in for Remote Configuration.
UNAUTHORIZEDThe SDK is associated with an Agent which doesn’t have APM Remote Configuration Read permission on its API key. To fix the issue, you need to enable Remote Configuration capability on the API Key used by the Agent associated with the SDK.
CONNECTION ERRORThe SDK deployed in your environment is associated with an Agent that has remote_config.enabled set to true in its datadog.yaml configuration file, however, the Agent cannot be found in the Remote Configuration service. The most likely cause of this is that the associated Agent is unable to reach Remote Configuration endpoints. To fix the issue, you need to allow outbound HTTPS access to Remote Configuration endpoints from your environment.
DISABLEDThe SDK deployed in your environment is associated with an Agent that has remote_config.enabled set to false in its datadog.yaml configuration file. This could be set deliberately or mistakenly. To enable Remote Configuration on the associated Agent, set remote_config.enabled to true.
NOT CONNECTEDThe SDK cannot be found in the Remote Configuration service and is associated with an Agent that could have remote_config.enabled set to true or false in its datadog.yaml configuration file. Check your local Agent configuration or your proxy settings.
UNSUPPORTED AGENTThe SDK is associated with an Agent which is not Remote Configuration capable. To fix this issue, update the associated Agent software to the latest available version.
NOT DETECTEDThe SDK does not support Remote Configuration. To fix this issue, update the SDK software to the latest available version.
UNKNOWNThe SDK status is unknown, and it can’t be determined if an Agent is associated with the SDK. For example, this could be because the Agent is deployed on a fully managed serverless container service like AWS Fargate.

Opting out of Remote Configuration for Fleet Automation

You can disable Remote Configuration capabilities:

  • at the API key level
  • at the Agent level
  • at the organization level (not recommended)

At the API key level

Disable the API key of your choice on the API Keys page. You need the api_keys_write permission to disable Remote Configuration on an API key.

At the Agent level

Starting with Agent version 7.47.0, remote_configuration.enabled is set to true by default in the Agent. This setting causes the Agent to request configuration updates from the Datadog site.

If you don’t want your Agent to send configuration requests to Datadog, you can set remote_configuration.enabled to false in the Agent.

Change remote_configuration.enabled from true to false in your configuration YAML file:

remote_configuration:enabled:false

Add the following to your Datadog Agent manifest:

DD_REMOTE_CONFIGURATION_ENABLED=false

Add the following to your Helm chart:

datadog:remoteConfiguration:enabled:false

At the organization level

Datadog does not recommend disabling Remote Configuration at the organization level. Disabling Remote Configuration at the organization level prevents Datadog components in several products across your organization from receiving configurations from Datadog.

To disable Remote Configuration at the organization level:

  1. Ensure you have the required org_management permission.
  2. Go to the Remote Configuration settings page.
  3. Click Disable.
  4. When the warning message appears, click Disable again.

Further reading

Additional helpful documentation, links, and articles: