Hello all,
First of all I would like to say what a wonderful tool xymon is. I have been using it since hobbit and still am amazed at what you can do with it.
Currently I'm running xymon 4.3.12 on opensuse 12.3 and I've run into a snag. I have had a yellow disk warning, but as most know, time enough to clear out disk space. However meanwhile the disk space had increased at such a rate, that it was completely full. What's the problem? Well, it never came out of acknowledgment. If it turns from yellow to red, I would expect the ack to be removed. Did anybody encounter this issue before? Is what I expect not possible?
Kind regards
Jurgen
This e-mail and all files transmitted as attachment(s) thereto are confidential and solely intended for the individual to whom or the organization to which they are addressed. If you received this e-mail by mistake, please notify Cegeka's Service Desk at cegeka.support at cegeka.be or call +32 (0)11 240 363. We thank you in advance. Cegeka hereby confirms that this message has been swept by Sophos for the presence of viruses.
Den 2014-01-23 11:36, Claessens Jurgen skrev:
Currently I'm running xymon 4.3.12 on opensuse 12.3 and I've run into a snag.
I have had a yellow disk warning, but as most know, time enough to clear out disk space. However meanwhile the disk space had increased at such a rate, that it was completely full.
What's the problem? Well, it never came out of acknowledgment. If it turns from yellow to red, I would expect the ack to be removed.
Did anybody encounter this issue before? Is what I expect not possible?
This is "works as designed".
As far as Xymon is concerned, once an event has been ack'ed, then it won't care about it until it has returned to green or the ack expires. Ack'ing an event means "I know about it, and I'll fix it" - then it is the admin's responsibility to handle it. If it goes from yellow to red while he is doing that, is not something Xymon worries about.
This is because the primary purpose of an ack is to stop alerts from being triggered - you dont want to be pestered with alerts while you are working on an issue. Also, if you have e.g. a disk that is flipping between yellow and red, then you don't want to constantly re-ack the event just because the color changed.
You could argue that an ack should be associated with a severity - so an ack-on-yellow would not have effect when the status went red; then you would have to re-ack it. But both acks should remain in effect until the status goes green. But that is not how the system works right now.
Regards, Henrik
Hi Henrik,
Thank you for the swift response. You are right, when flipping between yellow-red this would be very annoying.
Thanks
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of henrik at hswn.dk Sent: donderdag 23 januari 2014 12:46 To: xymon at xymon.com Subject: Re: [Xymon] Acknowledge problem
Den 2014-01-23 11:36, Claessens Jurgen skrev: Currently I’m running xymon 4.3.12 on opensuse 12.3 and I’ve run into a snag. I have had a yellow disk warning, but as most know, time enough to clear out disk space. However meanwhile the disk space had increased at such a rate, that it was completely full. What’s the problem? Well, it never came out of acknowledgment. If it turns from yellow to red, I would expect the ack to be removed. Did anybody encounter this issue before? Is what I expect not possible?
This is "works as designed". As far as Xymon is concerned, once an event has been ack'ed, then it won't care about it until it has returned to green or the ack expires. Ack'ing an event means "I know about it, and I'll fix it" - then it is the admin's responsibility to handle it. If it goes from yellow to red while he is doing that, is not something Xymon worries about. This is because the primary purpose of an ack is to stop alerts from being triggered - you dont want to be pestered with alerts while you are working on an issue. Also, if you have e.g. a disk that is flipping between yellow and red, then you don't want to constantly re-ack the event just because the color changed. You could argue that an ack should be associated with a severity - so an ack-on-yellow would not have effect when the status went red; then you would have to re-ack it. But both acks should remain in effect until the status goes green. But that is not how the system works right now.
Regards, Henrik
This e-mail and all files transmitted as attachment(s) thereto are confidential and solely intended for the individual to whom or the organization to which they are addressed. If you received this e-mail by mistake, please notify Cegeka's Service Desk at cegeka.support at cegeka.be or call +32 (0)11 240 363. We thank you in advance. Cegeka hereby confirms that this message has been swept by Sophos for the presence of viruses.
This reminds me of a wish-list item…
When acking an alert for (example) C: drive, if after that point D: starts to fill up it will also be included within the ack. So, the wish list item is to treat each item under an alert (disk/process/service) as separate items.
I know, keep wishing… ☺
Thanks, John Upcoming PTO: (none)
John Rothlisberger IT Strategy, Infrastructure & Security - Technology Growth Platform TGP for Business Process Outsourcing Accenture 312.693.3136 office
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of henrik at hswn.dk Sent: Thursday, January 23, 2014 5:46 AM To: xymon at xymon.com Subject: Re: [Xymon] Acknowledge problem
Den 2014-01-23 11:36, Claessens Jurgen skrev: Currently I’m running xymon 4.3.12 on opensuse 12.3 and I’ve run into a snag. I have had a yellow disk warning, but as most know, time enough to clear out disk space. However meanwhile the disk space had increased at such a rate, that it was completely full. What’s the problem? Well, it never came out of acknowledgment. If it turns from yellow to red, I would expect the ack to be removed. Did anybody encounter this issue before? Is what I expect not possible?
This is "works as designed". As far as Xymon is concerned, once an event has been ack'ed, then it won't care about it until it has returned to green or the ack expires. Ack'ing an event means "I know about it, and I'll fix it" - then it is the admin's responsibility to handle it. If it goes from yellow to red while he is doing that, is not something Xymon worries about. This is because the primary purpose of an ack is to stop alerts from being triggered - you dont want to be pestered with alerts while you are working on an issue. Also, if you have e.g. a disk that is flipping between yellow and red, then you don't want to constantly re-ack the event just because the color changed. You could argue that an ack should be associated with a severity - so an ack-on-yellow would not have effect when the status went red; then you would have to re-ack it. But both acks should remain in effect until the status goes green. But that is not how the system works right now.
Regards, Henrik
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. .
www.accenture.com
participants (3)
-
henrik＠hswn.dk
-
john.r.rothlisberger＠accenture.com
-
Jurgen.Claessens＠cegeka.be