OpenTelemetry logs

Fluxtail accepts OTLP logs. This receiver does not accept traces or metrics.

Prerequisites

Create the matching OTLP HTTP or OTLP gRPC receiver and a token bound to it. Copy the exact endpoint shown by Fluxtail.

OTLP/HTTP

Use the exact logs endpoint:

https://ingest.fluxtail.io/v1/receivers/RECEIVER_ID/otlp/v1/logs

Send Authorization: Bearer TOKEN. The body may be OTLP JSON or protobuf. Optional HTTP gzip encoding is supported.

OpenTelemetry Collector:

exporters:
  otlphttp/fluxtail:
    logs_endpoint: ${env:FLUXTAIL_OTLP_LOGS_URL}
    headers:
      Authorization: "Bearer ${env:FLUXTAIL_TOKEN}"

service:
  pipelines:
    logs:
      exporters: [otlphttp/fluxtail]

Do not append /v1/logs when logs_endpoint already contains the exact Fluxtail receiver path.

OTLP/gRPC

Use ingest.fluxtail.io:443. The exporter calls the standard OTLP LogsService Export method. Send the receiver token as Bearer metadata; no receiver ID metadata is required.

exporters:
  otlp/fluxtail:
    endpoint: ingest.fluxtail.io:443
    headers:
      Authorization: "Bearer ${env:FLUXTAIL_TOKEN}"

Verify

Emit one log from the Collector, open the configured stream in Live Tail, and filter by its service name.

Troubleshooting

• Confirm the receiver type matches HTTP or gRPC.
• Confirm the exporter is sending logs, not traces or metrics.
• Keep normal public CA and hostname verification enabled.
• For HTTP protobuf, use application/x-protobuf; for JSON, use application/json.

Next steps

Confirm resource and service attributes with search and filters, then add Collector batching and retry settings appropriate for your workload. See the official OpenTelemetry Collector configuration guide for pipeline options.