- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
",t};e.buildCustomizationMenuUi=t;function n(e){let t='
",t}function s(e){let n=e.filter.currentValue||e.filter.defaultValue,t='${e.filter.label}
`,e.filter.options.forEach(s=>{let o=s.id===n;t+=``}),t+="${e.filter.label}
`,t+=`This page covers configuring Remote Configuration for Fleet Automation. The following Fleet Automation features require Remote Configuration:
Datadog recommends upgrading your Agents regularly to make sure you have access to the latest features.
7.47.0
or later.org_management
, so you can enable Remote Configuration for your organization.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.Gain visibility into the Remote Configuration status of your Agent through the Remote Configuration UI.
The following table describes the meaning of each Agent status:
Agent Status | Description |
---|---|
CONNECTED | The Agent deployed in your environment is able to reach, authenticate, and authorize successfully to Datadog. This is the optimal state you want your Agents to be in for Remote Configuration. |
UNAUTHORIZED | The Agent deployed in your environment is able to reach Datadog but is not able to authenticate and authorize with Datadog for Remote Configuration operation. The most likely cause is the API Key used by the Agent is not Remote Configuration-enabled. To fix the issue, enable Remote Configuration capability on the API Key used by the Agent. |
CONNECTION ERROR | The Agent deployed in your environment 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 is that the Agent is unable to reach Remote Configuration endpoints. To fix the issue, allow outbound HTTPS access to Remote Configuration endpoints from your environment. This status displays when the Agent version is 7.45.0 or higher. |
DISABLED | The Agent deployed in your environment has remote_config.enabled set to false in its datadog.yaml configuration file. Set remote_config.enabled to true if you want to enable Remote Configuration on the Agent. This status displays when the Agent version is 7.45.0 or higher. |
NOT CONNECTED | The Agent cannot be found in the Remote Configuration service and 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. This status displays when the Agent version is higher than 7.41.1 but lower than 7.45.0 . |
UNSUPPORTED AGENT | The Agent is on a version that is not Remote Configuration capable. To fix this issue, update the Agent to the latest available version. |
You can disable Remote Configuration capabilities at the API key level and Agent 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.
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
If you experience issues using Remote Configuration, use the following troubleshooting guidelines. If you need further assistance, contact Datadog support.
After the Agent configuration is updated in the [datadog.yaml
][16] file, restart the Agent for th change to take effect.
To use Remote Configuration, the Agent deployed in your environment needs access to the Datadog Remote Configuration endpoints. For a private network connection between your environment and Datadog, you can also connect to Remote Configuration Virtual Private Cloud endpoints. Ensure that outbound HTTPS has access to Remote Configuration endpoints from your environment. If you also have a proxy in between Datadog and your environment, update your proxy settings to incorporate Remote Configuration endpoints.
To authenticate and authorize the Agent to receive configuration, enable Remote Configuration on the relevant API Key. Only users who have the api_keys_write
RBAC permission can enable Remote Configuration on the API Key.
Note: If you have api_keys_write
RBAC permission, but are missing Remote Configuration Organization level permissions, you cannot enable Remote Configuration on a new or an existing API Key. You only have permission to disable Remote Configuration on an existing API Key.