Hi, I'd like to be able to have more control over purple alerts. I know Henrik has added a new parm into xymonserver.cfg called STATUSLIFETIME but that seems to be a global parm.
What I'd really like to do is reduce the purple time for devmon to 5 minutes less than the global. This would enable me to detect devmon going purple and trigger the restart script without having all the snmp monitored devices (we have about 10) going purple as well.
I hope someone can help on this,
Neil Simmonds Operations Analyst Operations Support Group Express Gifts Ltd. neil.simmonds at express-gifts.co.uk
Tel :- 01254 303092 Fax :- 01254 303100
Name & Registered Office: EXPRESS GIFTS LIMITED, 2 GREGORY ST, HYDE, CHESHIRE, ENGLAND, SK14 4TH, Company No. 00718151. Express Gifts Limited is authorised and regulated by the Financial Services Authority
NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Findel PLC and the recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Findel PLC. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Findel Plc reserves the right to monitor all e-mail communications through its internal and external networks. If you have received this email in error please notify our IT helpdesk on +44(0) 1254 303030
Hi all,
I am currently running 4.3.0 and just starting a project to upgrade. I know the newer releases include major changes and require some specific upgrade processing. Do I need to upgrade to a specific version before going all the way to 4.3.6 (or 4.3.7 when released?), or can I upgrade from 4.3.0 directly to 4.3.6?
Thanks,
Bruce
Bruce White Senior Enterprise Systems Engineer | Phone: 1-630-671-5169 | Fax: 630-893-1648 | bewhite at fellowes.com | http://www.fellowes.com/ Disclaimer: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Fellowes, Inc.
On Fri, 9 Dec 2011 11:37:01 -0600, "White, Bruce" <bewhite at fellowes.com> wrote:
I am currently running 4.3.0 and just starting a project to upgrade. I know the newer releases include major changes and require some specific upgrade processing. Do I need to upgrade to a specific version before going all the way to 4.3.6 (or 4.3.7 when released?), or can I upgrade from 4.3.0 directly to 4.3.6?
If you are running the release version of 4.3.0 (not the early beta-versions), then you can upgrade directly to 4.3.6 or 4.3.7 without any problems. It is only if you are running 4.3.0-beta2 or earlier that you will have to do some work (mostly because of all the renaming of files from hobbit to xymon).
Regards, Henrik
Is there anything we need to do to avoid losing graph data? I saw an earlier poster warning about this.
We're running 4.3.2 and planning to jump to 4.3.7 , server is RHEL linux
thanks Betsy
It depends on your version of the os. I went from 32bit RHEL4 to 64bit RHEL5. So I had to" rrdtool dump" all the graphs and restore them on the 64-bit system. If you are going from 32bit - 32bit or 64 to 64, you should be fine.
-----Original Message----- From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Elizabeth Schwartz Sent: Wednesday, December 21, 2011 3:03 PM To: Xymon Mailing List Subject: Re: [Xymon] Upgrade path?
Is there anything we need to do to avoid losing graph data? I saw an earlier poster warning about this.
We're running 4.3.2 and planning to jump to 4.3.7 , server is RHEL linux
thanks Betsy
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
And once again my reply didn't go to the list...
On Fri, Dec 9, 2011 at 6:22 AM, Neil Simmonds < Neil.Simmonds at express-gifts.co.uk> wrote:
Hi, I’d like to be able to have more control over purple alerts. I know Henrik has added a new parm into xymonserver.cfg called STATUSLIFETIME but that seems to be a global parm.****
What I’d really like to do is reduce the purple time for devmon to 5 minutes less than the global. This would enable me to detect devmon going purple and trigger the restart script without having all the snmp monitored devices (we have about 10) going purple as well.****
**
Dunno about devmon specifically, but in general a test script "does stuff" to discover the state of the target device/service, then constructs a message that looks something like:
"status $MACHINE.$TEST $COLOR `date`
yadda yadda yadda
other informational bits, etc, and so on"then sends that message to the xymon server. The default lifetime of a status message is 30 minutes, which you can change by appending a time to the word "status".
"status+15 thing,domain,co,uk.test green `date`"to get a 15 minute lifetime. You ought to be able to locate that part in devmon and make an appropriate adjustment. Or maybe there's already something in devmon for setting the message lifetime, but I don't use it so I don't know.
This is described in the "XYMON MESSAGE SYNTAX" section in the xymon.1 man page.
Ralph Mitchell
I created a script that I call a heartbeat check. It is based on this query:
$serverDate = $XYMON localhost "clientlog $server section=date";
Just check the date of the last message from the client and alert as appropriate. I use this query to get my configured hosts:
my $XYMONHOSTGREP = "$XYMONHOME/bin/xymongrep hb"; # retrieve all hosts with the 'hb'tag in hosts.cfg
And I use this config file for exceptions:
default hb time is 600 seconds or 10 minutes
configure exceptions here
#server|max heartbeat time (seconds) somehost29|900 somehost30|900
I do not know if I could share the script without consulting the corporate policy since they effectively paid and own my work.
~David
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Ralph Mitchell Sent: Friday, December 09, 2011 13:18 To: Xymon Mailing List Subject: Re: [Xymon] Purple alerts
And once again my reply didn't go to the list...
On Fri, Dec 9, 2011 at 6:22 AM, Neil Simmonds <Neil.Simmonds at express-gifts.co.uk> wrote: Hi, I'd like to be able to have more control over purple alerts. I know Henrik has added a new parm into xymonserver.cfg called STATUSLIFETIME but that seems to be a global parm. What I'd really like to do is reduce the purple time for devmon to 5 minutes less than the global. This would enable me to detect devmon going purple and trigger the restart script without having all the snmp monitored devices (we have about 10) going purple as well.
Dunno about devmon specifically, but in general a test script "does stuff" to discover the state of the target device/service, then constructs a message that looks something like:
"status $MACHINE.$TEST $COLOR date
yadda yadda yadda
other informational bits, etc, and so on"
then sends that message to the xymon server. The default lifetime of a status message is 30 minutes, which you can change by appending a time to the word "status".
"status+15 thing,domain,co,uk.test green date"
to get a 15 minute lifetime. You ought to be able to locate that part in devmon and make an appropriate adjustment. Or maybe there's already something in devmon for setting the message lifetime, but I don't use it so I don't know.
This is described in the "XYMON MESSAGE SYNTAX" section in the xymon.1 man page.
Ralph Mitchell
participants (7)
-
betsy.schwartz＠gmail.com
-
bewhite＠fellowes.com
-
david.gore＠verizon.com
-
henrik＠hswn.dk
-
Neil.Simmonds＠express-gifts.co.uk
-
ralphmitchell＠gmail.com
-
Tom.Moore＠sas.com