traefik.service.requests.total

Total requests to service

Dimensions:None

Technical Annotations (25)

Configuration Parameters (6)

traefik.http.services.<service>.loadbalancer.server.portrecommended: 8080

Must be set explicitly when container exposes multiple ports

entrypoints.<name>.transport.respondingtimeouts.readtimeoutrecommended: 60-300

Maximum seconds for reading entire request including body; 0 disables

serversTransport.forwardingTimeouts.idleConnTimeoutrecommended: shorter than upstream timeout (e.g., 3s if upstream is 5s)

Controls how long Traefik keeps idle connections to upstream servers open

serversTransport.maxIdleConnsPerHostrecommended: default (not -1)

Setting to -1 disables keep-alive entirely, causing performance issues

retry.attemptsrecommended: 2

Fewer attempts reduce amplification during outages

retry.initialIntervalrecommended: 500ms

Longer interval spreads retry load over time

Error Signatures (5)

404 page not foundhttp status

502 Bad Gatewayhttp status

dial tcp [IP]:[port]: connect: connection refusedlog pattern

read: connection reset by peerlog pattern

502http status

CLI Commands (3)

docker exec -it traefik sh -lc 'wget -qO- http://127.0.0.1:8080/api/http/services | jq -r ".[] | select(.name==\"app-svc@docker\") | .loadBalancer.servers"'

diagnostic

docker ps --format 'table {{.Names}}\t{{.Image}}\t{{.Status}}\t{{.Ports}}'diagnostic

kubectl logs -n traefik deployment/traefik | grep -i retrydiagnostic

Technical References (11)

Servicecomponentloadbalancer.server.portcomponentHTTP request timeoutconceptServersTransportcomponentforwardingTimeoutscomponentkeep-aliveprotocolpkg/middlewares/accesslogcomponentpkg/proxy/httputil/proxy.gofile pathErrorHandlerWithContextcomponentcircuit breaker middlewarecomponentexponential backoffconcept

Related Insights (7)

Auto-detected service port routes to wrong container port with multiple exposed portscritical

▸

Excessive retry rate indicates backend instabilitywarning

▸

Read timeout terminates slow uploads and large POST requestswarning

▸

Idle timeout mismatch between Traefik and upstream causes 502 errorscritical

▸

502 Bad Gateway errors lack failure details in access logswarning

▸

Retry storms overwhelm recovering backend servicescritical

▸

High retry rate indicates persistent backend failureswarning

▸