---
title: SDK Configurations
description: >-
  Use the SDK configurations view to validate setup, and troubleshoot
  instrumentation issues.
breadcrumbs: Docs > APM > APM Troubleshooting > SDK Configurations
---

# SDK Configurations

## Overview{% #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{% #access-sdk-configurations %}

To view SDK configurations for a service:

1. Navigate to [**APM** > **Services**](https://app.datadoghq.com/software).
1. Open the **Service Page** for your service.
1. Go to **Service Config** > **SDK & Agent Configurations** tab.

The **SDK Configurations** section displays configurations for active instances of the service.

## Configuration sources{% #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](https://docs.datadoghq.com/tracing/trace_collection/runtime_config)    |
| **Code**                            | Set in application code                                                                                                            |
| **Remote Fleet Automation**         | Applied remotely at the host level through [Fleet Automation](https://docs.datadoghq.com/agent/fleet_automation/remote_management) |
| **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{% #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](https://docs.datadoghq.com/agent/configuration/network/#destinations)).
- The service name is manually set on spans (a [Service Override](https://docs.datadoghq.com/tracing/guide/base_service/#service-overrides)).