Re: [chrony-users] Monitoring Chrony

On Thu, Feb 11, 2016 at 1:58 PM, Miroslav Lichvar wrote: > On Thu, Feb 11, 2016 at 10:54:49AM +0100, Ben Kochie wrote: > > So far, I haven't been able to find a good programmatic way to extract > > stats with chronyc. There are a bunch of annoying parsing issues with > >

Re: [chrony-users] Monitoring Chrony

On Thu, Feb 11, 2016 at 10:54:49AM +0100, Ben Kochie wrote: > So far, I haven't been able to find a good programmatic way to extract > stats with chronyc. There are a bunch of annoying parsing issues with > things like the sourcestats command. The offset includes a precision, so I > have to

Re: [chrony-users] Monitoring Chrony

Log parsing is possible, there is a tool called mtail that can parse logs to collect metrics. It is generally recommend to ask services directly about their current state rather than regexping logs. This way the stats are read in a more on-demand way. On Feb 11, 2016 11:35 AM, "Bryan