Hi, Johannes. It's not the most "elegant" solution with respect to the capabilities of ntpd, and there is a bit of a system performance hit involved, but using netfilter (IPTables) to log the connections then parsing that as time-series metrics may give you what you need.
I'm doing this with telegraf/influxdb. On the latter, there is a very rich capability for analysis and display (i.e. I can show how many sources are hitting each of the anycast sources vs. how many clients are requesting time from the real IPs, at what time of day, etc. Additionally, if you want something with good data retention, an external tool, or at least offloading the task to files would seem to give you much more flexibility than the memory of the daemon process. Dan ----- Original Message ----- > From: "Johannes Weber" <johan...@webernetz.net> > To: "questions" <questions@lists.ntp.org> > Sent: Monday, February 6, 2017 3:10:49 PM > Subject: [ntp:questions] Monitoring Number of Clients > Hello NTP list, > > I have one question concerning the monstats and mrulist commands. I am > monitoring my NTP servers and I want to graph the current clients. I am > using the "addresses" line from the monstats output. > However, it seems that every client that is gone many days ago (!) is > still listed within the "addresses" section and not only in the "peak > addresses". Same is true within the mrulist output which lists addresses > that have a lstint many days ago. > > So my question is: How can I get a number of the "most recent" clients, > i.e., clients that have a lstint < 2000 or the like. (One bad approach > might be to use the mrulist output and to grep all lines that have an > lstint < 2000. But I am searching for a better way to do it.) > > Thanks in advance! > -- Dan Geist dan(@)polter.net _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
