Kumishifts: The Release

One of my personal missions within Kumina is to decrease the amount of noise. We work fairly event-driven, responding to everything that gets reported. Although I believe our customers like this very much, it can be a bit of a bother in the case where someone is not on helpdesk duty. One of my pet peeves was the fact that Nagios sent SMS alerts to everyone, instead of the person who was on duty at the time.

Since we have multiple Nagios instances, it would be a bit of a hassle to change the config everywhere all the time, so we stuck with the current way. At least you can be sure that someone received the message. But since we get some false positives too, at time, it does add to the bill.

So I decided to create Kumishifts. This little Python script takes a Google Calendar (or any ical you point it at) and distills who’s on duty. It generated a Nagios contacts file based on that information (and then some). We can now actually work with escalations to make sure that if the first person responsible doesn’t respond fast enough (bad person!), a second one will get the message after a little while, too.

We’re not yet deploying the script everywhere, but will soon, after it’s properly tested. I’d appreciated any feedback on the app!

Tags: , , , , , , , ,


2 Responses to “Kumishifts: The Release”

  1. Rob says:

    This sounds like what I’ve been looking for. We use Google for our corporate email and calendar, and I’d love to be able to leverage an on-call schedule in Nagios.

    However…

    Your link is dead. Do you still have the script?

    Thanks!

  2. Tim Stoop says:

    Hi Rob,

    Nice to see someone is interested in it! Honestly, we’ve never brought it in production, so it was never developed further. It was moved to our new Trac instance, here. I’ll change the link in the article as well. I hope it still works, because I haven’t looked at it in ages…

Leave a Reply