AppSignal automatically provides a dashboard for queue length, a good indicator of Sidekiq health. Need alerts? Set triggers and get alerts when your queues are too long.
Know if your Sidekiq jobs succeed or fail. AppSignal visualizes failed, retried, dead and successful jobs.
Inspect the throughput and duration per worker to see if any worker is performing badly. This helps you scale your Sidekiq cluster.
Track the memory used by Redis and find out if there are any memory leaks in Sidekiq.
1500+ development teams rely on AppSignal to ship code with confidence. We are sharing a few of their stories with you.
# Add to .gemfile source "https://rubygems.org" gem "appsignal" # Ruby on Rails installation bundle exec appsignal install YOUR_PUSH_API_KEY
Want to learn more? Check out our Sidekiq docs.
AppSignal offers a 30-day free trial, no credit card is required. All features are available in all plans. Start monitoring your application in just a few clicks!
We've made a checklist to help you get started with Sidekiq monitoring and performance, including links to further resources. We recommend you follow these four steps:
Let's start with what to measure and how to set alerts.
Start with monitoring queue length. If your queues get too long, Sidekiq might not be able to catch up. Set alerts for maximum lengths so that you can scale up in time. Set up alerts and triggers for Sidekiq queue lengths
The next metric to track is job_status per queue. Tracking your job_status is important, as it indicates if your jobs are being processed successfully. Set alerts for failed job percentages and you'll know when something is wrong with your system.
If you've had Sidekiq running for a while, you will know the usual variance in duration per job. Monitor duration per job and set an alert when it goes over a certain threshold, so you're warned before the bits hit the fan.
In every AppSignal graph, you can go to 'what happened here' and look at the performance page (or errors, or host metrics) for that point in time. Here you can dive into a detailed event timeline to see why the job is taking so long.
Sometimes a problem surfaces in part of your stack (like Sidekiq), but originates somewhere else. A host that gets a surge in I/O from another app might cause performance issues in your Sidekiq background processes.
Read some helpful resources below:
You can also read our Sidekiq installation documentation
Do you need help, have a feature request or just need someone to rubber duck with? Get in touch with one of our engineers.