> For the complete documentation index, see [llms.txt](https://docs.nimbus.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nimbus.dev/integrations/integrations.datadog/datadog.agent.md).

# DD Agent

### 1. Add Nimbus as a log endpoint

Add the following configuration to your datadog config

```yaml
observability_pipelines_worker:
  logs:
    enabled: true
    url: "https://YOUR_NIMBUS_ENDPOINT"
```

> NOTE: YOUR\_NIMBUS\_ENDPOINT is an URL that is generated for you when you first create an account

Optionally, you can configure the endpoint using the following environmental variables. This is useful when you're running the datadog agent in kubernetes like environments and don't have easy access to the raw configuration.

```bash
DD_OBSERVABILITY_PIPELINES_WORKER_LOGS_ENABLED=true 
DD_OBSERVABILITY_PIPELINES_WORKER_LOGS_URL="https://YOUR_NIMBUS_ENDPOINT"
```

Update your datadog agent to run with the new configuration. Congratulations - you're now forwarding log traffic with Nimbus!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nimbus.dev/integrations/integrations.datadog/datadog.agent.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.