Why? Because the kernel would like to select swap memory for caches. That sounds wonderful because swap space usage would be minimal, right? The first surprise: the Linux system is cheeky and outsources parts of the processes to the swap partition. ![]() Now, let's assume we have an app or a tool that needs 64 GB of RAM. And let's just forget the fact that the kernel itself needs some space. Our server has 64 GB RAM and just as much swap partition. How does it make sense if a RAM threshold is above 100%? ![]() This led to a new, much bigger problem: explaining it! The check plug-in was running processes correctly, working to such an extent that many users were surprised and suspicious of the results. In my opinion, Checkmk has the best, most accurate, and, above all, most technically “correct” Linux memory check imaginable. Checkmk's Linux memory check needed to be reworked entirely to ensure we monitor swap usage accurately and display information correctly.Īfter a few days of work, we did it.Many important parameters are not shown for free, but they can be critical for how the system runs.Even the apparent idea of considering buffers/caches as free is not necessarily correct!. ![]() ![]()
0 Comments
Leave a Reply. |