**CMK version: Checkmk Enterprise Edition 2.1.0p37 **
OS version: Red Hat Enterprise Linux 9.5 (Plow)
**Error message: Service event history says “Socket timed out afet 10 s”
Service “Response time” graph shows a maximun value of 7,30 s at this period.
**
Please, Any help to understand what is going on?
BR
You can see how the graph is flat during what I assume to be the CRIT period. Usually it fluctuates a little bit. This shows us that something is off there.
This issue happens because the graph only shows gaps for periods without performance data if the period is longer than 8460 seconds (141 minutes or 2h 21m). An example can be seen on your graph between about 14:00 and 17:00. This period was long enough to cause a gap.
The one starting at about 21:10 however was too short to have the graph display a gap.
If the service is critical for less than the 8460 seconds, say 30 minutes (1800 seconds) for example, the graph will fill the gap with a flat line between the last value before the outage and the first value after the outage.
For a bit more background about this behaviour, read this: Graphs display data for stale periods
From that thread:
CRE users can change the RRD heartbeat value of 8460 seconds inside the config file ~/etc/pnp4nagios/process_perfdata.cfg, CEE users would need to change it inside a python file of Checkmk: ~/lib/check_mk/base/cee/rrd.py (but this would be overwritten by updates).
