Built in escalation process would be cool Example: - if server down do normal notifications (email dispatch or whatever) - If server down x number of checks/minutes/hours/days/whatever send email/page to mangement/senior tech(s)
--------- Scot Gabriel (417) 208-9133 <google voice account> On Dec 6, 2009, at 1:35 PM, "Dirk Bulinckx" <d...@woodstone.nu> wrote: > One of those question we often get is "what will change to SA in the > (near) > future", well here we go, our roadmap :-) > > > * Windows 2008 compatibility > * checking engine and GUI separated > * webinterface (<- have a look at the current beta and you'll see > that > we already have saWeb built-in now :-)) > * db backend (instead of flat-file) > * boolean check (makes it possible to make a boolean combination of > already executed checks) > > When will all of that be done....?? Good question! Don't know :-) > I *hope* we can get all of this into the next major release, and no > I don't have > a date for that :-)) > > > Now how can YOU help us? Tell us what you think is missing from > Servers Alive. > Try not only to focus on the "look" of it, but also think about > CHECK - ALERTS - > OUTPUTS - ... that are "missing" (or better that would be nice to > have too) > > > > > Dirk. > > To unsubscribe send a message with UNSUBSCRIBE in the subject line > to salive@woodstone.nu > If you use auto-responders (like out-of-the-office messages), make > sure that they are not sent to the list nor to individual members. > Doing so will cause you to be automatically removed from the list. > To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list.
