[Xymon] status+ in custom tests

J.C. Cleaver cleaver at terabithia.org
Thu Apr 7 00:08:56 CEST 2016


Using this, it might actually be easier to just look at the message
directly than calculate the diff. Inelegant, but something along the lines
of this:

[rpmbuild at rhel6-x86-64 /]$
xymon localhost "xymondboard msg=status\+ fields=hostname,testname,msg" |
grep -v -- status+30 | cut -b 1-132

rhel6-x86-64.build|xymonproxy3|status+11 rhel6-x86-64,build.xymonproxy3
green Wed Sep 17 17:33:07 2014 - xymon proxy up: 0 days, 00:
rhel6-x86-64.build|xymonproxy2|status+11 rhel6-x86-64,build.xymonproxy2
green Sun May 24 17:08:31 2015 - xymon proxy up: 0 days, 00:
rhel6-x86-64.build|xymond|status+11 rhel6-x86-64,build.xymond green Wed
Apr  6 15:03:46 2016 - xymon daemon up: 5 days, 22:00:03\nSt
rhel6-x86-64.build|xymonproxy|status+11 rhel6-x86-64,build.xymonproxy
green Wed Apr  6 15:03:48 2016 - xymon proxy up: 5 days, 22:00


HTH,
-jc


On Wed, April 6, 2016 8:16 am, Ralph Mitchell wrote:
> You can pick up the raw data from xymondboard on the server:
>
>    xymon localhost "xymondboard test=svcacct
> fields=hostname,logtime,validtime"
>
> *logtime* Unix timestamp when the log message was received.
>
> *validtime* Unix timestamp when the log message is no longer valid (it
> goes
> purple at this time).
>
> Subtract logtime from validtime to get number of seconds.  If the result
> is
> not 1800, it's a non-standard validity time.
>
> Ralph Mitchell
>
>
>
> On Wed, Apr 6, 2016 at 11:00 AM, Neil Simmonds
> <neilsimmonds1808 at gmail.com>
> wrote:
>
>> Hi all,
>>
>> Is there any way on the Xymon server to check if any custom tests have a
>> validity timeout that is not default because they have a parameter on
>> the
>> status command setting a custom validity.
>>
>> I'd prefer to do it from the server as it would be very time consuming
>> to
>> have to log onto every client to check it.
>>
>> I know we have some that aren't using the default 30 minutes but I
>> really
>> need to identify them due to other people writing custom scripts and
>> apparently not understanding what status+**** does.
>>
>> Thanks, Neil.
>>
>> _______________________________________________
>> Xymon mailing list
>> Xymon at xymon.com
>> http://lists.xymon.com/mailman/listinfo/xymon
>>
>>
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon
>





More information about the Xymon mailing list