We have Networking devices, that produce a huge output on Discovery. Checkmk
warns with the message “Lost data due to truncation of long output to 2kB”.
It is - obviously - possible to change this limit by clicking on “increase limit”, e.g.:
When you go into this setting and just “blindly” delete the value
and want to save it, Checkmk - correctly - doesn’t allow you to do so
(although the message it “throws” at you could be a little more helpful…):
But: If you leave it “empty”, uncheck the box and save it:
The value becomes “unset”:
If you now “activate changes”, the following happens:
As I said, I found this out by accident, and I don’t think it’s a huge problem,
but… perhaps it shouldn’t be allowed at all, that this value becomes “unset”.
as a Checkmk Partner, I think it would be best to reproduce this on the most current Checkmk version (if not already happened) and report it as a support ticket. That way it can be fixed most efficiently.
Thanks. The “test” above was done on a CEE 2.2.0p17, which - as far as I know - is the latest available. In any case - as per your recommendation - I will open a ticket for this issue, too.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.
