# Datadog Log Integration (OpenTelemetry)

CloudAMQP ships broker logs to Datadog via **OpenTelemetry Protocol (OTLP).** Available on RabbitMQ and LavinMQ dedicated instances.

Link: [https://www.datadoghq.com](https://www.datadoghq.com)

## Setup

1. In Datadog, go to **Organization Settings → API Keys** and copy an existing key or create a new one.
2. In the CloudAMQP console, select **Datadog** under Log Integrations. Enter your API key, select your region, and optionally add tags in `key=value` format (e.g. `env=prod,team=platform`).
3. Click **Save.**

Setting a `service=` tag overrides the service name in Datadog — otherwise it defaults to your cluster name.

## Log format

- **HOST** — node hostname (e.g. `my-cluster-01`)
- **SERVICE** — cluster name, or overridden by your `service=` tag
- **SOURCE** — `cloudamqp`

Log record body:

```json
{
  "appname": "lavinmq",
  "otel": {
    "service": { "name": "my-cluster" },
    "severity_number": 17,
    "timestamp": 1783083429237880000
  },
  "user_agent": "CloudAMQP OTel Collector/0.0.69 (linux/arm64)"
}
```

## If you're coming from the legacy integration

- **Severity is now a number** — `otel.severity_number` (17 = ERROR, 9 = INFO), not embedded as text in the message.
- **Message is clean** — no timestamp, PID, or log level prefix.
- **Timestamp is nanosecond epoch** — Datadog handles the conversion automatically, but be aware if you have custom log processors.
- **One stream per node** — on multi-node clusters you'll see individual streams per host rather than a single aggregated stream.

Review any existing monitors, dashboards, or log processors that depend on the legacy format before switching.

[← Back to Log Integrations](/docs/cloudamqp-integrations/#otel-logs)
