3. It's probably more usefull if you can set that as executive alert, instead as individual (per entry) alert.
4. I see...I'll have to see how that would work..... Dirk Bulinckx. From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, May 20, 2008 6:46 PM To: Servers Alive Discussion List Subject: RE: [SA-list] SA possible enhancements 1 - Excellent 2 - understand that - already include the checkresponse on the screen. However, what the Service Desk see is a big chunk of red text (they don't read the small print...). Perhaps a clever bit of HTML coding could exclude timeouts, but that would be beyond me... 3 - That gives me another idea. I wonder if it would be useful to have an alerts section under Setup that is linked to SA as a whole (i.e. a batch of alerts/actions that is worked through whenever SA finishes a check cycle or at a specific time) rather than being specific to an individual check. Do you see what I mean? 4 - I think we're talking at cross purposes. What I'm talking about is the individual days on the calendar component on the "On Call" tab for each person. Each date on that calendar component is deselected by default (in other words, you have to select when they're on call, rather than selecting when they're *not* on call. If that could be reversed, that would be of much more use for us. Our typical scenario to use this is when someone goes on holiday - it would be much easier to set someone to be "off" for 28 days a year than to set them "on" for 337 days a year! Cheers, Ian _________________________________ Ian K Gray OEL IS - European Infrastructure Support Tel: +44 1236 502661 Mob: +44 7881 518854 Ad eundum quo nemo ante iit "Dirk" <[EMAIL PROTECTED]> Sent by: Servers Alive Discussion List <[email protected]> 20/05/2008 17:20 Please respond to Servers Alive Discussion List <[email protected]> To Servers Alive Discussion List <[email protected]> cc Subject RE: [SA-list] SA possible enhancements 1) Predefined alerts: looks like something usefull (I'll add that to our to-look-at list) 2) Failed check "down": well a DOWN is the status you get when SA can't say for sure that it's UP. If you want to know the reason of the down, then use the checkresponse (this can be viewed in the interface, used in the alerts and used within the HTML output) 3) XML output: correct this can't be done each cycle, what I can see as a possible option is to add that to the alerts - Execute Command - Internal Servers Alive command (something for the TODO list) 4) On Call: if the On-Call would be enabled by default, then sending the alert to that person would not work, as "just" enabling isn't enough you would alsoneed to set the dates when that person is on-call. Dirk Bulinckx. From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, May 20, 2008 6:06 PM To: Servers Alive Discussion List Subject: [SA-list] SA possible enhancements Hi Dirk (et al for info), We had an internal service review today on our monitoring services (of which SA forms the backbone). A number of things came up as a result of that, which I would like to pass on as enhancement requests: * We need to do some significant restructuring of alerts, and to do this check by check is going to be a huge piece of work. What would be really great would be to have a number of predefined alerts (e.g. Alert A is an alert set up to send SMS to engineer team X immediately; Alert B does the same but to engineer team Y; Alert C is set up to send an email to management group Z after 3 downs, etc). My idea is that you would then, in each check, be able to say "use predefined alerts A, B and D", as well as being able to create additional alerts for that specific check. I could imagine this being done with tick boxes - i.e. have (say) 10 predefined alert types which you can select within a check. The point of all this is that, if I need to make changes such as changing who gets the alerts, or what the wording of the alerts are, or when they get sent, or even add a new alert to a number of checks, one can simply change a single predefined alert, and/or tick an additional box in each check that is to be affected. Do you follow me? * I can adjust when an alert is sent (e.g. after x downs), and I can adjust how often a check is done (e.g. every x cycles). However, what I can't do is determine when a failed check should be considered a "down". Example: as mentioned in the past, we have a COM check that looks at an SQL db on a server, which quite often fails with a timeout. I have adjusted the alert to only go out after 2 downs (and in fact not to go out at all if the response includes "Timeout", but that doesn't stop that check from going red on our screens. (To be absolutely accurate, therefore, the issue is when a failed check should be presented as a "down" on the on the HTML outputs, but that's probably getting too complicated...) * XML output (that favourite topic of the discussion group) - I can manually export to XML, but I can't (I don't think) have SA do that automatically every check cycle. Hey - I don't understand XML at all, but my colleagues tell me that they can do something clever with it... * I think I've asked this before, but I'll double check... The on-call schedule for people defaults to "Not on call". Would it be possible (as standard or as an option) to change this to defaulting to "On call"? Thoughts? Many thanks as ever, Ian _________________________________ Ian K Gray OEL IS - European Infrastructure Support Tel: +44 1236 502661 Mob: +44 7881 518854 Ad eundum quo nemo ante iit ______________________________________________________________________________ Any opinions expressed in this email are those of the individual and not necessarily of the Company. This email and any files transmitted with it, including replies and forwarded copies (which may contain alterations) subsequently transmitted from the Company are confidential and solely for the use of the intended recipient. It may contain material protected by legal privilege. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this email in error and that any use is strictly prohibited. Please notify the sender immediately of the error and delete any copies of this message Warning: Although the Company has taken reasonable precautions to ensure that no viruses are present in this e-mail, the Company cannot accept responsibility for any loss or damage arising from the use of this e-mail or attachments. To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] 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 [email protected] 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. ______________________________________________________________________________ Any opinions expressed in this email are those of the individual and not necessarily of the Company. This email and any files transmitted with it, including replies and forwarded copies (which may contain alterations) subsequently transmitted from the Company are confidential and solely for the use of the intended recipient. It may contain material protected by legal privilege. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this email in error and that any use is strictly prohibited. Please notify the sender immediately of the error and delete any copies of this message Warning: Although the Company has taken reasonable precautions to ensure that no viruses are present in this e-mail, the Company cannot accept responsibility for any loss or damage arising from the use of this e-mail or attachments. To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] 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 [email protected] 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.
