My understanding about the Beep Manager service was that it only applied to the alerts from Pingdom itself. If it's something we can use with Nagios, that might be worth looking into since we already use them for critical checks.
-- ~*~ StormeRider ~*~ "Every world needs its heroes [...] They inspire us to be better than we are. And they protect from the darkness that's just around the corner." (from Smallville Season 6x1: "Zod") On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS On Mon, Aug 25, 2014 at 9:48 AM, Nathan Hruby <[email protected]> wrote: > PagerDuty is well worth the investment. > > The time saved by not having to maintain alerting infrastructure and > being able to quickly and easily manage oncall and alerting with > multiple contact methods more than covers the cost of PD. I've done > this at multiple sites, including managing the script you refer to at > /. -- it really isn't worth it anymore. > > With geographically dispersed teams, it's even nicer since > follow-the-sun rotations and easy overrides / maintence windows help > prevent on-call spam outside of business hours from a single point > instead of all the alert sources. > > I'm also a fan of the iCal feed for your on-call rotation. Not only > is it handy for planning oncall duties around vacations, but in cases > where you're going to cover oncall for a few hours for someone, the > schedule override pops into your calendar as well so you're not > surprised when you get paged. > > Pingdom recently launched a PagerDuty competitor as well called Beep > Manager Pro, and I believe several other Monitorig-As-A-Service > platforms have similar features that you may want to look at. > > -n > > On Mon, Aug 25, 2014 at 6:09 AM, Nathan Clemons <[email protected]> > wrote: > > We're looking to set up small teams in nagios and rotate between primary > and secondary contacts, vs having one global on call person. (Ie, two > networking folks, two vmware folks, two Unix folks, etc.) What kind of > solutions have folks tried for this? Pagerduty seems excessively priced for > this kind of task, especially when we're trying to trim opex costs. When I > worked at /. we used sendmail aliases to control the paging and just ran a > script from cron to adjust the list to the next person in line on Monday > morning. > > > > Thanks. > > _______________________________________________ > > Discuss mailing list > > [email protected] > > https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss > > This list provided by the League of Professional System Administrators > > http://lopsa.org/ > > > > -- > ------------------------------------------- > nathan hruby <[email protected]> > metaphysically wrinkle-free > ------------------------------------------- >
_______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
