<a id="manage-observability-integrations"></a>

# Manage Observability Integrations on Confluent Cloud

Connect your third-party integrations in Confluent Cloud to simplify your observability
activities.

#### NOTE
Observability integrations are an Early Access Program feature in Confluent Cloud.


An Early Access feature is a component of Confluent Cloud introduced to gain
feedback. This feature should be used only for evaluation and non-production
testing purposes or to provide feedback to Confluent, particularly as it
becomes more widely available in follow-on preview editions.

Early Access Program features are intended for evaluation use in development
and testing environments only, and not for production use. Early Access Program
features are provided: (a) without support; (b) “AS IS”; and (c) without
indemnification, warranty, or condition of any kind. No service level commitment
will apply to Early Access Program features. Early Access Program features are
considered to be a Proof of Concept as defined in the Confluent Cloud Terms of Service.
Confluent may discontinue providing preview releases of the Early Access
Program features at any time in Confluent’s sole discretion.

If you want to participate in the Early Access Program, contact
Confluent at [obs.integration@confluent.io](mailto:obs.integration@confluent.io).

An observability integration is the connection from Confluent Cloud to a destination
that receives audit, Connect, Confluent Cloud for Apache Flink®, and Tableflow logs. Use these
integrations to send data to your preferred third-party observability tool,
centralize all your observability data, and store your data for longer
durations to comply with your internal data and security policies.

## Supported third-party observability integrations

The following integrations can be connected in Confluent Cloud Console:

* Datadog
* Splunk

## Manage destinations

A destination is a third-party endpoint, such as Datadog or Splunk, where
Confluent Cloud sends your observability data.

Destinations can be in a **Ready** or **Error** status.

### Create destination

1. In Confluent Cloud Console, open the sidebar menu. Below the current user name,
   click **Observability integrations**.
