> This page is for Docs.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://zuora.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://zuora.ferndocs.com/_mcp/server.

# Configure Datadog integration for Observability Connector

> Configure a Datadog connector in OneID so that Zuora sends observability events to your Datadog account.

Configure a Datadog connector in OneID so that Zuora sends observability events to your Datadog account.

In OneID, go to **Admin Console** > **Observability Connector**.

Click the + icon. The **Add Connetor** dialog opens.

Choose **Sumo Logic** and click **Next**.

In **Name**, enter a name for the connector.

The name identifies the connector in the connector list. Use a name that indicates the destination, so that you can distinguish this connector from others that send to the same platform.

In **Site Region**, enter the regional instance that hosts your destination account.

For example, `us1` or `eu1`. If you enter a region that your destination account is not provisioned in, authentication fails even when the API key is valid.

In **Endpoint URL**, enter the address that Zuora sends events to.

The URL must use HTTPS. Include the full path to the receiving endpoint, not only the host.

In **API Key**, enter the key that authenticates Zuora to the destination platform.

In **Service**, enter the service name that Zuora sends with each event.

Use this value to group Zuora events by service in the destination platform.

In **Source**, enter the source name that Zuora sends with each event.

Destination platforms use this value to select the parsing rules that they apply to incoming events.

In **Tags**, enter the key-value pairs that Zuora attaches to each event.

Use tags to filter and group Zuora events in the destination platform.

Expand **Advanced settings** and set the options that your destination requires.

1. In **Connection Timeout (ms)**, enter how long Zuora waits to establish a connection to the endpoint.

   Zuora treats an attempt that exceeds this value as failed.
2. In **Read Timeout (ms)**, enter how long Zuora waits for a response after it sends events.

   A destination that acknowledges slowly under load needs a higher value.
3. In **Max Retries**, enter the number of times Zuora retries a failed delivery before it stops.

   The **Retries** column in the connector list shows the retry count for each connector.

Set the **Enabled** toggle.

The toggle is on by default, so a saved connector begins sending events immediately. Turn the toggle off to save the configuration without sending events.

Click **Test Connection**.

Zuora attempts to reach the endpoint with the values that you entered. Resolve any reported error before you continue.

Click **Save**.

The connector appears in the connector list. An enabled connector shows the status **Active**.