DOWNTIME can be used for any test (local or network).
Here an example of setting for Oracle that we use:
DOWNTIME=orcl,orcl-chk,procs,msgs:*:0130:0230:Backups
"orcl" is a local check running on the client and "orcl-chk" is a remote
check -connecting to the listener- performed from the server.
Dominique
user-9219fb9415b1@xymon.invalid wrote:
I was able to test it now. Indeed the DOWNTIME tag has no effect to the
database test. Do I have to interpret the DOWNTIME tag for myself or is
there a possibility to "downtime" specific tests in hobbit itself.
can I somehow tell Hobbit to ignore bad test results in certain
times,
like the DOWNTIME tag does for network tests?
e.g. I do some Oracle database tests and shutdown the databases on
weekends for backup. I don't want this planned downtime to appear in
the Non-Green-Systems View and in the Availability reports.
Maybe I can "missuse" the badTEST tag somehow?> If this is really
planned and regularly scheduled, then use the DOWNTIME
tag. If it can be variable, you can schedule downtime in advance with
the enable/disable menu item.
It is really planned. But as I see it, the DOWNTIME tag is only
valid for the network test. But the network is up during this
period. So the system itself is green, but the oracle test is red
and is so propagated to the summary pages above.
But I cannot really test it, because I cannot shutdown my databases
at the current time. But we will see what happens tomorrow.
Thorsten
If you are not the intended addressee, please inform us immediately
that you have received this e-mail in error, and delete it. We thank
you for your cooperation.
If you are not the intended addressee, please inform us immediately that
you have received this e-mail in error, and delete it. We thank you for
your cooperation.