16776 FIX chrony: change default warning level

SUP-19602

Change-Id: Iecb7f0db069522d68999c15bbc66cd5f267be8dd

.werks/16776.md

@@ -0,0 +1,19 @@
+[//]: # (werk v2)
+# chrony: change default warning level
+
+key        | value
+---------- | ---
+date       | 2024-08-19T06:14:01+00:00
+version    | 2.4.0b1
+class      | fix
+edition    | cre
+component  | checks
+level      | 1
+compatible | no
+
+Chrony's default `minpoll` and `maxpoll` values are 64 seconds and 1024 seconds.
+In standard situations (good internet connection, low error etc)
+the interval between polls should stick near the max value (1024 seconds).
+(see `https://chrony-project.org/examples.html#_client_using_public_servers`)
+
+Beacuse of that, the default WARN alert is now set to 1025 seconds.

cmk/plugins/collection/agent_based/chrony.py

@@ -163,7 +163,7 @@ def check_chrony(params, section_chrony, section_ntp):
     check_function=check_chrony,
     check_default_parameters={
         "ntp_levels": (10, 200.0, 500.0),
-        "alert_delay": (1800, 3600),  # chronys default maxpoll is 10 (1024s)
+        "alert_delay": (1025, 3600),  # chronys default maxpoll is 10 (1024s)
     },
     check_ruleset_name="ntp_time",
 )

cmk/plugins/collection/checkman/chrony

@@ -12,6 +12,11 @@ description:
  You can set levels for the maximum stratum and for the time offset
  in milliseconds. The configuration is compatible with {ntp}.
 
+ The default {WARN} alert is set to 1025 seconds
+ (default chrony's {maxpoll} values is 1024 seconds,
+ see https://chrony-project.org/examples.html#_client_using_public_servers)
+ and thus differs from the default {WARN} alert of the {NTP} check.
+
  When {chrony} is not found running, the check goes to {CRIT}.
 
 discovery: