Any thoughts to having a simple Icon on each and every page that simply shows if there are alarms or not, a sort of Red or green button as an alert to the admin. It could be multi-button, with a red and green for each - minor, major, critical alarms. This could provide a consistent method of advertising the alarms, and a consistent place to find them on each page. A click on the icon could then open the page that has the filtered alarms on that page.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Damian Krzeminski Sent: Monday, July 06, 2009 7:21 AM To: [email protected] Subject: Re: [sipX-dev] (XX-6051) sipXsupervisor to alert admin whensystem services can not start Carolyn Beeton wrote: >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of >> Krzeminski, Damian (BL60:9D30) >> Sent: Monday, July 06, 2009 4:51 AM >> To: [email protected] >> Subject: Re: [sipX-dev] (XX-6051) sipXsupervisor to alert >> admin whensystem services can not start >> >> Carolyn Beeton wrote: >>>> -----Original Message----- >>>> http://track.sipfoundry.org/browse/XX-6051 >>> This is asking for two quite separate things: >>> >>> 1) visual indication of non-running service. >>> This would be a config server feature: any Enabled >> service which >>> is not in Running should cause a message to be displayed on >> each page >>> with a link to the Services page. After restarting a service, the >>> config server would have to follow its status until it >> reaches Running >>> or a failure state. >>> >>> 2) alarm on any service which does not get to Running. >>> This is a supervisor feature: raise alarm on entry to states >>> ConfigurationMismatch, ResourceRequired, and ConfigTestFailed. >>> >>> I think two JIRAs are warranted, assuming that we have agreement on >>> both these requirements. >>> >> I agree: it should be split in 2 issues... >> But to make it useful (and less annoying) sipXconfig should >> allow admin to acknowledge alarms. Otherwise we will drive >> admins mad with constant nagging. >> I created an issue for the 'display' part: >> http://track.sipfoundry.org/browse/XX-6069 >> Feel free to add comments or change something. >> D. >> > > Hmmm... I wasn't thinking of generic sipXconfig alerts for alarms > (though I originally envisioned an alarm counter thingy (I think the > technical term is histogram :-) on each sipXconfig page: I think I at > least sketched in queries for alarm counters with TODOs to make them > return a count for each severity level). Nice touch with nested parenthesis! I always thought (being a somewhat self-centered geek (not that geeky I hope)) that I am the only person who does it in e-mails. > > In this context, it was more specific: Mark wants to know that a service > has not started (not that an alarm was raised). > I see: looks like I've read to much in it. I do not mind simplifying this to implement yet another specific warning. We already have 3 or 4. I hoped if we implemented a generic 'alarm raised' panel we can simplify code a bit but it can certainly wait. D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
