langfuse.worker.queue.depth
Background job queue sizeDimensions:None
Interface Metrics (2)
Dimensions:None
Technical Annotations (33)
Configuration Parameters (6)
ADMIN_API_KEYLANGFUSE_INGESTION_QUEUE_PROCESSING_CONCURRENCYrecommended: lower than defaultLANGFUSE_INGESTION_CLICKHOUSE_WRITE_BATCH_SIZErecommended: lower than defaultLANGFUSE_TOKEN_COUNT_WORKER_POOL_SIZErecommended: lower than 2 (default)NODE_OPTIONSrecommended: --max-old-space-size=6144LANGFUSE_INGESTION_CLICKHOUSE_WRITE_INTERVAL_MSrecommended: 100Error Signatures (8)
ERR Error running script (call to f_b588db2e6f108117dcfa5966b343f1203d60c649): @user_script:431: @user_script: 431: -OOM command not allowed when used memory > 'maxmemory'error codeQueue job trace-delete errored: ReplyErrorlog patternFATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memoryexceptionMark-Compactlog patternjob stalled more than allowable limitexceptionQueue job ingestion-job with idlog pattern504 Gateway Time-outhttp statusHTTPSConnectionPool(host='...'): Read timed out. (read timeout=exceptionCLI Commands (7)
curl -X GET "https://your-langfuse-instance.com/api/admin/bullmq" -H "Authorization: Bearer YOUR_ADMIN_API_KEY" -H 'Content-Type: application/json' --data '{"action": "retry", "queueNames": [ "ingestion-queue" ]}'monitoringcurl -X POST "https://your-langfuse-instance.com/api/admin/bullmq" -H "Authorization: Bearer YOUR_ADMIN_API_KEY" -H "Content-Type: application/json" -d '{"action": "retry", "queueNames": ["ingestion-queue", "evaluation-queue"]}'remediationcurl -X POST "https://your-langfuse-instance.com/api/admin/bullmq" -H "Authorization: Bearer YOUR_ADMIN_API_KEY" -H "Content-Type: application/json" -d '{"action": "remove", "queueNames": ["ingestion-queue"], "bullStatus": "failed"}'remediationps -eo pid,comm,args | awk "/[n]ode( |$)/ && !/node -e/ {print}"diagnostickill -USR1 $PIDdiagnosticcurl -v -X POST https://langfuse.perso.be/api/public/ingestion -H "Content-Type: application/json" -H "Authorization: Basic <base64_creds>" -d '{"batch": [{"type": "trace-create", "id": "test-trace-001", "timestamp": "2025-07-12T12:00:00.000Z", "body": {"id": "test-trace-001", "timestamp": "2025-07-12T12:00:00.000Z", "name": "curl-test"}}]}'diagnosticcurl -v https://langfuse.perso.be/api/public/ingestiondiagnosticTechnical References (12)
BullMQcomponentingestion-queuecomponentevaluation-queuecomponent/api/admin/bullmqcomponentNode.js heapconceptno-eviction cache policyconfigurationobservationsconceptingestion workerscomponentotel directoryfile path/api/public/ingestionendpointnginxcomponentingestion workercomponentRelated Insights (7)
BullMQ queue backlog requires monitoring and managementinfo
▸
Worker container high memory usage with low CPU under ingestion loadcritical
▸
Redis OOM blocks BullMQ job processing and ingestioncritical
▸
High-cardinality traces (10K+ spans) cause Node.js heap exhaustion in ingestion workerscritical
▸
BullMQ ingestion jobs stall when workers are unresponsive under memory pressurecritical
▸
Insufficient capacity amplifies networking issues into cascading failureswarning
▸
504 Gateway Timeout on ingestion endpoint while other API endpoints workcritical
▸