Technologies/Express/express.eventloop.lag.max
ExpressExpressMetric

express.eventloop.lag.max

Maximum event loop lag
Dimensions:None
Available on:PrometheusPrometheus (1)
Interface Metrics (1)
PrometheusPrometheus
Maximum recorded event loop lag in seconds
Dimensions:None

Technical Annotations (24)

Configuration Parameters (3)
prisma.transaction.timeoutrecommended: 5000
Default Prisma transaction timeout in milliseconds
thresholdrecommended: 100
Event loop delay threshold in ms for warning alerts
resolutionrecommended: 10
Resolution for monitorEventLoopDelay histogram in ms
Error Signatures (2)
Transaction already closed: A query cannot be executed on an expired transactionexception
Invalid `prisma.taskAttempt.create()` invocation: Transaction API errorexception
CLI Commands (8)
node --trace-sync-io app.jsdiagnostic
npx clinic doctor -- node app.jsdiagnostic
npm install -g 0xdiagnostic
0x app.jsdiagnostic
node --inspect your_app.jsdiagnostic
clinic doctor -- node your_app.jsdiagnostic
npm install event-loop-lagmonitoring
node --trace-sync-io server.jsdiagnostic
Technical References (11)
PM2componentevent loopconceptfs.readFileSynccomponentcrypto.pbkdf2SynccomponentPrismacomponentV8 profilercomponentprocess.hrtime.bigint()componentfs.readFilecomponentasync/awaitconceptperf_hookscomponentmonitorEventLoopDelaycomponent
Related Insights (10)
Event loop lag exceeds 10-20ms thresholdwarning
Synchronous operations block event loop and tank throughputcritical
Prisma transaction timeouts due to event loop blockingcritical
High event loop lag degrades API responsivenesswarning
Synchronous file I/O blocks event loop in productioncritical
Event loop blocking causes complete application unresponsivenesscritical
Event loop delay exceeding 100ms indicates blockingwarning
Synchronous functions block event loop under high trafficwarning
Event-loop stalls invisible without direct lag measurementcritical
Event loop lag indicates delayed task executionwarning