Technologies/Jaeger/express.http.request.duration
JaegerJaegerMetric

express.http.request.duration

HTTP request duration histogram
Dimensions:None

Technical Annotations (39)

Configuration Parameters (3)
NODE_ENVrecommended: development
When set to 'development', stack traces are included in error responses for debugging
corsOptions.maxAgerecommended: 600
Seconds to cache preflight; 10 minutes recommended for production
UV_THREADPOOL_SIZErecommended: 8
Increase from default 4 for heavy I/O on multi-core systems
CLI Commands (2)
npx clinic doctor -- node app.jsdiagnostic
node --trace-event-categories v8,node,node.async_hooks,node.perfdiagnostic
Technical References (34)
morgancomponenttracer.startActiveSpancomponentspan.recordExceptioncomponentPerformanceObservercomponentperformance.markcomponentperformance.measurecomponentexpress-status-monitorcomponentSequelizecomponentMongoosecomponentv8-profilercomponentClinic.jscomponentRediscomponentMemcachedcomponentsaturation pointconceptthroughputconceptmiddleware chainconcepterror-handling middlewarecomponentexpress-async-errorscomponentExpress 4.xcomponentExpress 5.xcomponentPromise.resolve().catch(next)conceptexpress.static()componentAccess-Control-Max-AgeprotocolN+1 queriesconceptconnection poolingconceptevent loopcomponentcallback queuecomponentreplicacomponentsingle-threadedconceptdistributed tracingcomponentSSRconceptWorker Threadscomponentworker_threadscomponentsetImmediate()component
Related Insights (21)
Slow API response times indicate processing bottleneckswarning
▸
Express async middleware timing not accurately measuredinfo
▸
Slow operations over 100ms threshold degrade user experiencewarning
▸
Slow database queries degrade response timeswarning
▸
High response times from application bottleneckswarning
▸
Network latency degrading response timeswarning
▸
Application saturation causing response time spikes or failurescritical
▸
Error handler positioned before routes silently swallows all errorscritical
▸
Async errors in Express 4.x never reach error handlerscritical
▸
Late express.static() placement increases request latencywarning
▸
Uncached preflight requests add 10-30% overhead to POST-heavy routesinfo
▸
Poorly optimized database queries delay callback executionwarning
▸
Event loop 100% utilization causes request latency spikes and timeoutscritical
▸
Horizontal scaling mitigates event loop starvation when under-provisionedwarning
▸
Event loop blocking misdiagnosed as downstream service latencywarning
▸
Response timer includes event loop wait time in observed latencyinfo
▸
High p99 latency from event loop blocking patternswarning
▸
APM sampling hides frequent short event-loop stallswarning
▸
Event loop congestion causes severe response time degradation at scalecritical
▸
CPU-intensive operations block event loop for secondscritical
▸
Event loop lag over 300ms causes API response time degradationcritical
▸