I understand that, I was just saying that the method of layout/description for
when the alerts would trigger could be expressed in a similar manner.
Clearly you don't need nearly as much granularity becasue of the structure of
how SA works.
Perhaps a stripped down version would be enough: Minute, Hour, Day of week
So I could say that I want alerts "* * Mon-Fri" ==> all day, monday through
friday or "00-25 8-17 *" would be from 8:00am to 8:25, 9:00am to 9:25, ...
5:00pm to 5:25 for every day of the week.
Even "00-15 00,12 Sun" would be from midnite to 12:15am and noon to 12:15pm on
Sundays only.
Since this is XML output, It might make sense for readability though to have
these as 3 seperate elements under each alert rather than a property of the
alert element.
<myalert schedule="00-15 00,12 Sun">
</myalert>
versus
<myalert>
<scheduleminutes>00-15</scheduleminutes>
<schedulehours>00,12</schedulehours>
<scheduledays>Sun</scheduledays></myalert>
Michael D. Shook
Systems Analyst - Data Integration
Saddle Creek Corporation
[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])
863 668 4477 (work)
863 665 1261 (fax)
www.saddlecrk.com (http://www.saddlecrk.com/)
--------------------------------------------------------------------------------
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk
Bulinckx
Sent: Monday, February 05, 2007 10:01 AM
To: Servers Alive Discussion List
Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse
looking at it, it does not seem to be the type of schedule we're using.
With the CRON schedule you can say that it has to run on a specific
day/hour/minute, while what we do is run "all the time" except...
Dirk Bulinckx.
--------------------------------------------------------------------------------
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of
Michael Shook
Sent: Monday, February 05, 2007 2:41 PM
To: Servers Alive Discussion List
Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse
Here's a good help file for vixie cron (ignore the bits that deal with their
specific example about the variables).
It covers the method/layout pretty well (at least as well as I understand it
:-) ) and should cover all the uses you'd need.
http://www.unixgeeks.org/security/newbie/unix/cron-1.html
(http://www.unixgeeks.org/security/newbie/unix/cron-1.html)
Michael D. Shook
Systems Analyst - Data Integration
Saddle Creek Corporation
[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])
863 668 4477 (work)
863 665 1261 (fax)
www.saddlecrk.com (http://www.saddlecrk.com/)
--------------------------------------------------------------------------------
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk
Bulinckx
Sent: Monday, February 05, 2007 8:26 AM
To: Servers Alive Discussion List
Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse
No I'm not aware of that format.
Can you give some examples/tips/hints/...?
Dirk Bulinckx.
--------------------------------------------------------------------------------
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of
Michael Shook
Sent: Monday, February 05, 2007 2:11 PM
To: Servers Alive Discussion List
Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse
Are you familiar with how cron jobs schedule on a *nix server? That's probably
the most concise 'readable' schedule description. Plus, it's only a single
element per each alert. We use that format in other production software, so it
would work well for us.
Michael D. Shook
Systems Analyst - Data Integration
Saddle Creek Corporation
[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])
863 668 4477 (work)
863 665 1261 (fax)
www.saddlecrk.com (http://www.saddlecrk.com/)
--------------------------------------------------------------------------------
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk
Bulinckx
Sent: Sunday, February 04, 2007 1:56 PM
To: Servers Alive Discussion List
Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse
About the schedule (as that seems to be one of the things you "need"), how do
you see that within an XML file?
Dirk Bulinckx.
--------------------------------------------------------------------------------
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of
Michael Shook
Sent: Friday, February 02, 2007 10:11 PM
To: Servers Alive Discussion List
Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse
Thanks, this will really look good for the managers.
You rock!!!
Michael D. Shook
Systems Analyst - Data Integration
Saddle Creek Corporation
[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])
863 668 4477 (work)
863 665 1261 (fax)
www.saddlecrk.com (http://www.saddlecrk.com/)
--------------------------------------------------------------------------------
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk
Bulinckx
Sent: Friday, February 02, 2007 3:46 PM
To: Servers Alive Discussion List
Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse
For the export?
I hope even before that :-) (that is before v7)
Dirk Bulinckx.
--------------------------------------------------------------------------------
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of
Michael Shook
Sent: Friday, February 02, 2007 9:31 PM
To: Servers Alive Discussion List
Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse
YEAH!!!!!!!!!!!!!
ummmmm, do you have a version eta? Maybe, dare I say, (dare!, dare!) version 7?
Michael D. Shook
Systems Analyst - Data Integration
Saddle Creek Corporation
[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])
863 668 4477 (work)
863 665 1261 (fax)
www.saddlecrk.com (http://www.saddlecrk.com/)
--------------------------------------------------------------------------------
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk
Bulinckx
Sent: Friday, February 02, 2007 3:16 PM
To: Servers Alive Discussion List
Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse
XML as output/export is an option. As input it's not (yet).
Dirk Bulinckx.
--------------------------------------------------------------------------------
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of
Vogl, Tom
Sent: Friday, February 02, 2007 8:01 PM
To: Servers Alive Discussion List
Subject: RE: [SA-list] Feature request, was: Changing alert recipients en masse
Can I throw in my $.02 and ask for the config file to moved to an XML format -
which will make it easier to parse/edit with external tools....
-Tom
--------------------------------------------------------------------------------
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of
Michael Shook
Sent: Friday, February 02, 2007 7:56 AM
To: Servers Alive Discussion List
Subject: [SA-list] Feature request, was: Changing alert recipients en masse
Can I request a way to print out the alerts that each check have? Or better yet
export a .csv with the alert data?
I'd love:
SAID
UID
Alert
Recipients
Alert Conditions
Alert Schedule
I have been asked repeatedly for this information so the managers of the teams
can review it.
Please, Please?
Michael D. Shook
Systems Analyst - Data Integration
Saddle Creek Corporation
[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])
863 668 4477 (work)
863 665 1261 (fax)
www.saddlecrk.com (http://www.saddlecrk.com/)
--------------------------------------------------------------------------------
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk
Bulinckx
Sent: Friday, February 02, 2007 1:36 AM
To: Servers Alive Discussion List
Subject: RE: [SA-list] Changing alert recipients en masse
There is no option/feature to add alerts "en masse".
Dirk Bulinckx.
--------------------------------------------------------------------------------
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of
Wuichner, Eric
Sent: Thursday, February 01, 2007 11:06 PM
To: Servers Alive Discussion List
Subject: [SA-list] Changing alert recipients en masse
Thanks to all for the help. The tool is doing some good things for us.
I have about 450 devices doing ping checks only now every two minutes. What's
the best way to set the same alert recipient for multiple devices at the same
time? We want to make sure the right people get alerted for only the devices
they support.
Thanks again for your help,
Eric
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure
that they are not send to the list nor to the individual members of the list
that send a message. Doing this will get you removed from the list.
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure
that they are not send to the list nor to the individual members of the list
that send a message. Doing this will get you removed from the list.
--------------------------------------
The information contained in this message is intended only for the use of the
addressee. If the reader of this message is not the intended recipient or agent
of the intended recipient, you are hereby notified that any dissemination,
distribution, or copying of the message is strictly prohibited.
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure
that they are not send to the list nor to the individual members of the list
that send a message. Doing this will get you removed from the list.
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure
that they are not send to the list nor to the individual members of the list
that send a message. Doing this will get you removed from the list.
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure
that they are not send to the list nor to the individual members of the list
that send a message. Doing this will get you removed from the list.
--------------------------------------
The information contained in this message is intended only for the use of the
addressee. If the reader of this message is not the intended recipient or agent
of the intended recipient, you are hereby notified that any dissemination,
distribution, or copying of the message is strictly prohibited.
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure
that they are not send to the list nor to the individual members of the list
that send a message. Doing this will get you removed from the list.
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure
that they are not send to the list nor to the individual members of the list
that send a message. Doing this will get you removed from the list.
--------------------------------------
The information contained in this message is intended only for the use of the
addressee. If the reader of this message is not the intended recipient or agent
of the intended recipient, you are hereby notified that any dissemination,
distribution, or copying of the message is strictly prohibited.
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure
that they are not send to the list nor to the individual members of the list
that send a message. Doing this will get you removed from the list.
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure
that they are not send to the list nor to the individual members of the list
that send a message. Doing this will get you removed from the list.
--------------------------------------
The information contained in this message is intended only for the use of the
addressee. If the reader of this message is not the intended recipient or agent
of the intended recipient, you are hereby notified that any dissemination,
distribution, or copying of the message is strictly prohibited.
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure
that they are not send to the list nor to the individual members of the list
that send a message. Doing this will get you removed from the list.
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure
that they are not send to the list nor to the individual members of the list
that send a message. Doing this will get you removed from the list.
--------------------------------------
The information contained in this message is intended only for the use of the
addressee. If the reader of this message is not the intended recipient or agent
of the intended recipient, you are hereby notified that any dissemination,
distribution, or copying of the message is strictly prohibited.
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure
that they are not send to the list nor to the individual members of the list
that send a message. Doing this will get you removed from the list.
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure
that they are not send to the list nor to the individual members of the list
that send a message. Doing this will get you removed from the list.
--------------------------------------
The information contained in this message is intended only for the use of the
addressee. If the reader of this message is not the intended recipient or agent
of the intended recipient, you are hereby notified that any dissemination,
distribution, or copying of the message is strictly prohibited.
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure
that they are not send to the list nor to the individual members of the list
that send a message. Doing this will get you removed from the list.
