![]() ![]() To see the amount of available memory, including caches and buffers that can be opened up, we would use node_memory_MemAvailable_bytes. Here, node_memory_MemFree_bytes denotes the amount of free memory left on the system, not including caches and buffers that can be cleared. While on its own this is not the most helpful number, it helps us calculate the amount of in-use memory: node_memory_MemTotal_bytes - node_memory_MemFree_bytes Node_memory_MemTotal_bytes provides us with the amount of memory on the server as a whole - in other words, if we have 64 GB of memory, then this would always be 64 GB of memory, until we allocate more. The metric expressions listed above provide us with what is essentially the same data as free but in a time series where we can witness trends over time or compare memory between multiple system builds. Those who do a bit of systems administration, incident response, and the like have probably used free before to check the memory of a system. ![]() However, of the vast array of memory information we have access to, there are only a few core ones we will have to concern ourselves with much of the time: Memory metrics for Prometheus and other monitoring systems are retreived through the /proc/meminfo file in Prometheus in particular, these metrics are prefixed with node_memory in the expression editor, and quite a number of them exist. When it comes to looking at our memory metrics, there are a few core metrics we want to consider. ![]() Run stress -m 1 on your server before starting this lesson. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |