Taskforce.sh
  • Documentation
  • Getting started
    • Direct Redis Connection
    • Taskforce connector
  • Account
    • Settings
  • Connections
    • Queues
    • Jobs
    • Workers
  • Metrics
  • Monitoring
    • Enable notifications
      • Slack
      • Pagerduty
    • Connection monitor
    • Failed jobs monitor
    • Missing workers monitor
    • Max Memory monitor
    • Backlog Monitor
  • Alerts
  • Organizations
  • BullMQ Pro
    • Connector Pro
  • On Premises
    • AWS
      • Launch AWS AMI.
      • Create role with SSM permissions
      • Assign SSM Role
      • Configure your instance
        • Create a PostgreSQL instance
        • Configure Auth0
          • Configure API
        • Configure Mailgun
      • Setup loadbalancer
      • Setup route 53
      • Monitors
      • Upgrading
      • Troubleshooting
    • Docker
      • Docker registry
      • Environment variables
      • Docker compose
    • Using the taskforce connector
  • Security primer
  • Troubleshooting
Powered by GitBook
On this page

Was this helpful?

  1. Monitoring

Failed jobs monitor

PreviousConnection monitorNextMissing workers monitor

Last updated 5 months ago

Was this helpful?

This monitor checks if there are new jobs that have failed. The monitor will trigger an alert as soon as it detects that there is a job at the top of the failed jobs that have not triggered an alarm before.

For this monitor to work properly you need to keep at least 1 failed job in your queues with the removeOnFailed option set to false, which is the default, or to a number equal or larger than 1.

Since it is not uncommon that when one job fails several others fail too, the monitor will not trigger new alerts until the existing triggered alert is acknowledged.

The alerts are triggered per queue, so you can have many alerts in the "triggered" status belonging to different queues.