Sidekiq is a popular library for background job processing in Ruby on Rails applications. It uses Redis as a backend to store and manage the job queue, providing efficient and scalable processing. Sidekiq allows developers to define asynchronous tasks that will be executed in the background, freeing the main thread to handle other requests. It supports advanced features such as job scheduling, prioritized queuing, and failure retention, ensuring reliability and error recovery. With its simple and easy-to-use interface, Sidekiq has become a popular choice for handling time-consuming tasks or tasks that do not require an immediate response, thereby improving the user experience.
How to monitor Sidekiq on One Platform
1 – In the side menu, click on Services Hub
2 – In the Queue category, click on the Sidekiq card
3 – You will be directed to the Sidekiq configuration form, fill in the fields
4 – If you want, you can configure automatic incident opening. In the Open automatic incident section, fill in the fields:
- Severity -> Choose between “SEV-1 – Critical”, “SEV-2 – High”, “SEV-3 – Moderate”, “SEV-4 – Low”, “SEV-5 – Informational” or “Not Classified”;
- Check Interval in seconds -> This is the interval at which checking will take place (this interval cannot be less than the number of failures x the Interval configured in the monitoring form;
- Failures to open automatic incident -> It is the number of failures necessary to open the automatic incident;
- Check Interval in seconds -> This is the interval in which checking will take place (this interval cannot be less than the number of hits x the Interval configured in the monitoring form;
- Hits to close automatic incident -> It is the number of hits needed to close the automatic incident;
- Responders -> These are the teams that will be notified if there are incidents in this monitoring, and you can add one or multiple teams;
If necessary, you can create a team by clicking + RESPONDER, you will be directed to the form
to create the team, then click on the button 
for the new team to appear in the list
***Don’t forget to activate the Enable to set up automatic incidents opening toggle to save the automatic incident opening settings
5 – Click on CREATE MONITORING
