OTLP Log Integration

The OTLP log integration ships broker logs from your CloudAMQP cluster to any backend that accepts OpenTelemetry logs over OTLP/HTTP, such as SigNoz or Honeycomb. Available on RabbitMQ and LavinMQ dedicated instances.

If your backend has a dedicated integration, use that instead. They are preconfigured for the endpoint and authentication the vendor expects. See the list of OTel log integrations.

Endpoint

The endpoint is the full https URL your backend receives logs on, including the path. It must use HTTPS. Most OTLP/HTTP backends document a base URL, so add /v1/logs to it:

https://otlp.example.com:4318/v1/logs
https://api.honeycomb.io/v1/logs
https://ingest.eu.signoz.cloud:443/v1/logs

Logs are sent to the URL exactly as entered, so a gateway that listens on another path works too.

Authentication

Four authentication modes are available:

None

No credentials are sent as such. Use this when the receiver carries its token in the endpoint URL as a query parameter, for example ?token=your-token

Basic Auth

A username and a password or token are sent as an HTTP Basic Authorization header.

Headers

The credentials live in the headers below, for example Authorization: Bearer your-token Use this for bearer tokens and for receivers that expect an API key header.

OAuth2

We fetch an access token with the OAuth2 client credentials flow and refresh it as needed. Enter the client ID, the client secret and the token URL of your identity provider, plus any scopes it requires.

Authentication runs through the OpenTelemetry Collector oauth2client extension. Of its options we expose four, with the same names it uses: client_id , client_secret , token_url and scopes . Enter scopes space or comma separated, and we pass them on as a list.

Headers

Headers are sent with every request, whichever authentication mode you pick, so you can combine them with basic auth or OAuth2. Enter one header per line in the format key: value

Most hosted OTLP backends take their API key as a header. Honeycomb reads x-honeycomb-team and SigNoz Cloud reads signoz-ingestion-key . Check your backend's OTLP ingestion documentation for the header name it expects.

Log attributes

Logs arrive as structured OpenTelemetry log records. Each record carries the resource attributes service.name (your cluster name) and host.name (the node hostname), the log attribute appname ( rabbitmq or lavinmq ) and a severity number mapped from the broker log level. The full list is in the OTel log integrations overview.

Setup

1. Enter the full https URL your backend receives logs on, usually the base URL followed by /v1/logs .
2. Select an authentication mode and fill in the credentials it needs.
3. Add any headers your receiver expects, such as an API key header.
4. Click Save.

← Back to Log Integrations