Observability
Durabull vs Sentry
Sentry groups reported worker exceptions and connects producer and consumer spans for queue performance analysis. Its Node.js guide documents manual queue.publish and queue.process spans with trace propagation. BullMQ records processor errors as failed jobs, so outside framework integrations you may need to capture those errors explicitly to create Sentry issues.
Choose Sentry when you want stack traces grouped into issues and alerts for missed cron check-ins.
Choose Durabull when you want to inspect the job that threw, retry it, and let an agent do the same. Use both: Sentry for the exception, Durabull for the queue.
Capabilities
The details that change the decision
| Feature | Durabull | Sentry |
|---|---|---|
| Errors | Per-job failedReason and stack traces | Issue grouping, alerts, and triage |
| Retry jobs | Yes | Not documented |
| MCP | Queue inspection and opt-in queue operations | Sentry issues and performance; no BullMQ job tools |
Setup
How Sentry connects
The Sentry SDK runs in your Node.js workers. Cron check-ins cover scheduled jobs.
Application changes. Yes: SDK initialization, plus optional queue spans and cron check-ins.
- Queue discovery
- Queue destinations appear from spans, not from scanning Redis.
- Environments
- Sentry projects and environments.
- Alerts
- Issue and performance alerts, plus cron monitors for scheduled work. Configure error capture and check-ins in the relevant processes.
- AI & MCP
- Sentry’s hosted MCP server (
https://mcp.sentry.dev/mcp, OAuth) supports issue, performance, and project workflows. It does not retry or promote BullMQ jobs in Redis.
Economics
Understand what you are paying for
- Sentry pricing
- Team is $26/month billed annually ($29 monthly); Business is $80/month ($89 monthly). Paid plans include quotas such as 50k errors, 5M spans, and one cron monitor; additional cron monitors are $0.78 each.
- Sentry license
- Commercial SaaS. Self-hosted Sentry is FSL-1.1-Apache-2.0; the JavaScript SDKs are MIT.
- 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 Sentry and Durabull
Does Sentry auto-instrument BullMQ?
Not in general. Sentry’s Node.js queue guide documents manual producer and consumer spans. The NestJS SDK (10.44.0 and later) automatically wraps @nestjs/bullmq processors to create queue.process transactions and capture exceptions. Error capture, queue spans, and direct job operations are separate capabilities.
Evidence
Sources & methodology
- Node.js queue instrumentation
- Queues dashboard
- NestJS BullMQ instrumentation (10.44.0)
- Sentry pricing
- Sentry MCP server
Durabull details: product documentation, pricing, and MCP reference. Found a change? Send a correction.
Continue your research
- Durabull vsDatadogRedis metrics plus first-party BullMQ tracing and Data Streams Monitoring. Pair with a queue console to inspect and retry jobs.
- Durabull vsGrafana + PrometheusFlexible dashboards and alerts from exported BullMQ metrics. Pair with a queue console for payload inspection and recovery.
- Durabull vsBull BoardMIT dashboard with embedded adapters and a standalone Redis-discovery CLI.
Connect Redis. Queues appear.
Inspect your Redis-backed BullMQ queues in one place. Hosted Durabull is free to start.