Check other people's stats pages, usually they mention how they're graphing those or their sources.
Here's mine (fwiw I finally got a "hit" it seems, only a 12k clients peak for a 10mbit netspeed, not bad): http://rikku.vrillusions.com/ntp/ The ones that put the least stress on your server as far data collecting is what your offset is with: ntpq -c 'rv 0 offset' This gets the offset value for associate id 0 (you) and that's how far off your clock is from "true" time in msec The other low stress one is: ntpdc -c iostats The received packets and sent packets are the number of udp packets transmitted by ntpd. The ones that get a client count can be very processor intensive on slower machines. Perhaps not as much so with the new dns system and not getting 50k client spikes. Jeffrey Goldberg wrote: > On Sep 15, 2007, at 11:45 AM, Chuck wrote: > >> what are most of you using to monitor local ntp servers? i am >> interested only >> in traffic and number of connections, preferably reported by source >> ip. > > For a while I used the scripts that someone already mentioned, but > I'd like to point out something that I haven't seen in other > messages. Monitoring consumes far more resources than the NTP > service itself. So monitor to satisfy curiosity and to get a feel > for what's going on. But after a while, you may wish to discontinue > monitoring at all. > > -j > -- Todd http://www.vrillusions.com/ My PGP Key ID: 0xBC90230C
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
