Technologies/Traefik/traefik.service.retries.total
TraefikTraefikMetric

traefik.service.retries.total

Total request retries to service
Dimensions:None
Available on:PrometheusPrometheus (1)DatadogDatadog (1)Native (1)
Interface Metrics (3)
PrometheusPrometheus
Total number of request retries to a service
Dimensions:None
DatadogDatadog
Total count of request retries per service
Dimensions:None
Native
Total number of request retries to service
Dimensions:None
Sources
traefik_service_retries_totaldoc.traefik.io
traefik.service.retries.totaldocs.datadoghq.com
traefik.service.retries.totaldoc.traefik.io

Technical Annotations (12)

Configuration Parameters (3)
http.middlewares.retry.retry.attemptsrecommended: 3
Number of retry attempts before failing the request
retry.attemptsrecommended: 2
Fewer attempts reduce amplification during outages
retry.initialIntervalrecommended: 500ms
Longer interval spreads retry load over time
Error Signatures (1)
502 Bad Gatewayhttp status
CLI Commands (1)
kubectl logs -n traefik deployment/traefik | grep -i retrydiagnostic
Technical References (7)
Round Robinconceptload balancingconceptorchestratorconceptserver list refreshconceptretry middlewarecomponentcircuit breaker middlewarecomponentexponential backoffconcept
Related Insights (6)
Single backend server failure causes partial user impact in load-balanced setupwarning
▸
Excessive retry rate indicates backend instabilitywarning
▸
Configuration reload causes transient 502 errors during server list refreshwarning
▸
Retry middleware mitigates 502 errors from transient upstream failuresinfo
▸
Retry storms overwhelm recovering backend servicescritical
▸
High retry rate indicates persistent backend failureswarning
▸