Bug or feature?
list Becker Christian
Hello everybody, i want to know if the following is a bug or a feature: I have a client (Ubuntu 9.10) running Xymon 4.3.7, reporting it's results to our Xymon server running Xymon 4.3.11. The client has a script in /opt/xymon/ext that is beeing kicked off once a working day in the week at 04:45 am. This is configured by a CRONDATE statement in clientlaunch.cfg. The script is reporting it's result to the Xymon server using a status lifetime of 1d (status +1d). The above is working. Now we had the situation, that this test has gone to status "red". The problem behind that wasn't a real problem, it was due to a bank holiday and not a real problem. Nevertheless I have disabled this particular test until 5 minutes beyond the next run-time of that test; it has been disabled until 4:50 am of the next day. When I checked this the next day at 08:30h, this test still was at "blue" (disabled) - I expected, that this should either be "green" or any other than "blue". When I clicked into that test I could see, that "inside" it showed the "new" test result as "green", but the test page was "blue". Hope my explanation of the situation is a bit understandeable..... Is the above a bug? Or did I do something wrong? Greetings Christian Christian Becker IT-Services user-e4a19bfb94c0@xymon.invalid<mailto:user-e4a19bfb94c0@xymon.invalid> Mittelrhein-Verlag GmbH August-Horch-Straße 28 D-56070 Koblenz Verleger und Geschäftsführer: Walterpeter Twer Reg.-Gericht Koblenz HRB 121 Finanzamt Koblenz Str.Nr. 22 65 10 285 2 www.rhein-zeitung.de<http://www.rhein-zeitung.de/>;
list Paul Root
If you set the test to disabled until a certain time, when the test runs, whether it has a green result or not, it will not clear out the disabled status. If you had disabled "until ok" then it would have cleared. Once a test is disabled for a set amount of time, it will not change to another state until 1) the time runs out AND 2) a new status comes in.
▸
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Becker Christian Sent: Friday, June 05, 2015 2:46 AM To: Xymon at xymon.com Subject: [Xymon] Bug or feature? Hello everybody, i want to know if the following is a bug or a feature: I have a client (Ubuntu 9.10) running Xymon 4.3.7, reporting it's results to our Xymon server running Xymon 4.3.11. The client has a script in /opt/xymon/ext that is beeing kicked off once a working day in the week at 04:45 am. This is configured by a CRONDATE statement in clientlaunch.cfg. The script is reporting it's result to the Xymon server using a status lifetime of 1d (status +1d). The above is working. Now we had the situation, that this test has gone to status "red". The problem behind that wasn't a real problem, it was due to a bank holiday and not a real problem. Nevertheless I have disabled this particular test until 5 minutes beyond the next run-time of that test; it has been disabled until 4:50 am of the next day. When I checked this the next day at 08:30h, this test still was at "blue" (disabled) - I expected, that this should either be "green" or any other than "blue". When I clicked into that test I could see, that "inside" it showed the "new" test result as "green", but the test page was "blue". Hope my explanation of the situation is a bit understandeable..... Is the above a bug? Or did I do something wrong? Greetings Christian Christian Becker IT-Services user-e4a19bfb94c0@xymon.invalid<mailto:user-e4a19bfb94c0@xymon.invalid> Mittelrhein-Verlag GmbH August-Horch-Straße 28 D-56070 Koblenz Verleger und Geschäftsführer: Walterpeter Twer Reg.-Gericht Koblenz HRB 121 Finanzamt Koblenz Str.Nr. 22 65 10 285 2 www.rhein-zeitung.de<http://www.rhein-zeitung.de/>;
This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
list John Thurston
▸
On 6/5/2015 5:44 AM, Root, Paul T wrote:
If you set the test to disabled until a certain time, when the test runs, whether it has a green result or not, it will not clear out the disabled status.
When I explain it to my users, I tell them it should have been named "ignore" rather than "disable". Forcing the status to blue doesn't prevent messages from arriving or tests from being run, it just has xymongen ignore everything and present blue. As such, you are seeing the expected behavior.
If you had disabled “until ok” then it would have cleared.
This is one of the nicest improvements from Big Brother :)
--
Do things because you should, not just because you can.
John Thurston XXX-XXX-XXXX
user-ce4d79d99bab@xymon.invalid
Enterprise Technology Services
Department of Administration
State of Alaska
list Paul Root
You are disabling the alarm, not the test. Ignore is probably a better description, yes.
▸
-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of John Thurston
Sent: Friday, June 05, 2015 11:07 AM
To: xymon at xymon.com
Subject: Re: [Xymon] Bug or feature?
On 6/5/2015 5:44 AM, Root, Paul T wrote:If you set the test to disabled until a certain time, when the test runs, whether it has a green result or not, it will not clear out the disabled status.
When I explain it to my users, I tell them it should have been named "ignore" rather than "disable". Forcing the status to blue doesn't prevent messages from arriving or tests from being run, it just has xymongen ignore everything and present blue. As such, you are seeing the expected behavior.
If you had disabled “until ok” then it would have cleared.
This is one of the nicest improvements from Big Brother :)
--
Do things because you should, not just because you can.
John Thurston XXX-XXX-XXXX
user-ce4d79d99bab@xymon.invalid
Enterprise Technology Services
Department of Administration
State of Alaska
This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.