Skip to content

Observability

Durabull vs New Relic

New Relic’s Redis integration monitors the datastore, and its Node.js agent instruments the redis and ioredis clients. Its instrumented-modules list does not include bullmq, so worker jobs need custom background transactions. Durabull adds direct inspection and recovery of BullMQ jobs.

New Relic website ↗4 primary references
System map
Your applicationProducers & workers
enqueue / process
Redis + BullMQQueue state & job lifecycle
runtime
inspect / operate
DurabullDashboard · alerts · MCP
operations
Telemetry explains system health. Queue tools act on individual jobs.
The case for New Relic

Choose New Relic when you have already standardized on New Relic for APM and Redis monitoring.

The case for Durabull

Choose Durabull when you need BullMQ-aware views of queues and jobs, plus MCP tools that can retry or promote jobs and pause queues. Keep New Relic for traces if you instrument workers there.

Capabilities

The details that change the decision

Compare the documented deployment modes. “Not documented” means we did not find a vendor claim, not proof that a capability is impossible. Check the primary sources.
Durabull versus New Relic feature comparison
FeatureDurabullNew Relic
BullMQ instrumentationReads BullMQ state from RedisNot in the instrumented-modules list
Retry jobsYesNot documented
MCPQueue inspection and opt-in queue operationsNew Relic telemetry; no BullMQ job tools

Setup

How New Relic connects

The infrastructure agent’s Redis integration collects INFO metrics and lengths of configured keys. The Node.js APM agent runs in your app and workers.

Application changes. Yes for APM: the agent in each worker or API process, plus custom background transactions around job handlers.

Queue discovery
No BullMQ queue discovery.
Environments
Separate environments by New Relic account, app name, or tags.
Alerts
Alert conditions on NRQL queries over collected telemetry. There is no job-level recovery workflow.
AI & MCP
New Relic’s MCP server (https://mcp.newrelic.com/mcp/ in the US; EU and JP endpoints are available) accesses New Relic telemetry and workflows. It does not document BullMQ job operations.

Economics

Understand what you are paying for

Different products, different cost boundaries. Durabull’s hosted app is free to start and covers its dashboard. Redis, worker compute, storage, networking, and operational work remain yours. A runtime’s usage charges may cover orchestration or compute. The prices here are not a total-cost or savings benchmark.
New Relic pricing
Includes 100 GB of data ingest per month, then $0.40/GB, or $0.60/GB with Data Plus. User-based and compute-based models are available. Pro full-platform users list at $349/user/month with an annual commitment; additional capabilities can add charges.
New Relic license
Commercial SaaS. The Node.js agent is Apache-2.0.
Durabull
Hosted dashboard is free to start. Redis, worker compute, and infrastructure operations remain your costs. Check the pricing page for current terms. Apache License 2.0 (OSI-approved open source). Self-host on your own infrastructure.

Questions about New Relic and Durabull

Does New Relic auto-instrument BullMQ?

New Relic’s Node.js compatibility table lists redis and ioredis but not bullmq. You can wrap job handlers in background transactions or add custom instrumentation. Check BullMQ support against the agent version you install.

Evidence

Sources & methodology

Reviewed against vendor documentation, public pricing, and source repositories. This is a documentation comparison, not a hands-on benchmark. Vendor docs may describe different editions or deployment modes; confirm those details before purchasing.

Durabull details: product documentation, pricing, and MCP reference. Found a change? Send a correction.

Continue your research

Connect Redis. Queues appear.

Inspect your Redis-backed BullMQ queues in one place. Hosted Durabull is free to start.