이 페이지는 아직 한국어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우
언제든지 연락주시기 바랍니다.Overview
The SDK Configurations view shows the active configurations of SDKs per service. Configurations are automatically reported from the SDKs. Use the view to:
- Troubleshoot instrumentation issues, including where configurations are inconsistent across instances of a service.
- Validate that a configuration change was deployed correctly across intended instances.
- Identify the source of a configuration value to help fix misconfigurations.
- Discover available configuration options and how they are set.
Access SDK configurations
To view SDK configurations for a service:
- Navigate to APM > Services.
- Open the Service Page for your service.
- Go to Service Config > SDK & Agent Configurations tab.
The SDK Configurations section displays configurations for active instances of the service.
Configuration sources
The configuration source shows where a given value is configured:
| Source | Description |
|---|
| Remote Configuration at Runtime | Set through the Datadog UI using Configuration at Runtime |
| Code | Set in application code |
| Remote Fleet Automation | Applied remotely at the host level through Fleet Automation |
| Local environment variable | Set through an environment variable (or system property) in the runtime environment |
| Local file | Set in a local configuration file |
| Default | Default value provided by the SDK |
Missing configuration data
Telemetry data is not available in the following situations:
- No service instances have been active in the last 15 minutes.
- Instrumentation telemetry has been disabled in configuration.
- The instrumentation telemetry intake endpoint is not accessible (see Network Destinations).
- The service name is manually set on spans (a Service Override).
