OpenTelemetry Tracing - resource attribute service.name = unknown_service:traefik

Traefik Traefik v3 (latest)
1

Traefik Version: 3.0.0-beta2
Install Method: Docker via Docker

OpenTelemetry Tracing - resource attribute `service.name = unknown_service:traefik` · Issue #9617 · traefik/traefik · GitHub claims that Fix OpenTelemetry service name by tomMoulard · Pull Request #9619 · traefik/traefik · GitHub should correct the issues with OpenTelemetry showing unknown_service:traefik as the OTEL service name, however this does not appear to be the case.

My docker-compose is as follows:

  traefik:
    image: "traefik:v3.0.0-beta2"
    container_name: "traefik"
    command:
      - "--api.insecure=true"
      - "--providers.docker=true"
      - "--providers.docker.exposedbydefault=false"
      - "--providers.docker.endpoint=unix:///var/run/balena-engine.sock"
      - "--entrypoints.web.address=:80"
      - "--entrypoints.ldap.address=:389"
      - "--tracing.opentelemetry=true"
      - "--tracing.opentelemetry.address=bindplanecollector:4318"
      - "--tracing.opentelemetry.insecure=true"
      - "--metrics.opentelemetry=true"
      - "--metrics.opentelemetry.address=bindplanecollector:4318"
      - "--metrics.opentelemetry.insecure=true"
      - "--metrics.openTelemetry.addRoutersLabels=true"
      - "--log.format=json"
      - "--accesslog=true"
      - "--accesslog.format=json"
      - "--accesslog.filePath=/data/traefik_logs/access.log"
      - "--log.filePath=/data/traefik_logs/traefik.log"
    ports:
      - "80:80"
      - "8080:8080"
    labels:
      - "io.balena.features.balena-socket=true"
      - "io.balena.features.supervisor-api=true"
    volumes:
      - "traefik_logs:/data/traefik_logs"

Metrics and traces are being sent to the collector correctly, but the service is still unknown_service:traefik. Ideally, this would be traefik:<router_name>, but just traefik (as detailed in the PR) would suffice.

Have I missed an argument somewhere?

2

If you check the release page, you will find that "3.0.0-beta2" is from "Dec 7, 2022", so before the fix was created.

It seems the focus of the Traefik team has been more on a stable v2.10 and not on refreshing v3 beta.

1 Like
3

Good spot, I'd completely missed that.

I'll run up my own container for now and see how that goes :slight_smile:

4

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.