| Re: [chrony-dev] SNMP agent |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] SNMP agent
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 14 Nov 2023 09:53:26 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1699952009; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=OPEq1euUplhGg66wrupau7xLQwRY9M8d1Brg6TMsODU=; b=cwLTmw1A7GslZ75fS+YKZEHBFnR0IEwkWRhUiU30qwExw7bZWqkn2Q/4z72wS5vZeF5eRg OJaCff4OyKmVU+kOqgES6KUWzosZ46yMLG3pI4HvAeOmhJ142NH0fNow8iDKTLnjBTsjBl th7Wob0YOX9i9pCGxhp+iGNbtXkyNWg=
On Tue, Nov 14, 2023 at 07:59:38AM +0000, Marko Hrastovec wrote:
> There is already a standard MIB
> (https://datatracker.ietf.org/doc/html/rfc5907) for ntp monitoring. I
> propose to make an agentX or subagent for snmpd in chrony, which would
> report ntp status via snmpd using a provided MIB. More information
> about subagents can be found here
> https://net-snmp.sourceforge.io/wiki/index.php/TUT:Writing_a_Subagent
>
> I am willing to contribute the code, but I am unfamiliar with chrony
> source. Is there an interest or will to incorporate the SNMP monitoring
> into chrony or not?
I think it should be a separate project using the cmdmon protocol for
communication with chronyd as used by chronyc. With this library it
should be easy
https://gitlab.com/chrony/libchrony
Note that it's still in early stages of development and the API might
change.
--
Miroslav Lichvar
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.