the new stable release 2.3.0p18 of Checkmk is ready for download.
This stable release ships with 28 changes affecting all editions of Checkmk,
1 changes for the Enterprise editions, 0 Cloud Edition specific and
1 Managed Services Edition specific changes.
Changes in all Checkmk Editions:
Checks & agents
16254 Add metric translations mrpe based windows checks…
I found that version 2.3.0p18 is much slower when synchronizing and activating changes in our distributed environment (two or three times slower than 2.3.0p17).
Also my users are complaining about 2.3.0p18 responding much slower (don’t have details at which actions so far)
HI @MasopustC@erik
If you can provide some specific information then we can look into it. If possible create a ticket with some diagnostic information so that we can investigate on this topic.
@chauhan_sudhir
We have now only experienced problems with Nagvis. And we can easily work around this, we are currently using the Nagvis from p17 (1.9.42) and not from p18 (1.9.44). A ticket is already open and the HAR file has also been uploaded.
The ajax_handler.php process alone takes >10 seconds (ONLY in the current Nagvis in p18, in p17 everything is completely normal). Something about Nagvis 1.9.44 or 1.9.43 is definitely different than 1.9.42 (which is used in p17).
We have already been able to rule out warnings / errors in the error_log
It needed a few days, it’s performing better now. I upgraded friday night.
Then saturday evening it was still performing slow. But now a few days later it’s working better.
I did notice an increase of CPU average use on the master site from around 15% towards 30-40% usage, but that might be expected with the 2.3 upgrade?
We also experience the same thing. It has become very slow. It uses twice as much cpu as before the upgrade. “Activate on sites” can sometimes take forever. And lots of other slowness issues.
Hi @MasopustC and @chauhan_sudhir ,
Have you found anything about the slower Activate Changes? We updated our production version from 2.2.0p33 to 2.3.0p33 on Tuesday, and our Activate Changes process has also increased significantly, from about 9 seconds per site to as low as 32 seconds. We have a distributed environment with 10 remote sites.
we are running now 2.3.0p33 and activation still needs up to a minute (or sometimes even more). Although, as mentioned above, we may suffer some issue because of TrendMicro and definitely because one site has a very poor connection. So, I’m not sure if our numbers can be compared to yours.
