Hey @robin.gierse I appreciate there suggestion but when I go and discuss to implement that I get to know it is not feasible for us!!
So I just have the question It it is fixed in 1.6.0p16 then why this comes up in 1.6.0p20.
or possible to get manual fix, so I can perform same thing to fix ,that you check_mk engineer did here!