> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agents.labs.bandwidth.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Datadog

> Export agent metrics, individual call results, and conversation traces to Datadog.

Connect Datadog to monitor agents in your selected workspace. You can choose which data to export and review delivery status for each signal.

## Before you begin

You need Admin or Owner access to the workspace, your Datadog site, and a [Datadog API key](https://docs.datadoghq.com/account_management/api-app-keys/) for that account. You do not need a Datadog application key. Conversation traces require access to Datadog's [Agent Observability](https://docs.datadoghq.com/llm_observability/quickstart/) product.

## Connect your account

1. Select the intended workspace, then open **Resources → External integrations → Datadog**.

2. Choose your **Datadog site** and enter your **Datadog API key**.

3. Under **Data to export**, select one or more signals:

   | Signal                      | What you receive                                                                                 |
   | --------------------------- | ------------------------------------------------------------------------------------------------ |
   | **Agent metrics**           | Rolling 24-hour call counts, outcomes, duration, usage, quality scores, and response performance |
   | **Individual call results** | A result for each completed call, with revisions when usage or quality results arrive later      |
   | **Conversation traces**     | Recorded call and turn timelines, model usage, tool names, timings, and error status             |

4. Select **Enable export**, then **Save connection**.

You can use **Test API key** to check the credential before saving. This checks authentication; it does not confirm that data has arrived in Datadog.

<Note>
  Datadog exports exclude transcripts, prompts, model responses, tool arguments and results, recordings, and phone numbers. Call results and traces begin with new calls after enablement. Metrics can include calls from the previous 24 hours.
</Note>

## Verify delivery

Complete a new browser test or inbound call. Include a model response or tool action if you selected conversation traces. Return to **Delivery status** and select **Refresh status** after about a minute. Review each selected signal separately, then confirm the data in Datadog.

| Data                    | Where to look in Datadog                                                   |
| ----------------------- | -------------------------------------------------------------------------- |
| Metrics                 | Metrics Explorer: `voai.customer.*`                                        |
| Individual call results | Logs Explorer: `service:voai-customer`; filter a call with `@voai.call_id` |
| Conversation traces     | Agent Observability: `ml_app:voai-customer`                                |

Select **Download Datadog dashboard** to import the supplied dashboard into Datadog. Filter by integration, agent, and channel. The metrics describe a rolling 24-hour window; do not sum snapshots as if they were separate calls. Call result revisions can produce multiple log entries for one call.

If data is missing, check the selected site, enabled signals, and any delivery error. **Connected** means credentials are saved. An API key check or successful delivery status alone does not confirm that your Datadog account has indexed the data or enabled the required product.

## Update, pause, or disconnect

Leave the API key blank when editing an existing connection to keep the saved key. Enter a key when changing sites. Members can view settings and delivery status; only Admins and Owners can change or test the connection.

Clear **Enable export** and save to pause delivery. When you resume, call results and traces start with new calls; calls from the paused period are not backfilled.

Select **Disconnect** to remove the saved connection and pending deliveries. Data already sent stays in Datadog, and a request already in progress can finish after you pause or disconnect. If you are switching to a different Datadog account at the same site, disconnect before configuring the new account.