|Re: [chrony-users] Monitoring Chrony|
[ Thread Index | Date Index | More chrony.tuxfamily.org/chrony-users Archives ]
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 parse the precision and convert that to be all in one precision.
Yeah, I've struggled with that too. I like the human readable format
when inspecting the chrony state, but it does complicate parsing quite
> A couple of specific questions.
> * Would chrony be interested in supporting the Prometheus metrics format?
I looked at the page describing the archicture, but it's not clear to
me how would a support in chrony look like. Would chronyd or something
using the chronyc protocol be listening on a port for requests? Or
would it periodically push data over socket somewhere? The page
listing client libraries does't include a C library.
> * Is there a mode for the various metrics outputs to be more machine
> readable? (json?)
No, not yet. I'd like to add a raw mode to chronyc that would print
the values in something easily parseable. I'm not sure about json, I'd
probably prefer something usable even from shell using just sed or
> * Is there documentation for the chronyc protocol outside the code?
No, unfortunately not. FWIW, the protocol is quite simple, almost all
information you would need to implement a new client is contained in
> * Are there any non-C chronyc client implementations? (python/ruby/whatever)
Probably not, at least I've not seen anything. At some point I'd like
to split chronyc into a library and a client application. Bindings for
other languages could then be easily created.
|Mail converted by MHonArc 2.6.19+||http://listengine.tuxfamily.org/|