BullMQ queue monitoring

Test the integration

Send and verify events with BullMQ queue monitoring

Use BullMQ queue monitoring where your app knows the final result. Collect only the fields you need, then verify a test event before building charts.

1
Choose the outcome
BullMQ worker health
2
Define the contract
job_id, job_name, queue_name, and status
3
Log the final result
Use BullMQ's job ID as the logical ID and record attemptsMade separately.
4
Check the stored event
Exercise a known fixture, then inspect job_completed for one correctly typed terminal row.

Before you start

A server-side TELEMETRY_API_KEY
Stable job names and queue names
Job timestamps preserved across retries

Delivery setup

Install and initialize server-side

Import telemetry-sh in server-only code and initialize it once with process.env.TELEMETRY_API_KEY. Keep ingestion credentials out of browser bundles, client-visible environment variables, source control, logs, and exception messages.

bullmq-install

npm installation

bash

npm install telemetry-sh

1Create one reusable server-side client. Set its timeout and retry limit.
2Log an event when the operation succeeds, fails, retries, or times out.
3Send test events with known results and inspect the stored rows before enabling an alert.

Snippet

Start with one structured event

Add this shape where the workflow completes, fails, or retries. Then build the dashboard from real fields.

bullmq

BullMQ queue monitoring event

javascript

worker.on("completed", async (job, result) => {
  await telemetry.log("job_completed", {
    job_id: String(job.id),
    job_name: job.name,
    queue_name: worker.name,
    status: "success",
    attempt: job.attemptsMade + 1,
    queue_wait_ms: job.processedOn - job.timestamp,
    duration_ms: job.finishedOn - job.processedOn,
    item_count: result?.itemCount,
  });
});

Event schema

job_id, job_name, queue_name, and status

attempt, queue_wait_ms, duration_ms, and error_type

item_count, worker_name, and release

Check your setup

Checkpoint 1

Use BullMQ's job ID as the logical ID and record attemptsMade separately.

Checkpoint 2

Derive queue wait from the original enqueue time rather than the retry time.

Checkpoint 3

Never log job.data wholesale because it often contains customer payloads.

Verification

Prove the event arrived

Run this after exercising known success and failure cases. Replace the fallback table name if your final event contract differs from the snippet.

bullmq-verification

BullMQ queue monitoring verification query

sql

SELECT *
FROM job_completed
ORDER BY timestamp_utc DESC
LIMIT 20;

Confirm one terminal row per logical outcome, with the expected status, identifiers, units, and UTC time.

Inspect the inferred schema and verify that retries do not change field types or generate a new logical event ID.

Search the stored fields for credentials, raw payloads, prompts, private content, and unbounded error messages.

Exercise a provider timeout, ingestion rejection, and process shutdown before treating the dashboard as complete.

Implementation references

Review the event contract, data-safety guidance, and upstream primary documentation before enabling a new production path.

Queue worker guide Dead-letter growth SQL BullMQ events

Where to log

Keep the outcome event small and recoverable

This pattern provides

Record the outcome as an event you can query with SQL.
Stable fields for dashboards, alerts, and cross-event correlation.
Test events for checking success, failure, retries, and timeouts.

This pattern does not provide

An OTLP exporter, automatic collection pipeline, or replacement for detailed traces and diagnostic logs.
Exactly-once delivery merely because the payload contains an event ID.
Permission to collect raw provider payloads, user content, credentials, or regulated data.

Delivery and idempotency Batching and shutdown Troubleshoot ingestion

Example event schemas

Check what each event records, when to send it, and which field types it needs. Review the example payload and privacy checklist before using it in production.

Async reliability11 fields