Skip to main content
Collect Traefik access logs β€” routing decisions, backend responses, and latency β€” with the OpenTelemetry Collector. The same Collector can also forward traces and metrics from your apps β€” see Connect OpenTelemetry Collector to Bronto.

Prerequisites

Enable a JSON access log in traefik.yaml:
traefik.yaml

Configure the Collector

Traefik’s JSON access log is one object per line β€” parse it with json_parser:
/etc/otel/config.yaml
Set <REGION> to eu or us.

What you will see in Bronto

Open Search and filter by service.name = traefik. Each entry carries the client address (ClientHost), entrypoint, router and service names, method (RequestMethod), path (RequestPath), status (DownstreamStatus), duration (Duration), and backend URL. The JSON fields map directly to searchable attributes.

Troubleshooting

  • No log file? Traefik logs to stdout unless accessLog.filePath is set. Add the accessLog block above and set format: json for automatic field extraction.
  • For general issues, see OTel Collector troubleshooting.

Alternative: Fluent Bit

If you already run Fluent Bit, tail the Traefik access log and forward it over HTTP:
fluent-bit.conf
Set Format to json_lines, not json. See Connect Fluent Bit to Bronto for installation.