Technologies/Traefik/traefik.entrypoint.request.duration
TraefikTraefikMetric

traefik.entrypoint.request.duration

Request duration at entrypoint
Dimensions:None
Available on:PrometheusPrometheus (1)DatadogDatadog (1)Native (1)
Interface Metrics (3)
PrometheusPrometheus
Request processing duration histogram
Dimensions:None
DatadogDatadog
Request processing duration at the entrypoint level
Dimensions:None
Native
Request processing duration at entrypoint
Dimensions:None
Sources
traefik_entrypoint_request_duration_secondsdoc.traefik.io
traefik.entrypoint.request.durationdocs.datadoghq.com
traefik.entrypoint.request.durationdoc.traefik.io

Technical Annotations (58)

Configuration Parameters (16)
ADVERTISE_IPrecommended: Internal IP address (e.g., https://192.168.0.100:32400/) rather than external domain
Plex environment variable that may reduce hairpin NAT reliance
accessLog.filters.minDurationrecommended: 10ms
logs only requests exceeding this duration for performance analysis
traefik.http.routers.*.middlewaresrecommended: authelia@file (single middleware, not chained with CrowdSec)
Avoid chaining multiple ForwardAuth middlewares to prevent request context corruption
entrypoints.<name>.transport.lifecycle.gracetimeoutrecommended: 30-60
Seconds to wait for active requests during graceful shutdown
entrypoints.<name>.http2.maxconcurrentstreamsrecommended: 250-1000
Maximum parallel requests per HTTP/2 connection
respondingTimeouts.readTimeoutrecommended: p90-p99 percentile
Start at p90 for diagnosis, tune to p99 for production
respondingTimeouts.writeTimeoutrecommended: p90-p99 percentile
Start at p90 for diagnosis, tune to p99 for production
respondingTimeouts.idleTimeoutrecommended: p90-p99 percentile
Start at p90 for diagnosis, tune to p99 for production
entryPoints.name.transport.respondingTimeouts.readTimeoutrecommended: 60
Default 60s; maximum duration for reading entire request including body
entryPoints.name.transport.respondingTimeouts.writeTimeoutrecommended: 0
Default 0s (no timeout); maximum duration for writing response to client
readTimeout
Configuring this mitigates indefinite hangs from Content-Length on GET requests
entryPoints.{name}.transport.respondingTimeouts.readTimeoutrecommended: 15s in example; increase for services with large request bodies (>1MiB)
Timeout for reading entire request including body; too low causes legitimate slow uploads to fail with misleading HTTP 499
experimental.fastProxyrecommended: enabled in example
Experimental feature that changes timeout error representation from HTTP 499 to HTTP 504
entryPoints.*.transport.respondingTimeouts.readTimeoutrecommended: 600s
Maximum duration for reading request including body for large uploads
entryPoints.*.transport.respondingTimeouts.idleTimeoutrecommended: 600s
Maximum duration an idle connection remains open during large uploads
entryPoints.*.transport.respondingTimeouts.writeTimeoutrecommended: 600s
Maximum duration for writing response for large file operations
Error Signatures (7)
499http status
499 Client Closed Requestlog pattern
context canceledlog pattern
504http status
504 Gateway Timeoutlog pattern
Error while writing request error="read tcplog pattern
i/o timeoutlog pattern
CLI Commands (4)
apt install crowdsec-firewall-bouncer-iptablesremediation
docker run --name swiss-army-knife --net=container:traefik -itd leodotcloud/swiss-army-knifediagnostic
time curl -svL http://whoami.mydomain.com |& ts '[%Y-%m-%d %H:%M:%.S]'diagnostic
tcpdump -n -i eth1diagnostic
Technical References (31)
cronjobcomponentlog rotationconceptresource constraintsconceptworkloadconceptdisk I/OcomponentPuma 6 chipsetcomponenthairpin NATconceptloopback functionalityconceptlatencyconceptrequest durationconcepterror ratiosconceptForwardAuthcomponentTraefik v3componentmiddleware chainconceptgraceful shutdownconceptHTTP/2protocolHTTP/2 streamsconceptp50conceptp90conceptp99conceptreadTimeoutcomponentwriteTimeoutcomponentContent-LengthprotocolentryPointcomponentrespondingTimeoutsconceptfastProxycomponentmacvlancomponentbridge networkcomponentARPprotocolTCP retransmissionconceptentryPointscomponent
Related Insights (20)
Log rotation background jobs cause periodic response time spikeswarning
▸
Resource saturation causes request response time degradationcritical
▸
Disk I/O bottleneck delays all requests globallycritical
▸
User expectation of 2-second response time thresholdinfo
▸
Router loopback bug causes 100x latency increase when accessing Traefik via external domain from internal networkcritical
▸
High request latency at p99 degrading user experiencewarning
▸
Uptime-based alerts waste debugging time compared to latency spike alertsinfo
▸
Monitoring raw traffic totals delays detection of production health issuesinfo
▸
Chained ForwardAuth middlewares cause request timeouts and silent failurescritical
▸
Graceful shutdown timeout too short terminates in-flight requestswarning
▸
HTTP/2 concurrent stream limit causes request queueingwarning
▸
Timeout configuration should be based on request duration percentilesinfo
▸
Read timeout too low causes rejection of legitimate slow requestswarning
▸
Write timeout terminates response transmission before completionwarning
▸
Content-Length header on GET requests causes indefinite hangcritical
▸
Slow client request bodies exceeding readTimeout logged as HTTP 499 Client Closed Requestwarning
▸
fastProxy enabled changes readTimeout violations to HTTP 504 Gateway Timeoutwarning
▸
Multi-network Docker configuration causes 5-second connection delayswarning
▸
Routed traffic through gateway causes TCP retransmissions and delayswarning
▸
Large file uploads fail due to default Traefik timeout valueswarning
▸