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

# Configure Datadog Agent

> Forward logs to Bronto using the Datadog Agent, ideal for migrating existing Datadog-based pipelines without changing your application instrumentation.

The Datadog Agent can forward logs to Bronto in addition to Datadog using the `additional_endpoints` configuration. This page covers configuration only.

For installation instructions, see the [Datadog Agent documentation](https://docs.datadoghq.com/agent/).

## Endpoint and authentication

Use the ingestion endpoint for your Bronto region:

| Region | Host                     |
| ------ | ------------------------ |
| EU     | `ingestion.eu.bronto.io` |
| US     | `ingestion.us.bronto.io` |

Set `api_key` to your [Bronto API key](/Account-Management/API-Keys#create-a-new-api-key).

## Configuration

<Tabs>
  <Tab title="Linux">
    Edit `~/.datadog-agent/datadog.yaml` to add Bronto as an additional log endpoint:

    ```yaml datadog.yaml theme={"dark"}
    logs_config:
      additional_endpoints:
        - api_key: "<YOUR_API_KEY>"
          host: "ingestion.<REGION>.bronto.io"
          port: 443
          is_reliable: true
    ```

    By default, the dataset and collection where logs are sent are derived from the `service` and `source` tags reported by the Datadog Agent. These can be overridden with the `br_dataset` and `br_collection` log attributes if required.
  </Tab>

  <Tab title="Kubernetes/Helm">
    Add Bronto as an additional endpoint by upgrading the Datadog Agent Helm chart:

    ```bash theme={"dark"}
    helm upgrade datadog-agent -f datadog-values.yaml datadog/datadog
    ```

    ```yaml datadog-values.yaml theme={"dark"}
    datadog:
      podAnnotationsAsTags:
        kubernetes.annotations.logs.bronto.io/collection: br_collection
      logs:
        enabled: true
      customAgentConfig:
        logs_config:
          additional_endpoints:
            - api_key: "<BRONTO_API_KEY>"
              host: "ingestion.<REGION>.bronto.io"
              port: 443
              is_reliable: true
    ```

    Add the `kubernetes.annotations.logs.bronto.io/collection` annotation to pods whose logs should be forwarded to Bronto. Set its value to a unique identifier for the cluster, e.g. `<CLUSTER_NAME>-<ENVIRONMENT>-<REGION>`. The `podAnnotationsAsTags` entry maps this annotation to the `br_collection` log attribute, which Bronto uses to determine which collection to save the log data under.
  </Tab>
</Tabs>

For the full `additional_endpoints` configuration reference, see the [Datadog Agent log forwarding documentation](https://docs.datadoghq.com/agent/logs/?tab=tailfiles#send-logs-to-a-custom-endpoint).

## Verify Log Collection

Once you have applied your configuration and restarted the Datadog Agent, you can expect to see your log data being ingested to Bronto and accessible via the [Search](https://app.bronto.io/search) page.