Technologies/Traefik/traefik.service.server.health
TraefikTraefikMetric

traefik.service.server.health

Backend server health status
Dimensions:None
Available on:PrometheusPrometheus (1)DatadogDatadog (1)Native (1)
Interface Metrics (3)
PrometheusPrometheus
Current health status of a backend server
Dimensions:None
DatadogDatadog
Current status of backend servers (1 for up, 0 for down)
Dimensions:None
Native
Current health status of service server
Dimensions:None
Sources
traefik_service_server_updoc.traefik.io
traefik.service.server.updocs.datadoghq.com
traefik.service.server.updoc.traefik.io

Technical Annotations (24)

Configuration Parameters (2)
--providers.docker.networkrecommended: edge
Restricts Traefik to only discover services on specified network
traefik.docker.networkrecommended: <shared_network_name> (e.g., traefik_proxy)
Docker Compose label that explicitly specifies which network Traefik should use for service discovery when container is attached to multiple networks
Error Signatures (5)
502 Bad Gatewayhttp status
504 Gateway Timeouthttp status
dial tcp [IP]:[port]: connect: connection refusedlog pattern
read: connection reset by peerlog pattern
502http status
CLI Commands (6)
docker inspect traefik --format '{{json .Config.Cmd}}'diagnostic
docker inspect app --format '{{json .NetworkSettings.Networks}}'diagnostic
docker exec -it traefik sh -lc 'wget -qSO- http://172.24.0.5:8080/health -O /dev/null'diagnostic
docker ps --format 'table {{.Names}}\t{{.Image}}\t{{.Status}}\t{{.Ports}}'diagnostic
docker-compose up -d --force-recreate backenddiagnostic
curl http://traefik-metrics.traefik:8082/metrics | grep traefik_service_requests_totaldiagnostic
Technical References (11)
Docker networkcomponent--providers.docker.networkcomponent0.0.0.0concept127.0.0.1conceptDocker providercomponentservice discoveryconceptRound Robinconceptload balancingconceptpkg/middlewares/accesslogcomponentpkg/proxy/httputil/proxy.gofile pathErrorHandlerWithContextcomponent
Related Insights (7)
Network isolation prevents Traefik from reaching container backendscritical
▸
502 Bad Gateway when backend unreachable despite router matchcritical
▸
Traefik 504 Gateway Timeout after backend container restart on multiple networkscritical
▸
Single backend server failure causes partial user impact in load-balanced setupwarning
▸
High 5xx error rate indicating backend or routing failurescritical
▸
Backend service down detected by health checkcritical
▸
502 Bad Gateway errors lack failure details in access logswarning
▸