Add sidekiq-monitoring to your application
- Identify a port you want to allocate to the sidekiq-monitoring instance for your application and reserve it in development-vm/Procfile.
Adding configuration for your application in sidekiq-monitoring repository
- Add a line to the Procfile with the port you reserved earlier in the sidekiq-monitoring repository maintaining the alphabetical order of the processes.
- Update index.html to include a link to your application’s sidekiq-monitoring maintaining the alphabetical order of the applications. This path is configured as a location under the sidekiq-monitoring vhost.
bundle exec foreman startand test that your Rack and Redis config work as expected.
Configuring a path under the sidekiq-monitoring vhost
The sidekiq-monitoring vhost in Nginx has one location for every sidekiq-monitoring application. Add one for your application in this puppet template.
Test that the configuration works on Integration
Once changes are merged and deployed to Integration, you can access your sidekiq monitoring instance running on Integration, and check that it works as expected.
More about Monitoring
- Add a deployment dashboard for an application
- Add an Icinga passive check to a Jenkins job
- Error reporting with Sentry
- GOV.UK and Virtual Private Networks (VPNs)
- Graphite and deployment dashboards
- How to deal with errors
- Monitor Sidekiq queues for your application
- Monitoring screens
- Nagios NRPE connection failures
- Pingdom Bouncer canary check
- Tools: Icinga, Grafana and Graphite, Kibana and Fabric
- Uptime Metrics
- Use AWS X-Ray to trace app requests
- Use Terraboard to monitor Terraform state