traefik.service.connections.open
Open connections to serviceDimensions:None
Technical Annotations (19)
Configuration Parameters (9)
serversTransport.maxIdleConnsPerHostrecommended: default (not -1)serversTransport.forwardingTimeouts.idleConnTimeoutrecommended: default 90 secondsrespondingTimeouts.readTimeoutrecommended: p90 request durationrespondingTimeouts.writeTimeoutrecommended: p90 request durationrespondingTimeouts.idleTimeoutrecommended: p90 request durationbackends.[name].loadbalancer.maxConnectionsentryPoints.*.transport.respondingTimeouts.readTimeoutentryPoints.*.transport.respondingTimeouts.idleTimeoutentryPoints.*.transport.respondingTimeouts.writeTimeoutCLI Commands (1)
lsof -p $(pgrep traefik)diagnosticTechnical References (9)
apache 32bitcomponentactivemqcomponentdeadlockconceptsynchronizationconceptrequest durationconcepterror ratiosconceptTIME_WAITconceptmaxIdleConnsPerHostcomponententrypointcomponentRelated Insights (8)
Timeouts occur when proxying to Apache backend despite backend capacitywarning
▸
Code deadlocks from excessive synchronization cause service outagescritical
▸
Monitoring raw traffic totals delays detection of production health issuesinfo
▸
Disabling keep-alive causes excessive TIME_WAIT connectionswarning
▸
Open connections accumulate to 5k threshold causing traffic routing failurecritical
▸
Backend maximum connections limit prevents connection pile-upwarning
▸
Entrypoint open connections metric reports non-existent connectionswarning
▸
Globally increased timeouts enable easier DDoS attackswarning
▸