5.02021-11-21T21:21:06ZTemplatesApp Chrony ServiceApp Chrony Service## Overview
This template will parse the various types of data from the acquisition result of chronyc tracking command.
This allows you to detect the change of the time of displacement and Stratum by chrony.
TemplatesTime synchronization- Number of chrony processesproc.num[,chrony]60Time synchronization{max(#1)}=0Chrony service is down on {HOST.NAME}DISABLEDAVERAGE
- Chrony Last offsetZABBIX_ACTIVEsystem.run[chronyc tracking|grep "Last offset"|awk '{print $4}']1800FLOATsThis is the estimated local offset on the last clock update.Time synchronization
- Chrony Leap statusZABBIX_ACTIVEsystem.run[chronyc tracking|grep "Leap status"|awk '{print $4" "$5}']18000CHARThis is the leap status, which can be Normal, Insert second, Delete second or Not synchronised.Time synchronization{regexp("Not synchronised")}=1{HOST.NAME} is Not synchronizedDISABLEDHIGH
- Chrony synchronized serverZABBIX_ACTIVEsystem.run[chronyc tracking|grep "Reference ID"|awk '{print $4$5}']18000CHARThis is the reference ID and name (or IP address) if available, of the server to which the computer is currently synchronized.Time synchronization{diff(0)}=1Chrony servers are synchronized has been changed .DISABLEDINFO
- Chrony RMS offsetZABBIX_ACTIVEsystem.run[chronyc tracking|grep "RMS offset"|awk '{print $4}']1800FLOATsThis is a long-term average of the offset value.Time synchronization
- Chrony Root delayZABBIX_ACTIVEsystem.run[chronyc tracking|grep "Root delay"|awk '{print $4}']1800FLOATsThis is the total of the network path delays to the stratum-1 computer from which the computer is ultimately synchronized. In certain extreme situations, this value can be negative. (This can arise in a symmetric peer arrangement where the computers’ frequencies are not tracking each other and the network delay is very short relative to the turn-around time at each computer.)Time synchronization
- Chrony StratumZABBIX_ACTIVEsystem.run[chronyc tracking|grep "Stratum"|awk '{print $3}']1800The stratum indicates how many hops away from a computer with an attached reference clock we are. Such a computer is a stratum-1 computer, so the computer in the example is two hops awayTime synchronization
- Chrony Update intervalZABBIX_ACTIVEsystem.run[chronyc tracking|grep "Update interval"|awk '{print $4}']1800FLOATsThis is the total dispersion accumulated through all the computers back to the stratum-1 computer from which the computer is ultimately synchronized. Dispersion is due to system clock resolution, statistical measurement variations etc.Time synchronization
- Version of chrony(d) runningZABBIX_ACTIVEsystem.run[chronyd --version]36000CHARTime synchronization