Mine always work very well, so at least in my environment, this isn't a concern. It is rare to see anything but 0s.
From: Ralph Mitchell [mailto:user-00a5e44c48c0@xymon.invalid]
Sent: Wednesday, September 25, 2013 06:05 PM
To: Novosielski, Ryan
Cc: Japheth Cleaver <user-87556346d4af@xymon.invalid>; xymon at xymon.com <xymon at xymon.com>
Subject: Re: [Xymon] CLOCK and CPU test
Just FYI, the clock drift is measured by comparing the date/time sent at the bottom of the client message against the Xymon server clock. I have some systems on slow network connections and sometimes it takes a couple of retries for the status report to get through, and by then the client time is often 10 - 30 seconds adrift.
In other words, it's not simply the client working out that its own clock is slow.
Ralph Mitchell
On Sep 25, 2013 4:22 PM, "Novosielski, Ryan" <user-6e4f7a3bb37f@xymon.invalid<mailto:user-6e4f7a3bb37f@xymon.invalid>> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 09/25/2013 04:16 PM, Japheth Cleaver wrote:
On Wed, September 25, 2013 12:35 pm, Novosielski, Ryan wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all,
I suspect I know the answer to this but want to check:
I'm running Xymon 4.3.12. My manager has recently brought up the
need to have the clock drift monitored (it caused problems with
a DB server when there was massive drift once for some reason).
I looked into how to do this and it looks like the highest level
that clock drift can cause Xymon to alert at is yellow. This
means that if I wanted to be alerted, I'd have to also get
alerted for yellow CPU on that machine, right? So far my only
idea is to raise the yellow level for CPU. I don't really want
to bother with an external test.
Any tips?
According to
http://www.xymon.com/xymon/help/manpages/man5/analysis.cfg.5.html
you should be able to add a line like
CLOCK 15 red
... to an analysis.cfg file (or *.d/ entry) to have it go red if
the clock delta exceeds that absolute value. I have to admit not
having tested that ever though.
If that doesn't work, you might be able to simulate it (or assign
the color to a different test entirely) with a DS entry; something
like:
DS cpu clock.rrd:la <-15 COLOR=red "TEXT=System clock is &V
seconds off" DS cpu clock.rrd:la >15 COLOR=red "TEXT=System clock
is &V seconds off"
Wonderful! I must have been reading an old copy of that documentation
(Google'd for it instead of using what was on the system). Thanks Japheth!
- --
____*Note: UMDNJ is now Rutgers-Biomedical and Health Sciences*
|| \\UTGERS |---------------------*O*---------------------
||_// Biomedical | Ryan Novosielski - Sr. Systems Programmer
|| \\ and Health | user-46c89e614701@xymon.invalid<mailto:user-46c89e614701@xymon.invalid> - 973/972.0922<tel:973%2F972.0922> (2x0922)
|| \\ Sciences | OIT/EI-Academic Svcs. - ADMC 450, Newark
`'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlJDRdAACgkQmb+gadEcsb61SQCaAgCrteviCwy+bUMIdDqsp0gd
+N8AoL9Wy6srB22AS1kA9iWdus++2gJZ
=d+Pi
-----END PGP SIGNATURE-----