diff options
author | Ilya Mashchenko <ilya@netdata.cloud> | 2021-09-29 09:28:26 +0300 |
---|---|---|
committer | GitHub <noreply@github.com> | 2021-09-29 09:28:26 +0300 |
commit | 1b22cba80bc2047b8a392a67aac6c0b7176053ec (patch) | |
tree | 3dd4fdde739c386ad231e506dd657764a1c51299 /web | |
parent | 5e91a7bc0c8b33a8c45d1c20c90af266ebe96454 (diff) |
add sys_devices_system_edac_mc charts info (#11589)
Diffstat (limited to 'web')
-rw-r--r-- | web/gui/dashboard_info.js | 27 |
1 files changed, 27 insertions, 0 deletions
diff --git a/web/gui/dashboard_info.js b/web/gui/dashboard_info.js index a1828f95f8..6a8f03d9a1 100644 --- a/web/gui/dashboard_info.js +++ b/web/gui/dashboard_info.js @@ -738,6 +738,21 @@ netdataDashboard.submenu = { info: 'Non-Uniform Memory Access (NUMA) is a hierarchical memory design the memory access time is dependent on locality. Under NUMA, a processor can access its own local memory faster than non-local memory (memory local to another processor or memory shared between processors). The individual metrics are described in the <a href="https://www.kernel.org/doc/Documentation/numastat.txt" target="_blank">Linux kernel documentation</a>.' }, + 'mem.ecc': { + info: '<p><a href="https://en.wikipedia.org/wiki/ECC_memory" target="_blank">ECC memory</a> '+ + 'is a type of computer data storage that uses an error correction code (ECC) to detect '+ + 'and correct n-bit data corruption which occurs in memory. '+ + 'Typically, ECC memory maintains a memory system immune to single-bit errors: '+ + 'the data that is read from each word is always the same as the data that had been written to it, '+ + 'even if one of the bits actually stored has been flipped to the wrong state.</p>'+ + '<p>Memory errors can be classified into two types: '+ + '<b>Soft errors</b>, which randomly corrupt bits but do not leave physical damage. '+ + 'Soft errors are transient in nature and are not repeatable, can be because of electrical or '+ + 'magnetic interference. '+ + '<b>Hard errors</b>, which corrupt bits in a repeatable manner because '+ + 'of a physical/hardware defect or an environmental problem.' + }, + 'ip.ecn': { info: '<a href="https://en.wikipedia.org/wiki/Explicit_Congestion_Notification" target="_blank">Explicit Congestion Notification (ECN)</a> '+ 'is an extension to the IP and to the TCP that allows end-to-end notification of network congestion without dropping packets. '+ @@ -1322,6 +1337,18 @@ netdataDashboard.context = { info: 'The amount of memory with physical corruption problems, identified by <a href="https://en.wikipedia.org/wiki/ECC_memory" target="_blank">ECC</a> and set aside by the kernel so it does not get used.' }, + 'mem.ecc_ce': { + info: 'The number of correctable (single-bit) ECC errors. '+ + 'These errors do not affect the normal operation of the system '+ + 'because they are still being corrected. '+ + 'Periodic correctable errors may indicate that one of the memory modules is slowly failing.' + }, + + 'mem.ecc_ue': { + info: 'The number of uncorrectable (multi-bit) ECC errors. '+ + 'An uncorrectable error is a fatal issue that will typically lead to an OS crash.' + }, + 'mem.cachestat_ratio': { info: 'When the processor needs to read or write a location in main memory, it checks for a corresponding entry in the page cache. If the entry is there, a page cache hit has occurred and the read is from the cache. If the entry is not there, a page cache miss has occurred and the kernel allocates a new entry and copies in data from the disk. Netdata calculates the percentage of accessed files that are cached on memory. <a href="https://github.com/iovisor/bcc/blob/master/tools/cachestat.py#L126-L138" target="_blank">The ratio</a> is calculated counting the accessed cached pages (without counting dirty pages and pages added because of read misses) divided by total access without dirty pages.' }, |