Content Comparison

...

There are log lines, that are missing from the event console but present in the monitored log file.
Specifically The configured patterns and filters should allow them to be forwarded to the event console.
Additionally, this behavior is not easily reproducible and happens at random times.

...

1. The agent is queried normally, and the agent output is cached on the Checkmk server
2. The periodic service discovery runs at their configured interval and 120 seconds or more after the agent was queried
3. The periodic service discovery considers the cached output data too old and fetches a new fresh agent output
4. This output contains new log lines but is never processed by the logwatch check plugin and therefore not forwarded to the event console
5. When the agent is queried on the normal interval again it can not realize, that log messages have been fetched but not been processed

Solution

...

...

bgColor	#fff

There are two main solutions:

1. Decrease the normal check interval for the Checkmk agent below 120 seconds

2. Manually change the affected site's main.mk and add the following line.lines. Adapt the $SECONDS to be at least the normal check interval of the Checkmk agent!

   Warning
   This is not supported by tribe29! Do this at your own risk!

   
   

   Code Block
   language bash theme RDark
   TBDmax_cachefile_age = $SECONDS cluster_max_cachefile_age = $SECONDS

   
   

Related articles

...