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. On Premises
  2. AWS

Monitors

PreviousSetup route 53NextUpgrading

Last updated 2 years ago

Was this helpful?

The On Premises instance runs a small Redis instance (128Mb) that is required for running the Monitors in Taskforce's alert system.

You can add a local connection for checking that the monitor system is working as it should, like this:

You will get a new connection that shows the monitor (and other queues as the monitors do their thing):

The Redis instance is isolated from the outside and only possible to be accessed from the EC2 host itself, so TLS, nor password authentication is necessary.