Resque Dashboard

All Memetria K/V databases and Memetria Monitoring for Redis™* include a free Resque dashboard, which allows you to manage your workers and queues without running, securing, and managing a Resque dashboard on your own.

For most users, our Resque dashboard should just work. In some cases, however, extra configuration may be required, which we’ve outlined below.

Resque Scheduler

The “Schedule” and “Delayed” tabs in the Resque dashboard give you access to your Resque Scheduler jobs with no extra configuration. However, if you want to use the “Queue now” button to manually queue jobs, you’ll need to tell our Resque dashboard which queue it should add each job to1.

In your Resque Scheduler configuration YAML file, all you need to do is specify the queue that each job should be placed in using the queue key:

MyPeriodicJob:
  queue: low
  cron: "*/10 * * * *"

“Cannot Connect to Redis”

If you see this error message in the Resque dashboard, it means that the Resque dashboard was unable to establish a connection to your Redis server. This can happen for a number of reasons:

  1. The most common cause is a mis-configured Memetria Monitor. Make sure that your Redis URL is correct. This includes the hostname, port, and password for your Redis server.
  2. You may also have firewall rules preventing the Resque dashboard from accessing your Redis database. The Resque dashboard is currently hosted on multiple servers in the AWS us-east-1 region. Multiple region support is in the works, but is not currently available.
  3. Still stuck? Send us an email at support@memetria.com and we’ll help you out.

  1. In normal Resque dashboard installations, the Resque dashboard has access to your application code and can use the @queue value from your job’s code. In our case, however, we don’t have access to your application’s code, so you have to configure it manually. ↩

← Back to docs