Lindsay Holmwood
Lindsay Holmwood
Dumb question: can you just shell out to `git rev-parse HEAD` to get the current git SHA?
At a very minimum, we need documentation on: - [ ] How to set up a production-like environment (on something like Linode or Digital Ocean) - [ ] How to...
@henare which queue are we talking about? I assume a Sidekiq one? If so, is it addressed by [the new graphs](http://morph-monitor.fractio.nl/dashboard/db/morph?from=now-2d&to=now)?
Is anyone going to respond to the alert? If not, don't set one up – it'll just be noise.
> _If so, is it addressed by the new graphs?_ For future readers, this is a screenshot of the Sidekiq graphs I'm talking about: 
Yep. Choose one way of being notified, and use that. If recovery is not time critical, then an email is an OK place for the alert to go and die.
> I think it would be most useful to have one chart for scheduled jobs so we can see if that's not draining properly. And one that shows retries (...
> I think the collectd-sidekiq-plugin needs some work so it displays stats from the retry queues properly. Per @equivalentideas's feedback, I've added support in [collectd-sidekiq-plugin](https://github.com/auxesis/collectd-sidekiq-plugin) to [collect retries, scheduled, dead,...
Here's the _retries, dead, scheduled_ graph with a log(10) scale on the _y_ axis:  This makes it a bit easier to see changes to retries at the same time...
> I recon it should span the whole way across to match the load chart above. @equivalentideas [how about this](http://morph-monitor.fractio.nl/dashboard/db/morph)? 