2. Click **Add destination**.
3. Select the provider for storing your logs. Insert the details for your
   destination.

   ### Datadog

   Provide the following details to configure Datadog as your
   observability destination. For more information, see
   [Datadog Logs documentation](https://docs.datadoghq.com/logs/).

   **Name**
   : A human-readable name for the destination, such as
     `my_datadog_destination`.

   **Description**
   : A description of the destination, such as “Send observability data
     to Datadog”.

   **Datadog Site**
   : Your Datadog site parameter. Select the appropriate site based on
     your region:
     * `datadoghq.com` for US1
     * `datadoghq.eu` for EU
     * `us3.datadoghq.com` for US3
     * `us5.datadoghq.com` for US5
     * `ap1.datadoghq.com` for AP1
     * `ddog-gov.com` for US1-FED

   **API Key**
   : Your Datadog API key ID for authentication. This key authenticates
     requests and sends data to your Datadog organization. For
     information on managing API keys, see
     [Datadog API Keys](https://docs.datadoghq.com/account_management/api-app-keys/).

   ### Splunk

   Provide the following details to configure Splunk as your observability
   destination. Confluent Cloud sends events using Splunk’s HTTP Event Collector
   (HEC). For more information, see
   [Splunk HTTP Event Collector documentation](https://help.splunk.com/en/splunk-enterprise/get-started/get-data-in/10.2/get-data-with-http-event-collector/set-up-and-use-http-event-collector-in-splunk-web).

   **Name**
   : A human-readable name for the destination, such as
     `my_splunk_destination`.

   **Description**
   : A description of the destination, such as “Send observability data
     to Splunk through HEC”.

   **HEC Endpoint**
   : The Splunk HTTP Event Collector endpoint URL where events are sent.

   **Index**
   : Optional. The Splunk index name where events are stored, such as
     `default`.

   **HEC Token**
   : Your Splunk HTTP Event Collector authentication token. This token
     authorizes the connector to send events to your Splunk instance.

   If your Splunk instance uses IP allowlisting, add the following
   static IP addresses to your allowlist: `44.226.85.132`,
   `44.235.136.122`, `44.241.78.207`, `35.161.229.13`,
   `35.160.220.191`, `52.38.2.235`, `52.43.84.211`,
   `44.212.112.178`, `98.85.95.222`, and `34.235.220.10`.
4. After you have entered the details, click **Complete**.

You receive confirmation that your destination was created. You can then set up
your observability integration.

### Edit destination

You can edit the details for your existing destination. This is helpful if you
need to update your API key or any additional details.

1. In Confluent Cloud Console, open the sidebar menu. Below the current user name,
   click **Observability integrations**.
2. Click your destination name.
3. Click **Edit**.
4. In the **Edit destination** panel, you can update the same details you
   entered when creating your destination.

   #### NOTE
   If you change the configuration details, you must also re-enter your
   destination credentials. You can change the **Name** and **Description**
   without re-entering your credentials.
5. Click **Save changes**.

Your changes to the destination are updated immediately.

### Delete destination

You can delete your existing destination.

1. In Confluent Cloud Console, open the sidebar menu. Below the current user name,
   click **Observability integrations**.
2. Click your destination name.
3. Click **Delete destination**.
4. Enter your destination name, which you can copy from the **Delete** window.
5. Click **Delete**.

Your destination no longer shows up on the **Observability integrations** page.

## Manage observability integrations

Observability integrations are the connection from Confluent Cloud to a destination.

Observability integrations can be in one of these statuses:

* **Active**
* **Error**
* **Provisioning**
* **Paused**
* **Resuming**
* **Updating**

### Create observability integration

1. In Confluent Cloud Console, open the sidebar menu. Below the current user name,
   click **Observability integrations**.
2. Click **Add observability integration**.
3. To set up your observability integration, enter the required details:

   **Name**
   : A name for the observability integration that describes the integration,
     such as `production_logs_to_datadog`.

   **Description**
   : A description of the observability integration, such as “Stream production
     cluster logs to Datadog for long-term storage”.

   **Destination**
   : Select the destination where logs are sent. Select the dropdown to see a
     list of your available configured destinations.

   **Log Source**
   : Select the log sources to include in the data streamed to your
     destination. Select the dropdown to see a list of your available sources.
4. Click **Create integration**.

You can now view your observability integration on the **Observability
integrations** page, along with their destination and status. From the
**Observability integrations** page, you can also edit your observability
integration to revise its name, description, destination, or log sources.

Observability data is not transferred while your observability integration is
**Provisioning**. After the integration is in the **Active** state, your data
starts to transfer.

### Edit observability integration

You can edit the details for your existing observability integrations. This is
helpful if you need to update any integration details, including log sources.

1. In Confluent Cloud Console, open the sidebar menu. Below the current user name,
   click **Observability integrations**.
2. Click your observability integration name.
3. Click **Edit**.
4. In the **Edit** panel, you can update the same details you entered when
   creating your observability integration.
5. Click **Save changes**.

Your changes to the observability integration are updated almost immediately.
While your observability integration is **Updating**, no observability data is
transferred to your destination from this observability integration.

### Pause observability integration

Pause your observability integration to temporarily stop transferring
observability data to a destination.

1. In Confluent Cloud Console, open the sidebar menu. Below the current user name,
   click **Observability integrations**.
2. Click your observability integration name.
3. On the observability integration page, select **Pause**.
4. Confirm you want to pause your integration.

While your observability integration is **Paused**, no observability data is
transferred to your destination from this observability integration.

### Resume observability integration

Resume your observability integration to start transferring observability data
to a destination again. When you resume your integration, Confluent Cloud transfers
only new observability data. Confluent Cloud does not transfer the data that was
created while the integration was paused.

1. In Confluent Cloud Console, open the sidebar menu. Below the current user name,
   click **Observability integrations**.
2. Click your observability integration name.
3. On the observability integration page, select **Resume**.
4. Confirm you want to resume your integration.

Observability data is not transferred while your observability integration is
**Resuming**. After the integration is in the **Active** state, your data starts
to transfer again.

### Delete observability integration

You can delete your existing observability integration.

1. In Confluent Cloud Console, open the sidebar menu. Below the current user name,
   click **Observability integrations**.
2. Click your observability integration name.
3. Click **Delete observability integration**.
4. Enter your observability integration name, which you can copy from the
   **Delete** window.
5. Click **Delete**.

Your observability integration no longer shows up on the **Observability
integrations** page.

## Related content

* [FAQ for Confluent Cloud Metrics](monitor-faq.md#metrics-api-faq)
* [Third-Party Monitoring](third-party-integration.md#ccloud-integrate-with-3rd-party-monitoring)
* [Monitor Tableflow](../topics/tableflow/operate/monitor-tableflow.md#tableflow-monitor)
* [Audit Log Concepts](audit-logging/cloud-audit-log-concepts.md#cloud-audit-logs)
* [Retain Audit Log Records](audit-logging/retain-audit-logs.md#retain-audit-log-records)
* [View Connector Events](../connectors/logging-cloud-connectors.md#ccloud-connector-logging)