Hello - thanks again, some follow up questions. I picked one host with stale services and upgraded the local agent to v1.6. What I noticed is that on our 1.5 server instance, the update times for all services are basically the same:
On the 1.5 server, everytime the Check_MK service “Checked” would update, everything underneath it would update at the same moment. Sometimes this happens on our 1.6 server, but more often than not I see this:
So the Check_MK service would update and everything else (every single other service, I just cropped the image) would lag behind it, sometimes by whole minutes.
I tried testing the local agent itself (check_mk_agent.exe test) and testing from the server (cmk -d ) but I don’t see anything that would indicate issues with the data returned - nothing truncated, no errors, etc.
From what I can see, both of our server instances have the same factory settings for staleness, check intervals, concurrent checks and helpers, etc. (oddly enough, on both servers, the helper usage is almost non-existent, basically 0.1%)
Apologies if I’m thinking about this wrong, but if the Check_MK service itself returns data, shouldn’t all of the services using that data update more or less immediately? Is there any additional debugging or logging you would recommend so I can figure out what might be throwing the 1.6 instance off?
Thanks!