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

Connection monitor

PreviousPagerdutyNextFailed jobs monitor

Last updated 6 months ago

Was this helpful?

The connection monitor checks that the access to your Redis instance works properly. If for some reason the Redis host is not reachable, either because the instance is down or there is a connectivity error between Redis and the Taskforce.sh servers, then an alert will be triggered.

This is the most critical monitor since it implies that the Redis server may be down and an action to bring it back online may be needed.

When a connection alert is in "Triggered" status, no more alerts will be triggered until the alert is acknowledged or a full day has passed. Furthermore, if the connection is not reachable, none of the other monitors will work either so it is really important to make sure the connection is back online as soon as this alert is triggered.