On Fri, March 11, 2016 9:54 am, John Thurston wrote:
*snip*
Alternatively, define an ext script on your inaccessible host to send a
status message in every X minutes with an appropriate TTL
status[+LIFETIME][/group:GROUP] HOSTNAME.TESTNAME COLOR <additional
text>
Something like:
xymon xyserver.foo.com "status+6 client.foo.com.alive green"
This will put a column "alive" for host "client" which will go purple
six minutes after the last green message is received.
This is probably the most "xymony" way of solving the issue :)
That being said, it wouldn't be too hard to add a default status lifetime
as another per-host option in hosts.cfg, overriding the global default,
but not a per-message TTL.
This would apply to *all* incoming status messages for that host, though,
including those which come from varying sources and (potentially)
intervals. xymond_client and xymonnet intervals should be considered along
with any other source of statuses to make sure they're all recurring under
the TTL, or that the failure modes encountered count as features and not
bugs...
Regards,
-jc