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
  2. Enable notifications

Pagerduty

PreviousSlackNextConnection monitor

Last updated 3 months ago

Was this helpful?

The notifications sytem also support sending alerts to Pagerduty. When an alert is triggered, Taskforce.sh will make a call to Pagerduty's events API, and the alert will be available in your Pagerduty dashboard, and normally all the members of a given team will get an alert email.

The alerts produced by the monitoring system will also be kept in Taskforce.sh alerts tab, so in order to acknowledge them you need to manually acknowlege them, or no new alerts will be produced during the next 24 hours for a give monitor in a given queue.

Pagerduty configuration