netdata.tbock.duckdns.org
Open in
urlscan Pro
92.91.177.197
Public Scan
Submitted URL: http://netdata.tbock.duckdns.org/
Effective URL: https://netdata.tbock.duckdns.org/
Submission Tags: krdtest
Submission: On January 03 via api from JP — Scanned from FR
Effective URL: https://netdata.tbock.duckdns.org/
Submission Tags: krdtest
Submission: On January 03 via api from JP — Scanned from FR
Form analysis 5 forms found in the DOM
<form id="optionsForm1" class="form-horizontal">
<div class="form-group">
<table>
<tbody>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-success" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="stop_updates_when_focus_is_lost" type="checkbox" checked="checked" data-toggle="toggle" data-offstyle="danger" data-onstyle="success"
data-on="On Focus" data-off="Always" data-width="110px">
<div class="toggle-group"><label class="btn btn-success toggle-on">On Focus</label><label class="btn btn-danger active toggle-off">Always</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>When to refresh the charts?</strong><br><small>When set to <b>On Focus</b>, the charts will stop being updated if the page / tab does not have the focus of the user. When set to <b>Always</b>, the charts will
always be refreshed. Set it to <b>On Focus</b> it to lower the CPU requirements of the browser (and extend the battery of laptops and tablets) when this page does not have your focus. Set to <b>Always</b> to work on another window (i.e.
change the settings of something) and have the charts auto-refresh in this window.</small></td>
</tr>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-primary" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="eliminate_zero_dimensions" type="checkbox" checked="checked" data-toggle="toggle" data-on="Non Zero" data-off="All"
data-width="110px">
<div class="toggle-group"><label class="btn btn-primary toggle-on">Non Zero</label><label class="btn btn-default active toggle-off">All</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Which dimensions to show?</strong><br><small>When set to <b>Non Zero</b>, dimensions that have all their values (within the current view) set to zero will not be transferred from the netdata server (except if
all dimensions of the chart are zero, in which case this setting does nothing - all dimensions are transferred and shown). When set to <b>All</b>, all dimensions will always be shown. Set it to <b>Non Zero</b> to lower the data
transferred between netdata and your browser, lower the CPU requirements of your browser (fewer lines to draw) and increase the focus on the legends (fewer entries at the legends).</small></td>
</tr>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-default off" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="destroy_on_hide" type="checkbox" data-toggle="toggle" data-on="Destroy" data-off="Hide" data-width="110px">
<div class="toggle-group"><label class="btn btn-primary toggle-on">Destroy</label><label class="btn btn-default active toggle-off">Hide</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>How to handle hidden charts?</strong><br><small>When set to <b>Destroy</b>, charts that are not in the current viewport of the browser (are above, or below the visible area of the page), will be destroyed and
re-created if and when they become visible again. When set to <b>Hide</b>, the not-visible charts will be just hidden, to simplify the DOM and speed up your browser. Set it to <b>Destroy</b>, to lower the memory requirements of your
browser. Set it to <b>Hide</b> for faster restoration of charts on page scrolling.</small></td>
</tr>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-default off" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="async_on_scroll" type="checkbox" data-toggle="toggle" data-on="Async" data-off="Sync" data-width="110px">
<div class="toggle-group"><label class="btn btn-primary toggle-on">Async</label><label class="btn btn-default active toggle-off">Sync</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Page scroll handling?</strong><br><small>When set to <b>Sync</b>, charts will be examined for their visibility immediately after scrolling. On slow computers this may impact the smoothness of page scrolling.
To update the page when scrolling ends, set it to <b>Async</b>. Set it to <b>Sync</b> for immediate chart updates when scrolling. Set it to <b>Async</b> for smoother page scrolling on slower computers.</small></td>
</tr>
</tbody>
</table>
</div>
</form><form id="optionsForm2" class="form-horizontal">
<div class="form-group">
<table>
<tbody>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-primary" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="parallel_refresher" type="checkbox" checked="checked" data-toggle="toggle" data-on="Parallel" data-off="Sequential"
data-width="110px">
<div class="toggle-group"><label class="btn btn-primary toggle-on">Parallel</label><label class="btn btn-default active toggle-off">Sequential</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Which chart refresh policy to use?</strong><br><small>When set to <b>parallel</b>, visible charts are refreshed in parallel (all queries are sent to netdata server in parallel) and are rendered
asynchronously. When set to <b>sequential</b> charts are refreshed one after another. Set it to parallel if your browser can cope with it (most modern browsers do), set it to sequential if you work on an older/slower computer.</small>
</td>
</tr>
<tr class="option-row" id="concurrent_refreshes_row">
<td class="option-control">
<div class="toggle btn btn-primary" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="concurrent_refreshes" type="checkbox" checked="checked" data-toggle="toggle" data-on="Resync" data-off="Best Effort"
data-width="110px">
<div class="toggle-group"><label class="btn btn-primary toggle-on">Resync</label><label class="btn btn-default active toggle-off">Best Effort</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Shall we re-sync chart refreshes?</strong><br><small>When set to <b>Resync</b>, the dashboard will attempt to re-synchronize all the charts so that they are refreshed concurrently. When set to
<b>Best Effort</b>, each chart may be refreshed with a little time difference to the others. Normally, the dashboard starts refreshing them in parallel, but depending on the speed of your computer and the network latencies, charts start
having a slight time difference. Setting this to <b>Resync</b> will attempt to re-synchronize the charts on every update. Setting it to <b>Best Effort</b> may lower the pressure on your browser and the network.</small></td>
</tr>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-success" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="sync_selection" type="checkbox" checked="checked" data-toggle="toggle" data-on="Sync" data-off="Don't Sync" data-onstyle="success"
data-offstyle="danger" data-width="110px">
<div class="toggle-group"><label class="btn btn-success toggle-on">Sync</label><label class="btn btn-danger active toggle-off">Don't Sync</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Sync hover selection on all charts?</strong><br><small>When enabled, a selection on one chart will automatically select the same time on all other visible charts and the legends of all visible charts will be
updated to show the selected values. When disabled, only the chart getting the user's attention will be selected. Enable it to get better insights of the data. Disable it if you are on a very slow computer that cannot actually do
it.</small></td>
</tr>
</tbody>
</table>
</div>
</form><form id="optionsForm3" class="form-horizontal">
<div class="form-group">
<table>
<tbody>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-default off" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="legend_right" type="checkbox" checked="checked" data-toggle="toggle" data-on="Right" data-off="Below" data-width="110px">
<div class="toggle-group"><label class="btn btn-primary toggle-on">Right</label><label class="btn btn-default active toggle-off">Below</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Where do you want to see the legend?</strong><br><small>Netdata can place the legend in two positions: <b>Below</b> charts (the default) or to the <b>Right</b> of
charts.<br><b>Switching this will reload the dashboard</b>.</small></td>
</tr>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-success" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="netdata_theme_control" type="checkbox" checked="checked" data-toggle="toggle" data-offstyle="danger" data-onstyle="success"
data-on="Dark" data-off="White" data-width="110px">
<div class="toggle-group"><label class="btn btn-success toggle-on">Dark</label><label class="btn btn-danger active toggle-off">White</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Which theme to use?</strong><br><small>Netdata comes with two themes: <b>Dark</b> (the default) and <b>White</b>.<br><b>Switching this will reload the dashboard</b>.</small></td>
</tr>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-primary" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="show_help" type="checkbox" checked="checked" data-toggle="toggle" data-on="Help Me" data-off="No Help" data-width="110px">
<div class="toggle-group"><label class="btn btn-primary toggle-on">Help Me</label><label class="btn btn-default active toggle-off">No Help</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Do you need help?</strong><br><small>Netdata can show some help in some areas to help you use the dashboard. If all these balloons bother you, disable them using this
switch.<br><b>Switching this will reload the dashboard</b>.</small></td>
</tr>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-primary" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="pan_and_zoom_data_padding" type="checkbox" checked="checked" data-toggle="toggle" data-on="Pad" data-off="Don't Pad"
data-width="110px">
<div class="toggle-group"><label class="btn btn-primary toggle-on">Pad</label><label class="btn btn-default active toggle-off">Don't Pad</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Enable data padding when panning and zooming?</strong><br><small>When set to <b>Pad</b> the charts will be padded with more data, both before and after the visible area, thus giving the impression the whole
database is loaded. This padding will happen only after the first pan or zoom operation on the chart (initially all charts have only the visible data). When set to <b>Don't Pad</b> only the visible data will be transfered from the
netdata server, even after the first pan and zoom operation.</small></td>
</tr>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-primary" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="smooth_plot" type="checkbox" checked="checked" data-toggle="toggle" data-on="Smooth" data-off="Rough" data-width="110px">
<div class="toggle-group"><label class="btn btn-primary toggle-on">Smooth</label><label class="btn btn-default active toggle-off">Rough</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Enable Bézier lines on charts?</strong><br><small>When set to <b>Smooth</b> the charts libraries that support it, will plot smooth curves instead of simple straight lines to connect the points.<br>Keep in
mind <a href="http://dygraphs.com" target="_blank">dygraphs</a>, the main charting library in netdata dashboards, can only smooth line charts. It cannot smooth area or stacked charts. When set to <b>Rough</b>, this setting can lower the
CPU resources consumed by your browser.</small></td>
</tr>
</tbody>
</table>
</div>
</form><form id="optionsForm4" class="form-horizontal">
<div class="form-group">
<table>
<tbody>
<tr class="option-row">
<td colspan="2" align="center"><small><b>These settings are applied gradually, as charts are updated. To force them, refresh the dashboard now</b>.</small></td>
</tr>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-success" data-toggle="toggle" style="width: 110px; height: 38px;"><input id="units_conversion" type="checkbox" checked="checked" data-toggle="toggle" data-on="Scale Units" data-off="Fixed Units"
data-onstyle="success" data-width="110px">
<div class="toggle-group"><label class="btn btn-success toggle-on">Scale Units</label><label class="btn btn-default active toggle-off">Fixed Units</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Enable auto-scaling of select units?</strong><br><small>When set to <b>Scale Units</b> the values shown will dynamically be scaled (e.g. 1000 kilobits will be shown as 1 megabit). Netdata can auto-scale these
original units: <code>kilobits/s</code>, <code>kilobytes/s</code>, <code>KB/s</code>, <code>KB</code>, <code>MB</code>, and <code>GB</code>. When set to <b>Fixed Units</b> all the values will be rendered using the original units
maintained by the netdata server.</small></td>
</tr>
<tr id="settingsLocaleTempRow" class="option-row">
<td class="option-control">
<div class="toggle btn btn-primary" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="units_temp" type="checkbox" checked="checked" data-toggle="toggle" data-on="Celsius" data-off="Fahrenheit" data-width="110px">
<div class="toggle-group"><label class="btn btn-primary toggle-on">Celsius</label><label class="btn btn-default active toggle-off">Fahrenheit</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Which units to use for temperatures?</strong><br><small>Set the temperature units of the dashboard.</small></td>
</tr>
<tr id="settingsLocaleTimeRow" class="option-row">
<td class="option-control">
<div class="toggle btn btn-success" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="seconds_as_time" type="checkbox" checked="checked" data-toggle="toggle" data-on="Time" data-off="Seconds" data-onstyle="success"
data-width="110px">
<div class="toggle-group"><label class="btn btn-success toggle-on">Time</label><label class="btn btn-default active toggle-off">Seconds</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Convert seconds to time?</strong><br><small>When set to <b>Time</b>, charts that present <code>seconds</code> will show <code>DDd:HH:MM:SS</code>. When set to <b>Seconds</b>, the raw number of seconds will be
presented.</small></td>
</tr>
</tbody>
</table>
</div>
</form>#
<form action="#"><input class="form-control" id="switchRegistryPersonGUID" placeholder="your personal ID" maxlength="36" autocomplete="off" style="text-align:center;font-size:1.4em"></form>Text Content
netdata Real-time performance monitoring, done right! Welcome back!Sign in again to enjoy the benefits of Netdata Cloud Sign in odrohc2 UTC Playing 1/3/22 • 13:0113:08 • last 7min 0 0 Sign in NETDATA REAL-TIME PERFORMANCE MONITORING, IN THE GREATEST POSSIBLE DETAIL Drag charts to pan. Shift + wheel on them, to zoom in and out. Double-click on them, to reset. Hover on them too! system.cpu SYSTEM OVERVIEW Overview of the key system metrics. 42.3Used Swap% 0.00Disk ReadMiB/s 0.0Disk WriteMiB/s 8.7CPU%0.0100.0 5.0Net Inboundmegabits/s 5.8Net Outboundmegabits/s 69.8Used RAM% CPU Total CPU utilization (all cores). 100% here means there is no CPU idle time at all. You can get per core usage at the CPUs section and per application usage at the Applications Monitoring section. Keep an eye on iowait iowait (0.0%). If it is constantly high, your disks are a bottleneck and they slow your system down. An important metric worth monitoring, is softirq softirq (0.77%). A constantly high percentage of softirq may indicate network driver issues. The individual metrics can be found in the kernel documentation. Total CPU utilization (system.cpu) 0.0 20.0 40.0 60.0 80.0 100.0 13:02:00 13:02:30 13:03:00 13:03:30 13:04:00 13:04:30 13:05:00 13:05:30 13:06:00 13:06:30 13:07:00 13:07:30 13:08:00 13:08:30 softirq user system nice iowait percentage Mon, Jan 03, 2022|13:08:48 softirq0.9 user3.0 system3.6 nice1.2 iowait0.0 LOAD Current system load, i.e. the number of processes using CPU or waiting for system resources (usually CPU and disk). The 3 metrics refer to 1, 5 and 15 minute averages. The system calculates this once every 5 seconds. For more information check this wikipedia article. System Load Average (system.load) 0.50 1.00 1.50 2.00 13:02:00 13:02:30 13:03:00 13:03:30 13:04:00 13:04:30 13:05:00 13:05:30 13:06:00 13:06:30 13:07:00 13:07:30 13:08:00 13:08:30 load1 load5 load15 load Mon, Jan 03, 2022|13:08:40 load11.42 load51.03 load150.67 DISK Total Disk I/O, for all physical disks. You can get detailed information about each disk at the Disks section and per application Disk usage at the Applications Monitoring section. Physical are all the disks that are listed in /sys/block, but do not exist in /sys/devices/virtual/block. Disk I/O (system.io) -9.8 -7.8 -5.9 -3.9 -2.0 0.0 2.0 3.9 5.9 13:02:00 13:02:30 13:03:00 13:03:30 13:04:00 13:04:30 13:05:00 13:05:30 13:06:00 13:06:30 13:07:00 13:07:30 13:08:00 13:08:30 in out MiB/s Mon, Jan 03, 2022|13:08:48 in0.0 out0.0 Memory paged from/to disk. This is usually the total disk I/O of the system. system.pgpgio RAM System Random Access Memory (i.e. physical memory) usage. system.ram SWAP System swap memory usage. Swap space is used when the amount of physical memory (RAM) is full. When the system needs more memory resources and the RAM is full, inactive pages in memory are moved to the swap space (usually a disk, a disk partition or a file). system.swap System swap I/O. In - pages the system has swapped in from disk to RAM. Out - pages the system has swapped out from RAM to disk. system.swapio NETWORK Total bandwidth of all physical network interfaces. This does not include lo, VPNs, network bridges, IFB devices, bond interfaces, etc. Only the bandwidth of physical network interfaces is aggregated. Physical are all the network interfaces that are listed in /proc/net/dev, but do not exist in /sys/devices/virtual/net. system.net Total IP traffic in the system. system.ip PROCESSES System processes. Running - running or ready to run (runnable). Blocked - currently blocked, waiting for I/O to complete. system.processes The number of new processes created. system.forks The total number of processes in the system. system.active_processes Context Switches, is the switching of the CPU from one process, task or thread to another. If there are many processes or threads willing to execute and very few CPU cores available to handle them, the system is making more context switching to balance the CPU resources among them. The whole process is computationally intensive. The more the context switches, the slower the system gets. system.ctxt IDLEJITTER Idle jitter is calculated by netdata. A thread is spawned that requests to sleep for a few microseconds. When the system wakes it up, it measures how many microseconds have passed. The difference between the requested and the actual duration of the sleep, is the idle jitter. This number is useful in real-time environments, where CPU jitter can affect the quality of the service (like VoIP media gateways). system.idlejitter INTERRUPTS Interrupts are signals sent to the CPU by external devices (normally I/O devices) or programs (running processes). They tell the CPU to stop its current activities and execute the appropriate part of the operating system. Interrupt types are hardware (generated by hardware devices to signal that they need some attention from the OS), software (generated by programs when they want to request a system call to be performed by the operating system), and traps (generated by the CPU itself to indicate that some error or condition occurred for which assistance from the operating system is needed). Total number of CPU interrupts. Check system.interrupts that gives more detail about each interrupt and also the CPUs section where interrupts are analyzed per CPU core. system.intr CPU interrupts in detail. At the CPUs section, interrupts are analyzed per CPU core. The last column in /proc/interrupts provides an interrupt description or the device name that registered the handler for that interrupt. system.interrupts SOFTIRQS Software interrupts (or "softirqs") are one of the oldest deferred-execution mechanisms in the kernel. Several tasks among those executed by the kernel are not critical: they can be deferred for a long period of time, if necessary. The deferrable tasks can execute with all interrupts enabled (softirqs are patterned after hardware interrupts). Taking them out of the interrupt handler helps keep kernel response time small. Total number of software interrupts in the system. At the CPUs section, softirqs are analyzed per CPU core. HI - high priority tasklets. TIMER - tasklets related to timer interrupts. NET_TX, NET_RX - used for network transmit and receive processing. BLOCK - handles block I/O completion events. IRQ_POLL - used by the IO subsystem to increase performance (a NAPI like approach for block devices). TASKLET - handles regular tasklets. SCHED - used by the scheduler to perform load-balancing and other scheduling tasks. HRTIMER - used for high-resolution timers. RCU - performs read-copy-update (RCU) processing. system.softirqs SOFTNET Statistics for CPUs SoftIRQs related to network receive work. Break down per CPU core can be found at CPU / softnet statistics. More information about identifying and troubleshooting network driver related issues can be found at Red Hat Enterprise Linux Network Performance Tuning Guide. Processed - packets processed. Dropped - packets dropped because the network device backlog was full. Squeezed - number of times the network device budget was consumed or the time limit was reached, but more work was available. ReceivedRPS - number of times this CPU has been woken up to process packets via an Inter-processor Interrupt. FlowLimitCount - number of times the flow limit has been reached (flow limiting is an optional Receive Packet Steering feature). system.softnet_stat ENTROPY Entropy, is a pool of random numbers (/dev/random) that is mainly used in cryptography. If the pool of entropy gets empty, processes requiring random numbers may run a lot slower (it depends on the interface each program uses), waiting for the pool to be replenished. Ideally a system with high entropy demands should have a hardware device for that purpose (TPM is one such device). There are also several software-only options you may install, like haveged, although these are generally useful only in servers. system.entropy UPTIME The amount of time the system has been running, including time spent in suspend. system.uptime CLOCK SYNCHRONIZATION NTP lets you automatically sync your system time with a remote server. This keeps your machine’s time accurate by syncing with servers that are known to have accurate times. The system clock synchronization state. It is strongly recommended having the clock in sync with reliable NTP servers. Otherwise, it leads to unpredictable problems. It can take several minutes (usually up to 17) before NTP daemon selects a server to synchronize with. State map: 0 - not synchronized, 1 - synchronized. system.clock_sync_state A typical NTP client regularly polls one or more NTP servers. The client must compute its time offset and round-trip delay. Time offset is the difference in absolute time between the two clocks. system.clock_sync_offset IPC SEMAPHORES System V semaphores is an inter-process communication (IPC) mechanism. It allows processes or threads within a process to synchronize their actions. They are often used to monitor and control the availability of system resources such as shared memory segments. For details, see svipc(7). To see the host IPC semaphore information, run ipcs -us. For limits, run ipcs -ls. Number of allocated System V IPC semaphores. The system-wide limit on the number of semaphores in all semaphore sets is specified in /proc/sys/kernel/sem file (2nd field). system.ipc_semaphores Number of used System V IPC semaphore arrays (sets). Semaphores support semaphore sets where each one is a counting semaphore. So when an application requests semaphores, the kernel releases them in sets. The system-wide limit on the maximum number of semaphore sets is specified in /proc/sys/kernel/sem file (4th field). system.ipc_semaphore_arrays IPC SHARED MEMORY System V shared memory is an inter-process communication (IPC) mechanism. It allows processes to communicate information by sharing a region of memory. It is the fastest form of inter-process communication available since no kernel involvement occurs when data is passed between the processes (no copying). Typically, processes must synchronize their access to a shared memory object, using, for example, POSIX semaphores. For details, see svipc(7). To see the host IPC shared memory information, run ipcs -um. For limits, run ipcs -lm. Number of allocated System V IPC memory segments. The system-wide maximum number of shared memory segments that can be created is specified in /proc/sys/kernel/shmmni file. system.shared_memory_segments Amount of memory currently used by System V IPC memory segments. The run-time limit on the maximum shared memory segment size that can be created is specified in /proc/sys/kernel/shmmax file. system.shared_memory_bytes -------------------------------------------------------------------------------- CPUS Detailed information for each CPU of the system. A summary of the system for all CPUs can be found at the System Overview section. UTILIZATION cpu.cpu0 cpu.cpu1 cpu.cpu2 cpu.cpu3 cpu.cpu4 cpu.cpu5 cpu.cpu6 cpu.cpu7 INTERRUPTS Total number of interrupts per CPU. To see the total number for the system check the interrupts section. The last column in /proc/interrupts provides an interrupt description or the device name that registered the handler for that interrupt. cpu.cpu0_interrupts cpu.cpu1_interrupts cpu.cpu2_interrupts cpu.cpu3_interrupts cpu.cpu4_interrupts cpu.cpu5_interrupts cpu.cpu6_interrupts cpu.cpu7_interrupts SOFTIRQS Total number of software interrupts per CPU. To see the total number for the system check the softirqs section. cpu.cpu0_softirqs cpu.cpu1_softirqs cpu.cpu2_softirqs cpu.cpu3_softirqs cpu.cpu4_softirqs cpu.cpu5_softirqs cpu.cpu6_softirqs cpu.cpu7_softirqs SOFTNET Statistics for CPUs SoftIRQs related to network receive work. Total for all CPU cores can be found at System / softnet statistics. More information about identifying and troubleshooting network driver related issues can be found at Red Hat Enterprise Linux Network Performance Tuning Guide. Processed - packets processed. Dropped - packets dropped because the network device backlog was full. Squeezed - number of times the network device budget was consumed or the time limit was reached, but more work was available. ReceivedRPS - number of times this CPU has been woken up to process packets via an Inter-processor Interrupt. FlowLimitCount - number of times the flow limit has been reached (flow limiting is an optional Receive Packet Steering feature). cpu.cpu0_softnet_stat cpu.cpu1_softnet_stat cpu.cpu2_softnet_stat cpu.cpu3_softnet_stat cpu.cpu4_softnet_stat cpu.cpu5_softnet_stat cpu.cpu6_softnet_stat cpu.cpu7_softnet_stat CPUFREQ The frequency measures the number of cycles your CPU executes per second. cpu.cpufreq -------------------------------------------------------------------------------- MEMORY Detailed information about the memory management of the system. SYSTEM Available Memory is estimated by the kernel, as the amount of RAM that can be used by userspace processes, without causing swapping. mem.available The number of processes killed by Out of Memory Killer. The kernel's OOM killer is summoned when the system runs short of free memory and is unable to proceed without killing one or more processes. It tries to pick the process whose demise will free the most memory while causing the least misery for users of the system. This counter also includes processes within containers that have exceeded the memory limit. mem.oom_kill Committed Memory, is the sum of all memory which has been allocated by processes. mem.committed A page fault is a type of interrupt, called trap, raised by computer hardware when a running program accesses a memory page that is mapped into the virtual address space, but not actually loaded into main memory. Minor - the page is loaded in memory at the time the fault is generated, but is not marked in the memory management unit as being loaded in memory. Major - generated when the system needs to load the memory page from disk or swap memory. mem.pgfaults KERNEL Dirty is the amount of memory waiting to be written to disk. Writeback is how much memory is actively being written to disk. mem.writeback The total amount of memory being used by the kernel. Slab - used by the kernel to cache data structures for its own use. KernelStack - allocated for each task done by the kernel. PageTables - dedicated to the lowest level of page tables (A page table is used to turn a virtual address into a physical memory address). VmallocUsed - being used as virtual address space. Percpu - allocated to the per-CPU allocator used to back per-CPU allocations (excludes the cost of metadata). When you create a per-CPU variable, each processor on the system gets its own copy of that variable. mem.kernel SLAB Slab memory statistics. Reclaimable - amount of memory which the kernel can reuse. Unreclaimable - can not be reused even when the kernel is lacking memory. mem.slab -------------------------------------------------------------------------------- DISKS Charts with performance information for all the system disks. Special care has been given to present disk performance metrics in a way compatible with iostat -x. netdata by default prevents rendering performance charts for individual partitions and unmounted virtual disks. Disabled charts can still be enabled by configuring the relative settings in the netdata configuration file. MMCBLK1 disk.mmcblk1 disk.mmcblk1 disk_util.mmcblk1 The amount of data transferred to and from disk. disk.mmcblk1 The amount of discarded data that are no longer in use by a mounted file system. disk_ext.mmcblk1 Completed disk I/O operations. Keep in mind the number of operations requested might be higher, since the system is able to merge adjacent to each other (see merged operations chart). disk_ops.mmcblk1 The number (after merges) of completed discard/flush requests. Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. Discarding/trimming enables the SSD to handle garbage collection more efficiently, which would otherwise slow future write operations to the involved blocks down. Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device so that all changed information can be retrieved even if the system crashes or is rebooted. Flush requests are executed by disks. Flush requests are not tracked for partitions. Before being merged, flush... The number (after merges) of completed discard/flush requests. Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. Discarding/trimming enables the SSD to handle garbage collection more efficiently, which would otherwise slow future write operations to the involved blocks down. Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device so that all changed information can be retrieved even if the system crashes or is rebooted. Flush requests are executed by disks. Flush requests are not tracked for partitions. Before being merged, flush operations are counted as writes. show more information disk_ext_ops.mmcblk1 I/O operations currently in progress. This metric is a snapshot - it is not an average over the last interval. disk_qops.mmcblk1 Backlog is an indication of the duration of pending disk operations. On every I/O event the system is multiplying the time spent doing I/O since the last update of this field with the number of pending operations. While not accurate, this metric can provide an indication of the expected completion time of the operations in progress. disk_backlog.mmcblk1 Disk Busy Time measures the amount of time the disk was busy with something. disk_busy.mmcblk1 Disk Utilization measures the amount of time the disk was busy with something. This is not related to its performance. 100% means that the system always had an outstanding operation on the disk. Keep in mind that depending on the underlying technology of the disk, 100% here may or may not be an indication of congestion. disk_util.mmcblk1 The average time for I/O requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_await.mmcblk1 The average time for discard/flush requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_ext_await.mmcblk1 The average I/O operation size. disk_avgsz.mmcblk1 The average discard operation size. disk_ext_avgsz.mmcblk1 The average service time for completed I/O operations. This metric is calculated using the total busy time of the disk and the number of completed operations. If the disk is able to execute multiple parallel operations the reporting average service time will be misleading. disk_svctm.mmcblk1 The number of merged disk operations. The system is able to merge adjacent I/O operations, for example two 4KB reads can become one 8KB read before given to disk. disk_mops.mmcblk1 The number of merged discard disk operations. Discard operations which are adjacent to each other may be merged for efficiency. disk_ext_mops.mmcblk1 The sum of the duration of all completed I/O operations. This number can exceed the interval if the disk is able to execute I/O operations in parallel. disk_iotime.mmcblk1 The sum of the duration of all completed discard/flush operations. This number can exceed the interval if the disk is able to execute discard/flush operations in parallel. disk_ext_iotime.mmcblk1 SDB disk.sdb disk.sdb disk_util.sdb The amount of data transferred to and from disk. disk.sdb The amount of discarded data that are no longer in use by a mounted file system. disk_ext.sdb Completed disk I/O operations. Keep in mind the number of operations requested might be higher, since the system is able to merge adjacent to each other (see merged operations chart). disk_ops.sdb The number (after merges) of completed discard/flush requests. Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. Discarding/trimming enables the SSD to handle garbage collection more efficiently, which would otherwise slow future write operations to the involved blocks down. Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device so that all changed information can be retrieved even if the system crashes or is rebooted. Flush requests are executed by disks. Flush requests are not tracked for partitions. Before being merged, flush... The number (after merges) of completed discard/flush requests. Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. Discarding/trimming enables the SSD to handle garbage collection more efficiently, which would otherwise slow future write operations to the involved blocks down. Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device so that all changed information can be retrieved even if the system crashes or is rebooted. Flush requests are executed by disks. Flush requests are not tracked for partitions. Before being merged, flush operations are counted as writes. show more information disk_ext_ops.sdb I/O operations currently in progress. This metric is a snapshot - it is not an average over the last interval. disk_qops.sdb Backlog is an indication of the duration of pending disk operations. On every I/O event the system is multiplying the time spent doing I/O since the last update of this field with the number of pending operations. While not accurate, this metric can provide an indication of the expected completion time of the operations in progress. disk_backlog.sdb Disk Busy Time measures the amount of time the disk was busy with something. disk_busy.sdb Disk Utilization measures the amount of time the disk was busy with something. This is not related to its performance. 100% means that the system always had an outstanding operation on the disk. Keep in mind that depending on the underlying technology of the disk, 100% here may or may not be an indication of congestion. disk_util.sdb The average time for I/O requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_await.sdb The average time for discard/flush requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_ext_await.sdb The average I/O operation size. disk_avgsz.sdb The average discard operation size. disk_ext_avgsz.sdb The average service time for completed I/O operations. This metric is calculated using the total busy time of the disk and the number of completed operations. If the disk is able to execute multiple parallel operations the reporting average service time will be misleading. disk_svctm.sdb The number of merged disk operations. The system is able to merge adjacent I/O operations, for example two 4KB reads can become one 8KB read before given to disk. disk_mops.sdb The number of merged discard disk operations. Discard operations which are adjacent to each other may be merged for efficiency. disk_ext_mops.sdb The sum of the duration of all completed I/O operations. This number can exceed the interval if the disk is able to execute I/O operations in parallel. disk_iotime.sdb The sum of the duration of all completed discard/flush operations. This number can exceed the interval if the disk is able to execute discard/flush operations in parallel. disk_ext_iotime.sdb ZRAM0 disk.zram0 disk.zram0 disk_util.zram0 The amount of data transferred to and from disk. disk.zram0 The amount of discarded data that are no longer in use by a mounted file system. disk_ext.zram0 Completed disk I/O operations. Keep in mind the number of operations requested might be higher, since the system is able to merge adjacent to each other (see merged operations chart). disk_ops.zram0 The number (after merges) of completed discard/flush requests. Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. Discarding/trimming enables the SSD to handle garbage collection more efficiently, which would otherwise slow future write operations to the involved blocks down. Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device so that all changed information can be retrieved even if the system crashes or is rebooted. Flush requests are executed by disks. Flush requests are not tracked for partitions. Before being merged, flush... The number (after merges) of completed discard/flush requests. Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. Discarding/trimming enables the SSD to handle garbage collection more efficiently, which would otherwise slow future write operations to the involved blocks down. Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device so that all changed information can be retrieved even if the system crashes or is rebooted. Flush requests are executed by disks. Flush requests are not tracked for partitions. Before being merged, flush operations are counted as writes. show more information disk_ext_ops.zram0 I/O operations currently in progress. This metric is a snapshot - it is not an average over the last interval. disk_qops.zram0 Backlog is an indication of the duration of pending disk operations. On every I/O event the system is multiplying the time spent doing I/O since the last update of this field with the number of pending operations. While not accurate, this metric can provide an indication of the expected completion time of the operations in progress. disk_backlog.zram0 Disk Busy Time measures the amount of time the disk was busy with something. disk_busy.zram0 Disk Utilization measures the amount of time the disk was busy with something. This is not related to its performance. 100% means that the system always had an outstanding operation on the disk. Keep in mind that depending on the underlying technology of the disk, 100% here may or may not be an indication of congestion. disk_util.zram0 The average time for I/O requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_await.zram0 The average time for discard/flush requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_ext_await.zram0 The average I/O operation size. disk_avgsz.zram0 The average discard operation size. disk_ext_avgsz.zram0 The average service time for completed I/O operations. This metric is calculated using the total busy time of the disk and the number of completed operations. If the disk is able to execute multiple parallel operations the reporting average service time will be misleading. disk_svctm.zram0 The sum of the duration of all completed I/O operations. This number can exceed the interval if the disk is able to execute I/O operations in parallel. disk_iotime.zram0 The sum of the duration of all completed discard/flush operations. This number can exceed the interval if the disk is able to execute discard/flush operations in parallel. disk_ext_iotime.zram0 ZRAM1 disk.zram1 disk.zram1 disk_util.zram1 The amount of data transferred to and from disk. disk.zram1 The amount of discarded data that are no longer in use by a mounted file system. disk_ext.zram1 Completed disk I/O operations. Keep in mind the number of operations requested might be higher, since the system is able to merge adjacent to each other (see merged operations chart). disk_ops.zram1 The number (after merges) of completed discard/flush requests. Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. Discarding/trimming enables the SSD to handle garbage collection more efficiently, which would otherwise slow future write operations to the involved blocks down. Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device so that all changed information can be retrieved even if the system crashes or is rebooted. Flush requests are executed by disks. Flush requests are not tracked for partitions. Before being merged, flush... The number (after merges) of completed discard/flush requests. Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. Discarding/trimming enables the SSD to handle garbage collection more efficiently, which would otherwise slow future write operations to the involved blocks down. Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device so that all changed information can be retrieved even if the system crashes or is rebooted. Flush requests are executed by disks. Flush requests are not tracked for partitions. Before being merged, flush operations are counted as writes. show more information disk_ext_ops.zram1 I/O operations currently in progress. This metric is a snapshot - it is not an average over the last interval. disk_qops.zram1 Backlog is an indication of the duration of pending disk operations. On every I/O event the system is multiplying the time spent doing I/O since the last update of this field with the number of pending operations. While not accurate, this metric can provide an indication of the expected completion time of the operations in progress. disk_backlog.zram1 Disk Busy Time measures the amount of time the disk was busy with something. disk_busy.zram1 Disk Utilization measures the amount of time the disk was busy with something. This is not related to its performance. 100% means that the system always had an outstanding operation on the disk. Keep in mind that depending on the underlying technology of the disk, 100% here may or may not be an indication of congestion. disk_util.zram1 The average time for I/O requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_await.zram1 The average time for discard/flush requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_ext_await.zram1 The average I/O operation size. disk_avgsz.zram1 The average discard operation size. disk_ext_avgsz.zram1 The average service time for completed I/O operations. This metric is calculated using the total busy time of the disk and the number of completed operations. If the disk is able to execute multiple parallel operations the reporting average service time will be misleading. disk_svctm.zram1 The sum of the duration of all completed I/O operations. This number can exceed the interval if the disk is able to execute I/O operations in parallel. disk_iotime.zram1 The sum of the duration of all completed discard/flush operations. This number can exceed the interval if the disk is able to execute discard/flush operations in parallel. disk_ext_iotime.zram1 ZRAM2 disk.zram2 disk.zram2 disk_util.zram2 The amount of data transferred to and from disk. disk.zram2 The amount of discarded data that are no longer in use by a mounted file system. disk_ext.zram2 Completed disk I/O operations. Keep in mind the number of operations requested might be higher, since the system is able to merge adjacent to each other (see merged operations chart). disk_ops.zram2 The number (after merges) of completed discard/flush requests. Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. Discarding/trimming enables the SSD to handle garbage collection more efficiently, which would otherwise slow future write operations to the involved blocks down. Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device so that all changed information can be retrieved even if the system crashes or is rebooted. Flush requests are executed by disks. Flush requests are not tracked for partitions. Before being merged, flush... The number (after merges) of completed discard/flush requests. Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. Discarding/trimming enables the SSD to handle garbage collection more efficiently, which would otherwise slow future write operations to the involved blocks down. Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device so that all changed information can be retrieved even if the system crashes or is rebooted. Flush requests are executed by disks. Flush requests are not tracked for partitions. Before being merged, flush operations are counted as writes. show more information disk_ext_ops.zram2 I/O operations currently in progress. This metric is a snapshot - it is not an average over the last interval. disk_qops.zram2 Backlog is an indication of the duration of pending disk operations. On every I/O event the system is multiplying the time spent doing I/O since the last update of this field with the number of pending operations. While not accurate, this metric can provide an indication of the expected completion time of the operations in progress. disk_backlog.zram2 Disk Busy Time measures the amount of time the disk was busy with something. disk_busy.zram2 Disk Utilization measures the amount of time the disk was busy with something. This is not related to its performance. 100% means that the system always had an outstanding operation on the disk. Keep in mind that depending on the underlying technology of the disk, 100% here may or may not be an indication of congestion. disk_util.zram2 The average time for I/O requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_await.zram2 The average time for discard/flush requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_ext_await.zram2 The average I/O operation size. disk_avgsz.zram2 The average discard operation size. disk_ext_avgsz.zram2 The average service time for completed I/O operations. This metric is calculated using the total busy time of the disk and the number of completed operations. If the disk is able to execute multiple parallel operations the reporting average service time will be misleading. disk_svctm.zram2 The sum of the duration of all completed I/O operations. This number can exceed the interval if the disk is able to execute I/O operations in parallel. disk_iotime.zram2 The sum of the duration of all completed discard/flush operations. This number can exceed the interval if the disk is able to execute discard/flush operations in parallel. disk_ext_iotime.zram2 ZRAM3 disk.zram3 disk.zram3 disk_util.zram3 The amount of data transferred to and from disk. disk.zram3 The amount of discarded data that are no longer in use by a mounted file system. disk_ext.zram3 Completed disk I/O operations. Keep in mind the number of operations requested might be higher, since the system is able to merge adjacent to each other (see merged operations chart). disk_ops.zram3 The number (after merges) of completed discard/flush requests. Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. Discarding/trimming enables the SSD to handle garbage collection more efficiently, which would otherwise slow future write operations to the involved blocks down. Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device so that all changed information can be retrieved even if the system crashes or is rebooted. Flush requests are executed by disks. Flush requests are not tracked for partitions. Before being merged, flush... The number (after merges) of completed discard/flush requests. Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. Discarding/trimming enables the SSD to handle garbage collection more efficiently, which would otherwise slow future write operations to the involved blocks down. Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device so that all changed information can be retrieved even if the system crashes or is rebooted. Flush requests are executed by disks. Flush requests are not tracked for partitions. Before being merged, flush operations are counted as writes. show more information disk_ext_ops.zram3 Backlog is an indication of the duration of pending disk operations. On every I/O event the system is multiplying the time spent doing I/O since the last update of this field with the number of pending operations. While not accurate, this metric can provide an indication of the expected completion time of the operations in progress. disk_backlog.zram3 Disk Busy Time measures the amount of time the disk was busy with something. disk_busy.zram3 Disk Utilization measures the amount of time the disk was busy with something. This is not related to its performance. 100% means that the system always had an outstanding operation on the disk. Keep in mind that depending on the underlying technology of the disk, 100% here may or may not be an indication of congestion. disk_util.zram3 The average time for I/O requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_await.zram3 The average time for discard/flush requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_ext_await.zram3 The average I/O operation size. disk_avgsz.zram3 The average discard operation size. disk_ext_avgsz.zram3 The average service time for completed I/O operations. This metric is calculated using the total busy time of the disk and the number of completed operations. If the disk is able to execute multiple parallel operations the reporting average service time will be misleading. disk_svctm.zram3 The sum of the duration of all completed I/O operations. This number can exceed the interval if the disk is able to execute I/O operations in parallel. disk_iotime.zram3 The sum of the duration of all completed discard/flush operations. This number can exceed the interval if the disk is able to execute discard/flush operations in parallel. disk_ext_iotime.zram3 ZRAM4 disk.zram4 disk.zram4 disk_util.zram4 The amount of data transferred to and from disk. disk.zram4 The amount of discarded data that are no longer in use by a mounted file system. disk_ext.zram4 Completed disk I/O operations. Keep in mind the number of operations requested might be higher, since the system is able to merge adjacent to each other (see merged operations chart). disk_ops.zram4 The number (after merges) of completed discard/flush requests. Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. Discarding/trimming enables the SSD to handle garbage collection more efficiently, which would otherwise slow future write operations to the involved blocks down. Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device so that all changed information can be retrieved even if the system crashes or is rebooted. Flush requests are executed by disks. Flush requests are not tracked for partitions. Before being merged, flush... The number (after merges) of completed discard/flush requests. Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. Discarding/trimming enables the SSD to handle garbage collection more efficiently, which would otherwise slow future write operations to the involved blocks down. Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device so that all changed information can be retrieved even if the system crashes or is rebooted. Flush requests are executed by disks. Flush requests are not tracked for partitions. Before being merged, flush operations are counted as writes. show more information disk_ext_ops.zram4 Backlog is an indication of the duration of pending disk operations. On every I/O event the system is multiplying the time spent doing I/O since the last update of this field with the number of pending operations. While not accurate, this metric can provide an indication of the expected completion time of the operations in progress. disk_backlog.zram4 Disk Busy Time measures the amount of time the disk was busy with something. disk_busy.zram4 Disk Utilization measures the amount of time the disk was busy with something. This is not related to its performance. 100% means that the system always had an outstanding operation on the disk. Keep in mind that depending on the underlying technology of the disk, 100% here may or may not be an indication of congestion. disk_util.zram4 The average time for I/O requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_await.zram4 The average time for discard/flush requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_ext_await.zram4 The average I/O operation size. disk_avgsz.zram4 The average discard operation size. disk_ext_avgsz.zram4 The average service time for completed I/O operations. This metric is calculated using the total busy time of the disk and the number of completed operations. If the disk is able to execute multiple parallel operations the reporting average service time will be misleading. disk_svctm.zram4 The sum of the duration of all completed I/O operations. This number can exceed the interval if the disk is able to execute I/O operations in parallel. disk_iotime.zram4 The sum of the duration of all completed discard/flush operations. This number can exceed the interval if the disk is able to execute discard/flush operations in parallel. disk_ext_iotime.zram4 ZRAM5 disk.zram5 disk.zram5 disk_util.zram5 The amount of data transferred to and from disk. disk.zram5 The amount of discarded data that are no longer in use by a mounted file system. disk_ext.zram5 Completed disk I/O operations. Keep in mind the number of operations requested might be higher, since the system is able to merge adjacent to each other (see merged operations chart). disk_ops.zram5 The number (after merges) of completed discard/flush requests. Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. Discarding/trimming enables the SSD to handle garbage collection more efficiently, which would otherwise slow future write operations to the involved blocks down. Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device so that all changed information can be retrieved even if the system crashes or is rebooted. Flush requests are executed by disks. Flush requests are not tracked for partitions. Before being merged, flush... The number (after merges) of completed discard/flush requests. Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. Discarding/trimming enables the SSD to handle garbage collection more efficiently, which would otherwise slow future write operations to the involved blocks down. Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device so that all changed information can be retrieved even if the system crashes or is rebooted. Flush requests are executed by disks. Flush requests are not tracked for partitions. Before being merged, flush operations are counted as writes. show more information disk_ext_ops.zram5 I/O operations currently in progress. This metric is a snapshot - it is not an average over the last interval. disk_qops.zram5 Backlog is an indication of the duration of pending disk operations. On every I/O event the system is multiplying the time spent doing I/O since the last update of this field with the number of pending operations. While not accurate, this metric can provide an indication of the expected completion time of the operations in progress. disk_backlog.zram5 Disk Busy Time measures the amount of time the disk was busy with something. disk_busy.zram5 Disk Utilization measures the amount of time the disk was busy with something. This is not related to its performance. 100% means that the system always had an outstanding operation on the disk. Keep in mind that depending on the underlying technology of the disk, 100% here may or may not be an indication of congestion. disk_util.zram5 The average time for I/O requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_await.zram5 The average time for discard/flush requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_ext_await.zram5 The average I/O operation size. disk_avgsz.zram5 The average discard operation size. disk_ext_avgsz.zram5 The average service time for completed I/O operations. This metric is calculated using the total busy time of the disk and the number of completed operations. If the disk is able to execute multiple parallel operations the reporting average service time will be misleading. disk_svctm.zram5 The sum of the duration of all completed I/O operations. This number can exceed the interval if the disk is able to execute I/O operations in parallel. disk_iotime.zram5 The sum of the duration of all completed discard/flush operations. This number can exceed the interval if the disk is able to execute discard/flush operations in parallel. disk_ext_iotime.zram5 ZRAM6 disk.zram6 disk.zram6 disk_util.zram6 The amount of data transferred to and from disk. disk.zram6 The amount of discarded data that are no longer in use by a mounted file system. disk_ext.zram6 Completed disk I/O operations. Keep in mind the number of operations requested might be higher, since the system is able to merge adjacent to each other (see merged operations chart). disk_ops.zram6 The number (after merges) of completed discard/flush requests. Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. Discarding/trimming enables the SSD to handle garbage collection more efficiently, which would otherwise slow future write operations to the involved blocks down. Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device so that all changed information can be retrieved even if the system crashes or is rebooted. Flush requests are executed by disks. Flush requests are not tracked for partitions. Before being merged, flush... The number (after merges) of completed discard/flush requests. Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. Discarding/trimming enables the SSD to handle garbage collection more efficiently, which would otherwise slow future write operations to the involved blocks down. Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device so that all changed information can be retrieved even if the system crashes or is rebooted. Flush requests are executed by disks. Flush requests are not tracked for partitions. Before being merged, flush operations are counted as writes. show more information disk_ext_ops.zram6 Backlog is an indication of the duration of pending disk operations. On every I/O event the system is multiplying the time spent doing I/O since the last update of this field with the number of pending operations. While not accurate, this metric can provide an indication of the expected completion time of the operations in progress. disk_backlog.zram6 Disk Busy Time measures the amount of time the disk was busy with something. disk_busy.zram6 Disk Utilization measures the amount of time the disk was busy with something. This is not related to its performance. 100% means that the system always had an outstanding operation on the disk. Keep in mind that depending on the underlying technology of the disk, 100% here may or may not be an indication of congestion. disk_util.zram6 The average time for I/O requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_await.zram6 The average time for discard/flush requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_ext_await.zram6 The average I/O operation size. disk_avgsz.zram6 The average discard operation size. disk_ext_avgsz.zram6 The average service time for completed I/O operations. This metric is calculated using the total busy time of the disk and the number of completed operations. If the disk is able to execute multiple parallel operations the reporting average service time will be misleading. disk_svctm.zram6 The sum of the duration of all completed I/O operations. This number can exceed the interval if the disk is able to execute I/O operations in parallel. disk_iotime.zram6 The sum of the duration of all completed discard/flush operations. This number can exceed the interval if the disk is able to execute discard/flush operations in parallel. disk_ext_iotime.zram6 ZRAM7 disk.zram7 disk.zram7 disk_util.zram7 The amount of data transferred to and from disk. disk.zram7 The amount of discarded data that are no longer in use by a mounted file system. disk_ext.zram7 Completed disk I/O operations. Keep in mind the number of operations requested might be higher, since the system is able to merge adjacent to each other (see merged operations chart). disk_ops.zram7 The number (after merges) of completed discard/flush requests. Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. Discarding/trimming enables the SSD to handle garbage collection more efficiently, which would otherwise slow future write operations to the involved blocks down. Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device so that all changed information can be retrieved even if the system crashes or is rebooted. Flush requests are executed by disks. Flush requests are not tracked for partitions. Before being merged, flush... The number (after merges) of completed discard/flush requests. Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. Discarding/trimming enables the SSD to handle garbage collection more efficiently, which would otherwise slow future write operations to the involved blocks down. Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device so that all changed information can be retrieved even if the system crashes or is rebooted. Flush requests are executed by disks. Flush requests are not tracked for partitions. Before being merged, flush operations are counted as writes. show more information disk_ext_ops.zram7 I/O operations currently in progress. This metric is a snapshot - it is not an average over the last interval. disk_qops.zram7 Backlog is an indication of the duration of pending disk operations. On every I/O event the system is multiplying the time spent doing I/O since the last update of this field with the number of pending operations. While not accurate, this metric can provide an indication of the expected completion time of the operations in progress. disk_backlog.zram7 Disk Busy Time measures the amount of time the disk was busy with something. disk_busy.zram7 Disk Utilization measures the amount of time the disk was busy with something. This is not related to its performance. 100% means that the system always had an outstanding operation on the disk. Keep in mind that depending on the underlying technology of the disk, 100% here may or may not be an indication of congestion. disk_util.zram7 The average time for I/O requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_await.zram7 The average time for discard/flush requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_ext_await.zram7 The average I/O operation size. disk_avgsz.zram7 The average discard operation size. disk_ext_avgsz.zram7 The average service time for completed I/O operations. This metric is calculated using the total busy time of the disk and the number of completed operations. If the disk is able to execute multiple parallel operations the reporting average service time will be misleading. disk_svctm.zram7 The sum of the duration of all completed I/O operations. This number can exceed the interval if the disk is able to execute I/O operations in parallel. disk_iotime.zram7 The sum of the duration of all completed discard/flush operations. This number can exceed the interval if the disk is able to execute discard/flush operations in parallel. disk_ext_iotime.zram7 SDA The amount of discarded data that are no longer in use by a mounted file system. disk_ext.sda The number (after merges) of completed discard/flush requests. Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. Discarding/trimming enables the SSD to handle garbage collection more efficiently, which would otherwise slow future write operations to the involved blocks down. Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device so that all changed information can be retrieved even if the system crashes or is rebooted. Flush requests are executed by disks. Flush requests are not tracked for partitions. Before being merged, flush... The number (after merges) of completed discard/flush requests. Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. Discarding/trimming enables the SSD to handle garbage collection more efficiently, which would otherwise slow future write operations to the involved blocks down. Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device so that all changed information can be retrieved even if the system crashes or is rebooted. Flush requests are executed by disks. Flush requests are not tracked for partitions. Before being merged, flush operations are counted as writes. show more information disk_ext_ops.sda Disk Busy Time measures the amount of time the disk was busy with something. disk_busy.sda The average time for discard/flush requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_ext_await.sda The average discard operation size. disk_ext_avgsz.sda The number of merged discard disk operations. Discard operations which are adjacent to each other may be merged for efficiency. disk_ext_mops.sda The sum of the duration of all completed discard/flush operations. This number can exceed the interval if the disk is able to execute discard/flush operations in parallel. disk_ext_iotime.sda / Disk space utilization. reserved for root is automatically reserved by the system to prevent the root user from getting out of space. disk_space._ Inodes (or index nodes) are filesystem objects (e.g. files and directories). On many types of file system implementations, the maximum number of inodes is fixed at filesystem creation, limiting the maximum number of files the filesystem can hold. It is possible for a device to run out of inodes. When this happens, new files cannot be created on the device, even though there may be free space available. disk_inodes._ /DEV Disk space utilization. reserved for root is automatically reserved by the system to prevent the root user from getting out of space. disk_space._dev Inodes (or index nodes) are filesystem objects (e.g. files and directories). On many types of file system implementations, the maximum number of inodes is fixed at filesystem creation, limiting the maximum number of files the filesystem can hold. It is possible for a device to run out of inodes. When this happens, new files cannot be created on the device, even though there may be free space available. disk_inodes._dev /DEV/SHM Disk space utilization. reserved for root is automatically reserved by the system to prevent the root user from getting out of space. disk_space._dev_shm Inodes (or index nodes) are filesystem objects (e.g. files and directories). On many types of file system implementations, the maximum number of inodes is fixed at filesystem creation, limiting the maximum number of files the filesystem can hold. It is possible for a device to run out of inodes. When this happens, new files cannot be created on the device, even though there may be free space available. disk_inodes._dev_shm /ETC/NETDATA Disk space utilization. reserved for root is automatically reserved by the system to prevent the root user from getting out of space. disk_space._etc_netdata Inodes (or index nodes) are filesystem objects (e.g. files and directories). On many types of file system implementations, the maximum number of inodes is fixed at filesystem creation, limiting the maximum number of files the filesystem can hold. It is possible for a device to run out of inodes. When this happens, new files cannot be created on the device, even though there may be free space available. disk_inodes._etc_netdata /VAR/CACHE/NETDATA Disk space utilization. reserved for root is automatically reserved by the system to prevent the root user from getting out of space. disk_space._var_cache_netdata Inodes (or index nodes) are filesystem objects (e.g. files and directories). On many types of file system implementations, the maximum number of inodes is fixed at filesystem creation, limiting the maximum number of files the filesystem can hold. It is possible for a device to run out of inodes. When this happens, new files cannot be created on the device, even though there may be free space available. disk_inodes._var_cache_netdata /VAR/LIB/NETDATA Disk space utilization. reserved for root is automatically reserved by the system to prevent the root user from getting out of space. disk_space._var_lib_netdata Inodes (or index nodes) are filesystem objects (e.g. files and directories). On many types of file system implementations, the maximum number of inodes is fixed at filesystem creation, limiting the maximum number of files the filesystem can hold. It is possible for a device to run out of inodes. When this happens, new files cannot be created on the device, even though there may be free space available. disk_inodes._var_lib_netdata -------------------------------------------------------------------------------- NETWORKING STACK Metrics for the networking stack of the system. These metrics are collected from /proc/net/netstat or attaching kprobes to kernel functions, apply to both IPv4 and IPv6 traffic and are related to operation of the kernel networking stack. TCP TCP maintains an out-of-order queue to keep the out-of-order packets in the TCP communication. InQueue - the TCP layer receives an out-of-order packet and has enough memory to queue it. Dropped - the TCP layer receives an out-of-order packet but does not have enough memory, so drops it. Merged - the received out-of-order packet has an overlay with the previous packet. The overlay part will be dropped. All these packets will also be counted into InQueue. Pruned - packets dropped from out-of-order queue because of socket buffer overrun. ip.tcpofo BROADCAST In computer networking, broadcasting refers to transmitting a packet that will be received by every device on the network. In practice, the scope of the broadcast is limited to a broadcast domain. Total broadcast traffic in the system. ip.bcast Total transferred broadcast packets in the system. ip.bcastpkts ECN Explicit Congestion Notification (ECN) is an extension to the IP and to the TCP that allows end-to-end notification of network congestion without dropping packets. ECN is an optional feature that may be used between two ECN-enabled endpoints when the underlying network infrastructure also supports it. Total number of received IP packets with ECN bits set in the system. CEP - congestion encountered. NoECTP - non ECN-capable transport. ECTP0 and ECTP1 - ECN capable transport. ip.ecnpkts -------------------------------------------------------------------------------- IPV4 NETWORKING Metrics for the IPv4 stack of the system. Internet Protocol version 4 (IPv4) is the fourth version of the Internet Protocol (IP). It is one of the core protocols of standards-based internetworking methods in the Internet. IPv4 is a connectionless protocol for use on packet-switched networks. It operates on a best effort delivery model, in that it does not guarantee delivery, nor does it assure proper sequencing or avoidance of duplicate delivery. These aspects, including data integrity, are addressed by an upper layer transport protocol, such as the Transmission Control Protocol (TCP). SOCKETS The total number of used sockets for all address families in this system. ipv4.sockstat_sockets PACKETS IPv4 packets statistics for this host. Received - packets received by the IP layer. This counter will be increased even if the packet is dropped later. Sent - packets sent via IP layer, for both single cast and multicast packets. This counter does not include any packets counted in Forwarded. Forwarded - input packets for which this host was not their final IP destination, as a result of which an attempt was made to find a route to forward them to that final destination. In hosts which do not act as IP Gateways, this counter will include only those packets which were Source-Routed and the Source-Route option processing was successful. Delivered - packets delivered to the upper layer protocols, e.g. TCP, UDP, ICMP, and so on. ipv4.packets ICMP The number of transferred IPv4 ICMP messages. Received, Sent - ICMP messages which the host received and attempted to send. Both these counters include errors. ipv4.icmp The number of IPv4 ICMP errors. InErrors - received ICMP messages but determined as having ICMP-specific errors, e.g. bad ICMP checksums, bad length, etc. OutErrors - ICMP messages which this host did not send due to problems discovered within ICMP such as a lack of buffers. This counter does not include errors discovered outside the ICMP layer such as the inability of IP to route the resultant datagram. InCsumErrors - received ICMP messages with bad checksum. ipv4.icmp_errors The number of transferred IPv4 ICMP control messages. ipv4.icmpmsg TCP The number of TCP connections for which the current state is either ESTABLISHED or CLOSE-WAIT. This is a snapshot of the established connections at the time of measurement (i.e. a connection established and a connection disconnected within the same iteration will not affect this metric). ipv4.tcpsock The number of TCP sockets in the system in certain states. Alloc - in any TCP state. Orphan - no longer attached to a socket descriptor in any user processes, but for which the kernel is still required to maintain state in order to complete the transport protocol. InUse - in any TCP state, excluding TIME-WAIT and CLOSED. TimeWait - in the TIME-WAIT state. ipv4.sockstat_tcp_sockets The number of packets transferred by the TCP layer. Received - received packets, including those received in error, such as checksum error, invalid TCP header, and so on. Sent - sent packets, excluding the retransmitted packets. But it includes the SYN, ACK, and RST packets. ipv4.tcppackets TCP connection statistics. Active - number of outgoing TCP connections attempted by this host. Passive - number of incoming TCP connections accepted by this host. ipv4.tcpopens TCP handshake statistics. EstabResets - established connections resets (i.e. connections that made a direct transition from ESTABLISHED or CLOSE_WAIT to CLOSED). OutRsts - TCP segments sent, with the RST flag set (for both IPv4 and IPv6). AttemptFails - number of times TCP connections made a direct transition from either SYN_SENT or SYN_RECV to CLOSED, plus the number of times TCP connections made a direct transition from the SYN_RECV to LISTEN. SynRetrans - shows retries for new outbound TCP connections, which can indicate general connectivity issues or backlog on the remote host. ipv4.tcphandshake The amount of memory used by allocated TCP sockets. ipv4.sockstat_tcp_mem UDP The number of used UDP sockets. ipv4.sockstat_udp_sockets The number of transferred UDP packets. ipv4.udppackets The number of errors encountered during transferring UDP packets. RcvbufErrors - receive buffer is full. SndbufErrors - send buffer is full, no kernel memory available, or the IP layer reported an error when trying to send the packet and no error queue has been setup. InErrors - that is an aggregated counter for all errors, excluding NoPorts. NoPorts - no application is listening at the destination port. InCsumErrors - a UDP checksum failure is detected. IgnoredMulti - ignored multicast packets. ipv4.udperrors The amount of memory used by allocated UDP sockets. ipv4.sockstat_udp_mem -------------------------------------------------------------------------------- IPV6 NETWORKING Metrics for the IPv6 stack of the system. Internet Protocol version 6 (IPv6) is the most recent version of the Internet Protocol (IP), the communications protocol that provides an identification and location system for computers on networks and routes traffic across the Internet. IPv6 was developed by the Internet Engineering Task Force (IETF) to deal with the long-anticipated problem of IPv4 address exhaustion. IPv6 is intended to replace IPv4. TCP6 The number of TCP sockets in any state, excluding TIME-WAIT and CLOSED. ipv6.sockstat6_tcp_sockets -------------------------------------------------------------------------------- NETWORK INTERFACES Performance metrics for network interfaces. Netdata retrieves this data reading the /proc/net/dev file and /sys/class/net/ directory. BR-09BADF13F34D net.br-09badf13f34d net.br-09badf13f34d The amount of traffic transferred by the network interface. net.br-09badf13f34d The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.br-09badf13f34d The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.br-09badf13f34d The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.br-09badf13f34d The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.br-09badf13f34d BR-5B55B4414204 net.br-5b55b4414204 net.br-5b55b4414204 The amount of traffic transferred by the network interface. net.br-5b55b4414204 The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.br-5b55b4414204 The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.br-5b55b4414204 The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.br-5b55b4414204 The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.br-5b55b4414204 BR-77C3E60744DC net.br-77c3e60744dc net.br-77c3e60744dc The amount of traffic transferred by the network interface. net.br-77c3e60744dc The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.br-77c3e60744dc The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.br-77c3e60744dc The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.br-77c3e60744dc The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.br-77c3e60744dc BR-99FCFB471D7C net.br-99fcfb471d7c net.br-99fcfb471d7c The amount of traffic transferred by the network interface. net.br-99fcfb471d7c The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.br-99fcfb471d7c The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.br-99fcfb471d7c The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.br-99fcfb471d7c The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.br-99fcfb471d7c BR-35501A5EFC3F net.br-35501a5efc3f net.br-35501a5efc3f The amount of traffic transferred by the network interface. net.br-35501a5efc3f The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.br-35501a5efc3f The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.br-35501a5efc3f The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.br-35501a5efc3f The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.br-35501a5efc3f BR-A30AEA43C2E1 net.br-a30aea43c2e1 net.br-a30aea43c2e1 The amount of traffic transferred by the network interface. net.br-a30aea43c2e1 The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.br-a30aea43c2e1 The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.br-a30aea43c2e1 The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.br-a30aea43c2e1 The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.br-a30aea43c2e1 BR-B8C09B3AC6DB net.br-b8c09b3ac6db net.br-b8c09b3ac6db The amount of traffic transferred by the network interface. net.br-b8c09b3ac6db The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.br-b8c09b3ac6db The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.br-b8c09b3ac6db The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.br-b8c09b3ac6db The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.br-b8c09b3ac6db BR-D3119AD3368C net.br-d3119ad3368c net.br-d3119ad3368c The amount of traffic transferred by the network interface. net.br-d3119ad3368c The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.br-d3119ad3368c The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.br-d3119ad3368c The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.br-d3119ad3368c The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.br-d3119ad3368c BR-E0B9521F4FD3 net.br-e0b9521f4fd3 net.br-e0b9521f4fd3 The amount of traffic transferred by the network interface. net.br-e0b9521f4fd3 The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.br-e0b9521f4fd3 The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.br-e0b9521f4fd3 The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.br-e0b9521f4fd3 The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.br-e0b9521f4fd3 BR-E878EE8E3899 net.br-e878ee8e3899 net.br-e878ee8e3899 The amount of traffic transferred by the network interface. net.br-e878ee8e3899 The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.br-e878ee8e3899 The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.br-e878ee8e3899 The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.br-e878ee8e3899 The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.br-e878ee8e3899 DOCKER0 net.docker0 net.docker0 The amount of traffic transferred by the network interface. net.docker0 The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.docker0 The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.docker0 The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.docker0 The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.docker0 ENX001E063772AE net.enx001e063772ae net.enx001e063772ae The amount of traffic transferred by the network interface. net.enx001e063772ae The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.enx001e063772ae The number of packets that have been dropped at the network interface level. Inbound - packets received but not processed, e.g. due to softnet backlog overflow, bad/unintended VLAN tags, unknown or unregistered protocols, IPv6 frames when the server is not configured for IPv6. Outbound - packets dropped on their way to transmission, e.g. due to lack of resources. net_drops.enx001e063772ae The interface's latest or current speed that the network adapter negotiated with the device it is connected to. This does not give the max supported speed of the NIC. net_speed.enx001e063772ae The interface's latest or current duplex that the network adapter negotiated with the device it is connected to. Unknown - the duplex mode can not be determined. Half duplex - the communication is one direction at a time. Full duplex - the interface is able to send and receive data simultaneously. State map: 0 - unknown, 1 - half, 2 - full. net_duplex.enx001e063772ae The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.enx001e063772ae The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.enx001e063772ae The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.enx001e063772ae VETH0ACA2E4 net.veth0aca2e4 net.veth0aca2e4 The amount of traffic transferred by the network interface. net.veth0aca2e4 The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.veth0aca2e4 The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.veth0aca2e4 The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.veth0aca2e4 The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.veth0aca2e4 VETH07A5D21 net.veth07a5d21 net.veth07a5d21 The amount of traffic transferred by the network interface. net.veth07a5d21 The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.veth07a5d21 The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.veth07a5d21 The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.veth07a5d21 The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.veth07a5d21 VETH1E98983 net.veth1e98983 net.veth1e98983 The amount of traffic transferred by the network interface. net.veth1e98983 The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.veth1e98983 The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.veth1e98983 The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.veth1e98983 The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.veth1e98983 VETH5DE6FF4 net.veth5de6ff4 net.veth5de6ff4 The amount of traffic transferred by the network interface. net.veth5de6ff4 The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.veth5de6ff4 The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.veth5de6ff4 The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.veth5de6ff4 The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.veth5de6ff4 VETH6C20FAC net.veth6c20fac net.veth6c20fac The amount of traffic transferred by the network interface. net.veth6c20fac The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.veth6c20fac The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.veth6c20fac The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.veth6c20fac The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.veth6c20fac VETH7BFFA9B net.veth7bffa9b net.veth7bffa9b The amount of traffic transferred by the network interface. net.veth7bffa9b The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.veth7bffa9b The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.veth7bffa9b The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.veth7bffa9b The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.veth7bffa9b VETH9ACF72A net.veth9acf72a net.veth9acf72a The amount of traffic transferred by the network interface. net.veth9acf72a The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.veth9acf72a The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.veth9acf72a The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.veth9acf72a The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.veth9acf72a VETH9BF1F16 net.veth9bf1f16 net.veth9bf1f16 The amount of traffic transferred by the network interface. net.veth9bf1f16 The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.veth9bf1f16 The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.veth9bf1f16 The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.veth9bf1f16 The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.veth9bf1f16 VETH44D179C net.veth44d179c net.veth44d179c The amount of traffic transferred by the network interface. net.veth44d179c The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.veth44d179c The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.veth44d179c The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.veth44d179c The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.veth44d179c VETH587C8FF net.veth587c8ff net.veth587c8ff The amount of traffic transferred by the network interface. net.veth587c8ff The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.veth587c8ff The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.veth587c8ff The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.veth587c8ff The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.veth587c8ff VETH5721F01 net.veth5721f01 net.veth5721f01 The amount of traffic transferred by the network interface. net.veth5721f01 The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.veth5721f01 The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.veth5721f01 The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.veth5721f01 The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.veth5721f01 VETH96227F5 net.veth96227f5 net.veth96227f5 The amount of traffic transferred by the network interface. net.veth96227f5 The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.veth96227f5 The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.veth96227f5 The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.veth96227f5 The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.veth96227f5 VETHC3D4AF2 net.vethc3d4af2 net.vethc3d4af2 The amount of traffic transferred by the network interface. net.vethc3d4af2 The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.vethc3d4af2 The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.vethc3d4af2 The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.vethc3d4af2 The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.vethc3d4af2 VETHE8018B9 net.vethe8018b9 net.vethe8018b9 The amount of traffic transferred by the network interface. net.vethe8018b9 The number of packets transferred by the network interface. Received multicast counter is commonly calculated at the device level (unlike received) and therefore may include packets which did not reach the host. net_packets.vethe8018b9 The current operational state of the interface. Unknown - the state can not be determined. NotPresent - the interface has missing (typically, hardware) components. Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. LowerLayerDown - the interface is down due to state of lower-layer interface(s). Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. Up - the interface is ready to pass packets and can be used. State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up. net_operstate.vethe8018b9 The current physical link state of the interface. State map: 0 - down, 1 - up. net_carrier.vethe8018b9 The interface's currently configured Maximum transmission unit (MTU) value. MTU is the size of the largest protocol data unit that can be communicated in a single network layer transaction. net_mtu.vethe8018b9 -------------------------------------------------------------------------------- FIREWALL (NETFILTER) Performance metrics of the netfilter components. CONNECTION TRACKER Netfilter Connection Tracker performance metrics. The connection tracker keeps track of all connections of the machine, inbound and outbound. It works by keeping a database with all open connections, tracking network and address translation and connection expectations. The number of entries in the conntrack table. netfilter.conntrack_sockets Packet tracking statistics. New - conntrack entries added which were not expected before. Ignore - packets seen which are already connected to a conntrack entry. Invalid - packets seen which can not be tracked. netfilter.conntrack_new The number of changes in conntrack tables. Inserted, Deleted - conntrack entries which were inserted or removed. Delete-list - conntrack entries which were put to dying list. netfilter.conntrack_changes The number of events in the "expect" table. Connection tracking expectations are the mechanism used to "expect" RELATED connections to existing ones. An expectation is a connection that is expected to happen in a period of time. Created, Deleted - conntrack entries which were inserted or removed. New - conntrack entries added after an expectation for them was already present. netfilter.conntrack_expect Conntrack errors. IcmpError - packets which could not be tracked due to error situation. InsertFailed - entries for which list insertion was attempted but failed (happens if the same entry is already present). Drop - packets dropped due to conntrack failure. Either new conntrack entry allocation failed, or protocol helper dropped the packet. EarlyDrop - dropped conntrack entries to make room for new ones, if maximum table size was reached. netfilter.conntrack_errors Conntrack table lookup statistics. Searched - conntrack table lookups performed. Restarted - conntrack table lookups which had to be restarted due to hashtable resizes. Found - conntrack table lookups which were successful. netfilter.conntrack_search -------------------------------------------------------------------------------- SYSTEMD SERVICES Resources utilization of systemd services. Netdata monitors all systemd services via cgroups (the resources accounting used by containers). CPU Total CPU utilization within the system-wide CPU resources (all cores). The amount of time spent by tasks of the cgroup in user and kernel modes. services.cpu MEM The amount of used RAM. services.mem_usage SWAP The amount of used swap memory. services.swap_usage DISK The amount of data transferred from specific devices as seen by the CFQ scheduler. It is not updated when the CFQ scheduler is operating on a request queue. services.io_read The amount of data transferred to specific devices as seen by the CFQ scheduler. It is not updated when the CFQ scheduler is operating on a request queue. services.io_write The number of read operations performed on specific devices as seen by the CFQ scheduler. services.io_ops_read The number write operations performed on specific devices as seen by the CFQ scheduler. services.io_ops_write The amount of data transferred from specific devices as seen by the throttling policy. services.throttle_io_read The amount of data transferred to specific devices as seen by the throttling policy. services.throttle_io_write The number of read operations performed on specific devices as seen by the throttling policy. services.throttle_io_ops_read The number of write operations performed on specific devices as seen by the throttling policy. services.throttle_io_ops_write The number of queued read requests. services.queued_io_ops_read The number of queued write requests. services.queued_io_ops_write The number of read requests merged. services.merged_io_ops_read The number of write requests merged. services.merged_io_ops_write -------------------------------------------------------------------------------- APPLICATIONS Per application statistics are collected using apps.plugin. This plugin walks through all processes and aggregates statistics for application groups. The plugin also counts the resources of exited children. So for processes like shell scripts, the reported values include the resources used by the commands these scripts run within each timeframe. CPU Total CPU utilization (all cores). It includes user, system and guest time. apps.cpu The amount of time the CPU was busy executing code in user mode (all cores). apps.cpu_user The amount of time the CPU was busy executing code in kernel mode (all cores). apps.cpu_system DISK The amount of data that has been read from the storage layer. Actual physical disk I/O was required. apps.preads The amount of data that has been written to the storage layer. Actual physical disk I/O was required. apps.pwrites The amount of data that has been read from the storage layer. It includes things such as terminal I/O and is unaffected by whether or not actual physical disk I/O was required (the read might have been satisfied from pagecache). apps.lreads The amount of data that has been written or shall be written to the storage layer. It includes things such as terminal I/O and is unaffected by whether or not actual physical disk I/O was required. apps.lwrites The number of open files and directories. apps.files MEM Real memory (RAM) used by applications. This does not include shared memory. apps.mem Virtual memory allocated by applications. Check this article for more information. apps.vmem The number of minor faults which have not required loading a memory page from the disk. Minor page faults occur when a process needs data that is in memory and is assigned to another process. They share memory pages between multiple processes – no additional data needs to be read from disk to memory. apps.minor_faults PROCESSES The number of threads. apps.threads The number of processes. apps.processes The period of time within which at least one process in the group has been running. apps.uptime The number of open pipes. A pipe is a unidirectional data channel that can be used for interprocess communication. apps.pipes SWAP The amount of swapped-out virtual memory by anonymous private pages. This does not include shared swap memory. apps.swap The number of major faults which have required loading a memory page from the disk. Major page faults occur because of the absence of the required page from the RAM. They are expected when a process starts or needs to read in additional data and in these cases do not indicate a problem condition. However, a major page fault can also be the result of reading memory pages that have been written out to the swap file, which could indicate a memory shortage. apps.major_faults NETWORK Netdata also gives a summary for eBPF charts in Networking Stack submenu. The number of open sockets. Sockets are a way to enable inter-process communication between programs running on a server, or between programs running on separate servers. This includes both network and UNIX sockets. apps.sockets -------------------------------------------------------------------------------- USER GROUPS Per user group statistics are collected using apps.plugin. This plugin walks through all processes and aggregates statistics per user group. The plugin also counts the resources of exited children. So for processes like shell scripts, the reported values include the resources used by the commands these scripts run within each timeframe. CPU Total CPU utilization (all cores). It includes user, system and guest time. groups.cpu The amount of time the CPU was busy executing code in user mode (all cores). groups.cpu_user The amount of time the CPU was busy executing code in kernel mode (all cores). groups.cpu_system DISK The amount of data that has been read from the storage layer. Actual physical disk I/O was required. groups.preads The amount of data that has been written to the storage layer. Actual physical disk I/O was required. groups.pwrites The amount of data that has been read from the storage layer. It includes things such as terminal I/O and is unaffected by whether or not actual physical disk I/O was required (the read might have been satisfied from pagecache). groups.lreads The amount of data that has been written or shall be written to the storage layer. It includes things such as terminal I/O and is unaffected by whether or not actual physical disk I/O was required. groups.lwrites The number of open files and directories. groups.files MEM Real memory (RAM) used per user group. This does not include shared memory. groups.mem Virtual memory allocated per user group since the Netdata restart. Please check this article for more information. groups.vmem The number of minor faults which have not required loading a memory page from the disk. Minor page faults occur when a process needs data that is in memory and is assigned to another process. They share memory pages between multiple processes – no additional data needs to be read from disk to memory. groups.minor_faults PROCESSES The number of threads. groups.threads The number of processes. groups.processes The period of time within which at least one process in the group has been running. groups.uptime The number of open pipes. A pipe is a unidirectional data channel that can be used for interprocess communication. groups.pipes SWAP The amount of swapped-out virtual memory by anonymous private pages. This does not include shared swap memory. groups.swap The number of major faults which have required loading a memory page from the disk. Major page faults occur because of the absence of the required page from the RAM. They are expected when a process starts or needs to read in additional data and in these cases do not indicate a problem condition. However, a major page fault can also be the result of reading memory pages that have been written out to the swap file, which could indicate a memory shortage. groups.major_faults NET The number of open sockets. Sockets are a way to enable inter-process communication between programs running on a server, or between programs running on separate servers. This includes both network and UNIX sockets. groups.sockets -------------------------------------------------------------------------------- USERS Per user statistics are collected using apps.plugin. This plugin walks through all processes and aggregates statistics per user. The plugin also counts the resources of exited children. So for processes like shell scripts, the reported values include the resources used by the commands these scripts run within each timeframe. CPU Total CPU utilization (all cores). It includes user, system and guest time. users.cpu The amount of time the CPU was busy executing code in user mode (all cores). users.cpu_user The amount of time the CPU was busy executing code in kernel mode (all cores). users.cpu_system DISK The amount of data that has been read from the storage layer. Actual physical disk I/O was required. users.preads The amount of data that has been written to the storage layer. Actual physical disk I/O was required. users.pwrites The amount of data that has been read from the storage layer. It includes things such as terminal I/O and is unaffected by whether or not actual physical disk I/O was required (the read might have been satisfied from pagecache). users.lreads The amount of data that has been written or shall be written to the storage layer. It includes things such as terminal I/O and is unaffected by whether or not actual physical disk I/O was required. users.lwrites The number of open files and directories. users.files MEM Real memory (RAM) used per user group. This does not include shared memory. users.mem Virtual memory allocated per user group since the Netdata restart. Please check this article for more information. users.vmem The number of minor faults which have not required loading a memory page from the disk. Minor page faults occur when a process needs data that is in memory and is assigned to another process. They share memory pages between multiple processes – no additional data needs to be read from disk to memory. users.minor_faults PROCESSES The number of threads. users.threads The number of processes. users.processes The period of time within which at least one process in the group has been running. users.uptime The number of open pipes. A pipe is a unidirectional data channel that can be used for interprocess communication. users.pipes SWAP The amount of swapped-out virtual memory by anonymous private pages. This does not include shared swap memory. users.swap The number of major faults which have required loading a memory page from the disk. Major page faults occur because of the absence of the required page from the RAM. They are expected when a process starts or needs to read in additional data and in these cases do not indicate a problem condition. However, a major page fault can also be the result of reading memory pages that have been written out to the swap file, which could indicate a memory shortage. users.major_faults NET The number of open sockets. Sockets are a way to enable inter-process communication between programs running on a server, or between programs running on separate servers. This includes both network and UNIX sockets. users.sockets -------------------------------------------------------------------------------- 6E344535A8BE Container resource utilization metrics. Netdata reads this information from cgroups (abbreviated from control groups), a Linux kernel feature that limits and accounts resource usage (CPU, memory, disk I/O, network, etc.) of a collection of processes. cgroups together with namespaces (that offer isolation between processes) provide what we usually call: containers. cgroup_6e344535a8be.cpu_limit cgroup_6e344535a8be.mem_usage_limit cgroup_6e344535a8be.throttle_io cgroup_6e344535a8be.throttle_io CPU Total CPU utilization within the configured or system-wide (if not set) limits. When the CPU utilization of a cgroup exceeds the limit for the configured period, the tasks belonging to its hierarchy will be throttled and are not allowed to run again until the next period. cgroup_6e344535a8be.cpu_limit Total CPU utilization within the system-wide CPU resources (all cores). The amount of time spent by tasks of the cgroup in user and kernel modes. cgroup_6e344535a8be.cpu Total CPU utilization per core within the system-wide CPU resources. cgroup_6e344535a8be.cpu_per_core MEM RAM utilization within the configured or system-wide (if not set) limits. When the RAM utilization of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_6e344535a8be.mem_utilization RAM usage within the configured or system-wide (if not set) limits. When the RAM usage of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_6e344535a8be.mem_usage_limit The amount of used RAM and swap memory. cgroup_6e344535a8be.mem_usage Memory usage statistics. The individual metrics are described in the memory.stat section for cgroup-v1 and cgroup-v2. cgroup_6e344535a8be.mem Dirty is the amount of memory waiting to be written to disk. Writeback is how much memory is actively being written to disk. cgroup_6e344535a8be.writeback Memory accounting statistics. In - a page is accounted as either mapped anon page (RSS) or cache page (Page Cache) to the cgroup. Out - a page is unaccounted from the cgroup. cgroup_6e344535a8be.mem_activity Memory page fault statistics. Pgfault - all page faults. Swap - major page faults. cgroup_6e344535a8be.pgfaults DISK The amount of data transferred to and from specific devices as seen by the CFQ scheduler. It is not updated when the CFQ scheduler is operating on a request queue. cgroup_6e344535a8be.io The number of I/O operations performed on specific devices as seen by the CFQ scheduler. cgroup_6e344535a8be.serviced_ops The amount of data transferred to and from specific devices as seen by the throttling policy. cgroup_6e344535a8be.throttle_io The number of I/O operations performed on specific devices as seen by the throttling policy. cgroup_6e344535a8be.throttle_serviced_ops The number of BIOS requests merged into requests for I/O operations. cgroup_6e344535a8be.merged_ops -------------------------------------------------------------------------------- 8D66473C29B4 Container resource utilization metrics. Netdata reads this information from cgroups (abbreviated from control groups), a Linux kernel feature that limits and accounts resource usage (CPU, memory, disk I/O, network, etc.) of a collection of processes. cgroups together with namespaces (that offer isolation between processes) provide what we usually call: containers. cgroup_8d66473c29b4.cpu_limit cgroup_8d66473c29b4.mem_usage_limit cgroup_8d66473c29b4.throttle_io cgroup_8d66473c29b4.throttle_io CPU Total CPU utilization within the configured or system-wide (if not set) limits. When the CPU utilization of a cgroup exceeds the limit for the configured period, the tasks belonging to its hierarchy will be throttled and are not allowed to run again until the next period. cgroup_8d66473c29b4.cpu_limit Total CPU utilization within the system-wide CPU resources (all cores). The amount of time spent by tasks of the cgroup in user and kernel modes. cgroup_8d66473c29b4.cpu Total CPU utilization per core within the system-wide CPU resources. cgroup_8d66473c29b4.cpu_per_core MEM RAM utilization within the configured or system-wide (if not set) limits. When the RAM utilization of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_8d66473c29b4.mem_utilization RAM usage within the configured or system-wide (if not set) limits. When the RAM usage of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_8d66473c29b4.mem_usage_limit The amount of used RAM and swap memory. cgroup_8d66473c29b4.mem_usage Memory usage statistics. The individual metrics are described in the memory.stat section for cgroup-v1 and cgroup-v2. cgroup_8d66473c29b4.mem Dirty is the amount of memory waiting to be written to disk. Writeback is how much memory is actively being written to disk. cgroup_8d66473c29b4.writeback Memory accounting statistics. In - a page is accounted as either mapped anon page (RSS) or cache page (Page Cache) to the cgroup. Out - a page is unaccounted from the cgroup. cgroup_8d66473c29b4.mem_activity Memory page fault statistics. Pgfault - all page faults. Swap - major page faults. cgroup_8d66473c29b4.pgfaults DISK The amount of data transferred to and from specific devices as seen by the CFQ scheduler. It is not updated when the CFQ scheduler is operating on a request queue. cgroup_8d66473c29b4.io The number of I/O operations performed on specific devices as seen by the CFQ scheduler. cgroup_8d66473c29b4.serviced_ops The amount of data transferred to and from specific devices as seen by the throttling policy. cgroup_8d66473c29b4.throttle_io The number of I/O operations performed on specific devices as seen by the throttling policy. cgroup_8d66473c29b4.throttle_serviced_ops The number of requests queued for I/O operations. cgroup_8d66473c29b4.queued_ops The number of BIOS requests merged into requests for I/O operations. cgroup_8d66473c29b4.merged_ops -------------------------------------------------------------------------------- 9EEB72A6F133 Container resource utilization metrics. Netdata reads this information from cgroups (abbreviated from control groups), a Linux kernel feature that limits and accounts resource usage (CPU, memory, disk I/O, network, etc.) of a collection of processes. cgroups together with namespaces (that offer isolation between processes) provide what we usually call: containers. cgroup_9eeb72a6f133.cpu_limit cgroup_9eeb72a6f133.mem_usage_limit cgroup_9eeb72a6f133.throttle_io cgroup_9eeb72a6f133.throttle_io CPU Total CPU utilization within the configured or system-wide (if not set) limits. When the CPU utilization of a cgroup exceeds the limit for the configured period, the tasks belonging to its hierarchy will be throttled and are not allowed to run again until the next period. cgroup_9eeb72a6f133.cpu_limit Total CPU utilization within the system-wide CPU resources (all cores). The amount of time spent by tasks of the cgroup in user and kernel modes. cgroup_9eeb72a6f133.cpu Total CPU utilization per core within the system-wide CPU resources. cgroup_9eeb72a6f133.cpu_per_core MEM RAM utilization within the configured or system-wide (if not set) limits. When the RAM utilization of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_9eeb72a6f133.mem_utilization RAM usage within the configured or system-wide (if not set) limits. When the RAM usage of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_9eeb72a6f133.mem_usage_limit The amount of used RAM and swap memory. cgroup_9eeb72a6f133.mem_usage Memory usage statistics. The individual metrics are described in the memory.stat section for cgroup-v1 and cgroup-v2. cgroup_9eeb72a6f133.mem Dirty is the amount of memory waiting to be written to disk. Writeback is how much memory is actively being written to disk. cgroup_9eeb72a6f133.writeback Memory accounting statistics. In - a page is accounted as either mapped anon page (RSS) or cache page (Page Cache) to the cgroup. Out - a page is unaccounted from the cgroup. cgroup_9eeb72a6f133.mem_activity Memory page fault statistics. Pgfault - all page faults. Swap - major page faults. cgroup_9eeb72a6f133.pgfaults DISK The amount of data transferred to and from specific devices as seen by the CFQ scheduler. It is not updated when the CFQ scheduler is operating on a request queue. cgroup_9eeb72a6f133.io The number of I/O operations performed on specific devices as seen by the CFQ scheduler. cgroup_9eeb72a6f133.serviced_ops The amount of data transferred to and from specific devices as seen by the throttling policy. cgroup_9eeb72a6f133.throttle_io The number of I/O operations performed on specific devices as seen by the throttling policy. cgroup_9eeb72a6f133.throttle_serviced_ops The number of BIOS requests merged into requests for I/O operations. cgroup_9eeb72a6f133.merged_ops -------------------------------------------------------------------------------- 27A1C59D725C Container resource utilization metrics. Netdata reads this information from cgroups (abbreviated from control groups), a Linux kernel feature that limits and accounts resource usage (CPU, memory, disk I/O, network, etc.) of a collection of processes. cgroups together with namespaces (that offer isolation between processes) provide what we usually call: containers. cgroup_27a1c59d725c.cpu_limit cgroup_27a1c59d725c.mem_usage_limit cgroup_27a1c59d725c.throttle_io cgroup_27a1c59d725c.throttle_io CPU Total CPU utilization within the configured or system-wide (if not set) limits. When the CPU utilization of a cgroup exceeds the limit for the configured period, the tasks belonging to its hierarchy will be throttled and are not allowed to run again until the next period. cgroup_27a1c59d725c.cpu_limit Total CPU utilization within the system-wide CPU resources (all cores). The amount of time spent by tasks of the cgroup in user and kernel modes. cgroup_27a1c59d725c.cpu Total CPU utilization per core within the system-wide CPU resources. cgroup_27a1c59d725c.cpu_per_core MEM RAM utilization within the configured or system-wide (if not set) limits. When the RAM utilization of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_27a1c59d725c.mem_utilization RAM usage within the configured or system-wide (if not set) limits. When the RAM usage of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_27a1c59d725c.mem_usage_limit The amount of used RAM and swap memory. cgroup_27a1c59d725c.mem_usage Memory usage statistics. The individual metrics are described in the memory.stat section for cgroup-v1 and cgroup-v2. cgroup_27a1c59d725c.mem Dirty is the amount of memory waiting to be written to disk. Writeback is how much memory is actively being written to disk. cgroup_27a1c59d725c.writeback Memory accounting statistics. In - a page is accounted as either mapped anon page (RSS) or cache page (Page Cache) to the cgroup. Out - a page is unaccounted from the cgroup. cgroup_27a1c59d725c.mem_activity Memory page fault statistics. Pgfault - all page faults. Swap - major page faults. cgroup_27a1c59d725c.pgfaults DISK The amount of data transferred to and from specific devices as seen by the CFQ scheduler. It is not updated when the CFQ scheduler is operating on a request queue. cgroup_27a1c59d725c.io The number of I/O operations performed on specific devices as seen by the CFQ scheduler. cgroup_27a1c59d725c.serviced_ops The amount of data transferred to and from specific devices as seen by the throttling policy. cgroup_27a1c59d725c.throttle_io The number of I/O operations performed on specific devices as seen by the throttling policy. cgroup_27a1c59d725c.throttle_serviced_ops The number of requests queued for I/O operations. cgroup_27a1c59d725c.queued_ops The number of BIOS requests merged into requests for I/O operations. cgroup_27a1c59d725c.merged_ops -------------------------------------------------------------------------------- 30D4E3835CC8 Container resource utilization metrics. Netdata reads this information from cgroups (abbreviated from control groups), a Linux kernel feature that limits and accounts resource usage (CPU, memory, disk I/O, network, etc.) of a collection of processes. cgroups together with namespaces (that offer isolation between processes) provide what we usually call: containers. cgroup_30d4e3835cc8.cpu_limit cgroup_30d4e3835cc8.mem_usage_limit cgroup_30d4e3835cc8.throttle_io cgroup_30d4e3835cc8.throttle_io CPU Total CPU utilization within the configured or system-wide (if not set) limits. When the CPU utilization of a cgroup exceeds the limit for the configured period, the tasks belonging to its hierarchy will be throttled and are not allowed to run again until the next period. cgroup_30d4e3835cc8.cpu_limit Total CPU utilization within the system-wide CPU resources (all cores). The amount of time spent by tasks of the cgroup in user and kernel modes. cgroup_30d4e3835cc8.cpu Total CPU utilization per core within the system-wide CPU resources. cgroup_30d4e3835cc8.cpu_per_core MEM RAM utilization within the configured or system-wide (if not set) limits. When the RAM utilization of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_30d4e3835cc8.mem_utilization RAM usage within the configured or system-wide (if not set) limits. When the RAM usage of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_30d4e3835cc8.mem_usage_limit The amount of used RAM and swap memory. cgroup_30d4e3835cc8.mem_usage Memory usage statistics. The individual metrics are described in the memory.stat section for cgroup-v1 and cgroup-v2. cgroup_30d4e3835cc8.mem Dirty is the amount of memory waiting to be written to disk. Writeback is how much memory is actively being written to disk. cgroup_30d4e3835cc8.writeback Memory accounting statistics. In - a page is accounted as either mapped anon page (RSS) or cache page (Page Cache) to the cgroup. Out - a page is unaccounted from the cgroup. cgroup_30d4e3835cc8.mem_activity Memory page fault statistics. Pgfault - all page faults. Swap - major page faults. cgroup_30d4e3835cc8.pgfaults DISK The amount of data transferred to and from specific devices as seen by the CFQ scheduler. It is not updated when the CFQ scheduler is operating on a request queue. cgroup_30d4e3835cc8.io The number of I/O operations performed on specific devices as seen by the CFQ scheduler. cgroup_30d4e3835cc8.serviced_ops The amount of data transferred to and from specific devices as seen by the throttling policy. cgroup_30d4e3835cc8.throttle_io The number of I/O operations performed on specific devices as seen by the throttling policy. cgroup_30d4e3835cc8.throttle_serviced_ops The number of requests queued for I/O operations. cgroup_30d4e3835cc8.queued_ops The number of BIOS requests merged into requests for I/O operations. cgroup_30d4e3835cc8.merged_ops -------------------------------------------------------------------------------- 53C538F6D014 Container resource utilization metrics. Netdata reads this information from cgroups (abbreviated from control groups), a Linux kernel feature that limits and accounts resource usage (CPU, memory, disk I/O, network, etc.) of a collection of processes. cgroups together with namespaces (that offer isolation between processes) provide what we usually call: containers. cgroup_53c538f6d014.cpu_limit cgroup_53c538f6d014.mem_usage_limit cgroup_53c538f6d014.throttle_io cgroup_53c538f6d014.throttle_io CPU Total CPU utilization within the configured or system-wide (if not set) limits. When the CPU utilization of a cgroup exceeds the limit for the configured period, the tasks belonging to its hierarchy will be throttled and are not allowed to run again until the next period. cgroup_53c538f6d014.cpu_limit Total CPU utilization within the system-wide CPU resources (all cores). The amount of time spent by tasks of the cgroup in user and kernel modes. cgroup_53c538f6d014.cpu Total CPU utilization per core within the system-wide CPU resources. cgroup_53c538f6d014.cpu_per_core MEM RAM utilization within the configured or system-wide (if not set) limits. When the RAM utilization of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_53c538f6d014.mem_utilization RAM usage within the configured or system-wide (if not set) limits. When the RAM usage of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_53c538f6d014.mem_usage_limit The amount of used RAM and swap memory. cgroup_53c538f6d014.mem_usage Memory usage statistics. The individual metrics are described in the memory.stat section for cgroup-v1 and cgroup-v2. cgroup_53c538f6d014.mem Dirty is the amount of memory waiting to be written to disk. Writeback is how much memory is actively being written to disk. cgroup_53c538f6d014.writeback Memory accounting statistics. In - a page is accounted as either mapped anon page (RSS) or cache page (Page Cache) to the cgroup. Out - a page is unaccounted from the cgroup. cgroup_53c538f6d014.mem_activity Memory page fault statistics. Pgfault - all page faults. Swap - major page faults. cgroup_53c538f6d014.pgfaults DISK The amount of data transferred to and from specific devices as seen by the CFQ scheduler. It is not updated when the CFQ scheduler is operating on a request queue. cgroup_53c538f6d014.io The number of I/O operations performed on specific devices as seen by the CFQ scheduler. cgroup_53c538f6d014.serviced_ops The amount of data transferred to and from specific devices as seen by the throttling policy. cgroup_53c538f6d014.throttle_io The number of I/O operations performed on specific devices as seen by the throttling policy. cgroup_53c538f6d014.throttle_serviced_ops The number of BIOS requests merged into requests for I/O operations. cgroup_53c538f6d014.merged_ops -------------------------------------------------------------------------------- 93E27022812D Container resource utilization metrics. Netdata reads this information from cgroups (abbreviated from control groups), a Linux kernel feature that limits and accounts resource usage (CPU, memory, disk I/O, network, etc.) of a collection of processes. cgroups together with namespaces (that offer isolation between processes) provide what we usually call: containers. cgroup_93e27022812d.cpu_limit cgroup_93e27022812d.mem_usage_limit cgroup_93e27022812d.throttle_io cgroup_93e27022812d.throttle_io CPU Total CPU utilization within the configured or system-wide (if not set) limits. When the CPU utilization of a cgroup exceeds the limit for the configured period, the tasks belonging to its hierarchy will be throttled and are not allowed to run again until the next period. cgroup_93e27022812d.cpu_limit Total CPU utilization within the system-wide CPU resources (all cores). The amount of time spent by tasks of the cgroup in user and kernel modes. cgroup_93e27022812d.cpu Total CPU utilization per core within the system-wide CPU resources. cgroup_93e27022812d.cpu_per_core MEM RAM utilization within the configured or system-wide (if not set) limits. When the RAM utilization of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_93e27022812d.mem_utilization RAM usage within the configured or system-wide (if not set) limits. When the RAM usage of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_93e27022812d.mem_usage_limit The amount of used RAM and swap memory. cgroup_93e27022812d.mem_usage Memory usage statistics. The individual metrics are described in the memory.stat section for cgroup-v1 and cgroup-v2. cgroup_93e27022812d.mem Dirty is the amount of memory waiting to be written to disk. Writeback is how much memory is actively being written to disk. cgroup_93e27022812d.writeback Memory accounting statistics. In - a page is accounted as either mapped anon page (RSS) or cache page (Page Cache) to the cgroup. Out - a page is unaccounted from the cgroup. cgroup_93e27022812d.mem_activity Memory page fault statistics. Pgfault - all page faults. Swap - major page faults. cgroup_93e27022812d.pgfaults DISK The amount of data transferred to and from specific devices as seen by the CFQ scheduler. It is not updated when the CFQ scheduler is operating on a request queue. cgroup_93e27022812d.io The number of I/O operations performed on specific devices as seen by the CFQ scheduler. cgroup_93e27022812d.serviced_ops The amount of data transferred to and from specific devices as seen by the throttling policy. cgroup_93e27022812d.throttle_io The number of I/O operations performed on specific devices as seen by the throttling policy. cgroup_93e27022812d.throttle_serviced_ops The number of BIOS requests merged into requests for I/O operations. cgroup_93e27022812d.merged_ops -------------------------------------------------------------------------------- 8458A511EF53 Container resource utilization metrics. Netdata reads this information from cgroups (abbreviated from control groups), a Linux kernel feature that limits and accounts resource usage (CPU, memory, disk I/O, network, etc.) of a collection of processes. cgroups together with namespaces (that offer isolation between processes) provide what we usually call: containers. cgroup_8458a511ef53.cpu_limit cgroup_8458a511ef53.mem_usage_limit cgroup_8458a511ef53.throttle_io cgroup_8458a511ef53.throttle_io CPU Total CPU utilization within the configured or system-wide (if not set) limits. When the CPU utilization of a cgroup exceeds the limit for the configured period, the tasks belonging to its hierarchy will be throttled and are not allowed to run again until the next period. cgroup_8458a511ef53.cpu_limit Total CPU utilization within the system-wide CPU resources (all cores). The amount of time spent by tasks of the cgroup in user and kernel modes. cgroup_8458a511ef53.cpu Total CPU utilization per core within the system-wide CPU resources. cgroup_8458a511ef53.cpu_per_core MEM RAM utilization within the configured or system-wide (if not set) limits. When the RAM utilization of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_8458a511ef53.mem_utilization RAM usage within the configured or system-wide (if not set) limits. When the RAM usage of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_8458a511ef53.mem_usage_limit The amount of used RAM and swap memory. cgroup_8458a511ef53.mem_usage Memory usage statistics. The individual metrics are described in the memory.stat section for cgroup-v1 and cgroup-v2. cgroup_8458a511ef53.mem Dirty is the amount of memory waiting to be written to disk. Writeback is how much memory is actively being written to disk. cgroup_8458a511ef53.writeback Memory accounting statistics. In - a page is accounted as either mapped anon page (RSS) or cache page (Page Cache) to the cgroup. Out - a page is unaccounted from the cgroup. cgroup_8458a511ef53.mem_activity Memory page fault statistics. Pgfault - all page faults. Swap - major page faults. cgroup_8458a511ef53.pgfaults DISK The amount of data transferred to and from specific devices as seen by the CFQ scheduler. It is not updated when the CFQ scheduler is operating on a request queue. cgroup_8458a511ef53.io The number of I/O operations performed on specific devices as seen by the CFQ scheduler. cgroup_8458a511ef53.serviced_ops The amount of data transferred to and from specific devices as seen by the throttling policy. cgroup_8458a511ef53.throttle_io The number of I/O operations performed on specific devices as seen by the throttling policy. cgroup_8458a511ef53.throttle_serviced_ops The number of BIOS requests merged into requests for I/O operations. cgroup_8458a511ef53.merged_ops -------------------------------------------------------------------------------- 9853E56CFE85 Container resource utilization metrics. Netdata reads this information from cgroups (abbreviated from control groups), a Linux kernel feature that limits and accounts resource usage (CPU, memory, disk I/O, network, etc.) of a collection of processes. cgroups together with namespaces (that offer isolation between processes) provide what we usually call: containers. cgroup_9853e56cfe85.cpu_limit cgroup_9853e56cfe85.mem_usage_limit cgroup_9853e56cfe85.throttle_io cgroup_9853e56cfe85.throttle_io CPU Total CPU utilization within the configured or system-wide (if not set) limits. When the CPU utilization of a cgroup exceeds the limit for the configured period, the tasks belonging to its hierarchy will be throttled and are not allowed to run again until the next period. cgroup_9853e56cfe85.cpu_limit Total CPU utilization within the system-wide CPU resources (all cores). The amount of time spent by tasks of the cgroup in user and kernel modes. cgroup_9853e56cfe85.cpu Total CPU utilization per core within the system-wide CPU resources. cgroup_9853e56cfe85.cpu_per_core MEM RAM utilization within the configured or system-wide (if not set) limits. When the RAM utilization of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_9853e56cfe85.mem_utilization RAM usage within the configured or system-wide (if not set) limits. When the RAM usage of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_9853e56cfe85.mem_usage_limit The amount of used RAM and swap memory. cgroup_9853e56cfe85.mem_usage Memory usage statistics. The individual metrics are described in the memory.stat section for cgroup-v1 and cgroup-v2. cgroup_9853e56cfe85.mem Dirty is the amount of memory waiting to be written to disk. Writeback is how much memory is actively being written to disk. cgroup_9853e56cfe85.writeback Memory accounting statistics. In - a page is accounted as either mapped anon page (RSS) or cache page (Page Cache) to the cgroup. Out - a page is unaccounted from the cgroup. cgroup_9853e56cfe85.mem_activity Memory page fault statistics. Pgfault - all page faults. Swap - major page faults. cgroup_9853e56cfe85.pgfaults DISK The amount of data transferred to and from specific devices as seen by the CFQ scheduler. It is not updated when the CFQ scheduler is operating on a request queue. cgroup_9853e56cfe85.io The number of I/O operations performed on specific devices as seen by the CFQ scheduler. cgroup_9853e56cfe85.serviced_ops The amount of data transferred to and from specific devices as seen by the throttling policy. cgroup_9853e56cfe85.throttle_io The number of I/O operations performed on specific devices as seen by the throttling policy. cgroup_9853e56cfe85.throttle_serviced_ops The number of BIOS requests merged into requests for I/O operations. cgroup_9853e56cfe85.merged_ops -------------------------------------------------------------------------------- AA55B6B437A9 Container resource utilization metrics. Netdata reads this information from cgroups (abbreviated from control groups), a Linux kernel feature that limits and accounts resource usage (CPU, memory, disk I/O, network, etc.) of a collection of processes. cgroups together with namespaces (that offer isolation between processes) provide what we usually call: containers. cgroup_aa55b6b437a9.cpu_limit cgroup_aa55b6b437a9.mem_usage_limit cgroup_aa55b6b437a9.throttle_io cgroup_aa55b6b437a9.throttle_io CPU Total CPU utilization within the configured or system-wide (if not set) limits. When the CPU utilization of a cgroup exceeds the limit for the configured period, the tasks belonging to its hierarchy will be throttled and are not allowed to run again until the next period. cgroup_aa55b6b437a9.cpu_limit Total CPU utilization within the system-wide CPU resources (all cores). The amount of time spent by tasks of the cgroup in user and kernel modes. cgroup_aa55b6b437a9.cpu Total CPU utilization per core within the system-wide CPU resources. cgroup_aa55b6b437a9.cpu_per_core MEM RAM utilization within the configured or system-wide (if not set) limits. When the RAM utilization of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_aa55b6b437a9.mem_utilization RAM usage within the configured or system-wide (if not set) limits. When the RAM usage of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_aa55b6b437a9.mem_usage_limit The amount of used RAM and swap memory. cgroup_aa55b6b437a9.mem_usage Memory usage statistics. The individual metrics are described in the memory.stat section for cgroup-v1 and cgroup-v2. cgroup_aa55b6b437a9.mem Dirty is the amount of memory waiting to be written to disk. Writeback is how much memory is actively being written to disk. cgroup_aa55b6b437a9.writeback Memory accounting statistics. In - a page is accounted as either mapped anon page (RSS) or cache page (Page Cache) to the cgroup. Out - a page is unaccounted from the cgroup. cgroup_aa55b6b437a9.mem_activity Memory page fault statistics. Pgfault - all page faults. Swap - major page faults. cgroup_aa55b6b437a9.pgfaults DISK The amount of data transferred to and from specific devices as seen by the CFQ scheduler. It is not updated when the CFQ scheduler is operating on a request queue. cgroup_aa55b6b437a9.io The number of I/O operations performed on specific devices as seen by the CFQ scheduler. cgroup_aa55b6b437a9.serviced_ops The amount of data transferred to and from specific devices as seen by the throttling policy. cgroup_aa55b6b437a9.throttle_io The number of I/O operations performed on specific devices as seen by the throttling policy. cgroup_aa55b6b437a9.throttle_serviced_ops The number of requests queued for I/O operations. cgroup_aa55b6b437a9.queued_ops The number of BIOS requests merged into requests for I/O operations. cgroup_aa55b6b437a9.merged_ops -------------------------------------------------------------------------------- CB90733C95C3 Container resource utilization metrics. Netdata reads this information from cgroups (abbreviated from control groups), a Linux kernel feature that limits and accounts resource usage (CPU, memory, disk I/O, network, etc.) of a collection of processes. cgroups together with namespaces (that offer isolation between processes) provide what we usually call: containers. cgroup_cb90733c95c3.cpu_limit cgroup_cb90733c95c3.mem_usage_limit cgroup_cb90733c95c3.throttle_io cgroup_cb90733c95c3.throttle_io CPU Total CPU utilization within the configured or system-wide (if not set) limits. When the CPU utilization of a cgroup exceeds the limit for the configured period, the tasks belonging to its hierarchy will be throttled and are not allowed to run again until the next period. cgroup_cb90733c95c3.cpu_limit Total CPU utilization within the system-wide CPU resources (all cores). The amount of time spent by tasks of the cgroup in user and kernel modes. cgroup_cb90733c95c3.cpu Total CPU utilization per core within the system-wide CPU resources. cgroup_cb90733c95c3.cpu_per_core MEM RAM utilization within the configured or system-wide (if not set) limits. When the RAM utilization of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_cb90733c95c3.mem_utilization RAM usage within the configured or system-wide (if not set) limits. When the RAM usage of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_cb90733c95c3.mem_usage_limit The amount of used RAM and swap memory. cgroup_cb90733c95c3.mem_usage Memory usage statistics. The individual metrics are described in the memory.stat section for cgroup-v1 and cgroup-v2. cgroup_cb90733c95c3.mem Dirty is the amount of memory waiting to be written to disk. Writeback is how much memory is actively being written to disk. cgroup_cb90733c95c3.writeback Memory accounting statistics. In - a page is accounted as either mapped anon page (RSS) or cache page (Page Cache) to the cgroup. Out - a page is unaccounted from the cgroup. cgroup_cb90733c95c3.mem_activity Memory page fault statistics. Pgfault - all page faults. Swap - major page faults. cgroup_cb90733c95c3.pgfaults DISK The amount of data transferred to and from specific devices as seen by the CFQ scheduler. It is not updated when the CFQ scheduler is operating on a request queue. cgroup_cb90733c95c3.io The number of I/O operations performed on specific devices as seen by the CFQ scheduler. cgroup_cb90733c95c3.serviced_ops The amount of data transferred to and from specific devices as seen by the throttling policy. cgroup_cb90733c95c3.throttle_io The number of I/O operations performed on specific devices as seen by the throttling policy. cgroup_cb90733c95c3.throttle_serviced_ops The number of requests queued for I/O operations. cgroup_cb90733c95c3.queued_ops The number of BIOS requests merged into requests for I/O operations. cgroup_cb90733c95c3.merged_ops -------------------------------------------------------------------------------- F061A397AC01 Container resource utilization metrics. Netdata reads this information from cgroups (abbreviated from control groups), a Linux kernel feature that limits and accounts resource usage (CPU, memory, disk I/O, network, etc.) of a collection of processes. cgroups together with namespaces (that offer isolation between processes) provide what we usually call: containers. cgroup_f061a397ac01.cpu_limit cgroup_f061a397ac01.mem_usage_limit cgroup_f061a397ac01.throttle_io cgroup_f061a397ac01.throttle_io CPU Total CPU utilization within the configured or system-wide (if not set) limits. When the CPU utilization of a cgroup exceeds the limit for the configured period, the tasks belonging to its hierarchy will be throttled and are not allowed to run again until the next period. cgroup_f061a397ac01.cpu_limit Total CPU utilization within the system-wide CPU resources (all cores). The amount of time spent by tasks of the cgroup in user and kernel modes. cgroup_f061a397ac01.cpu Total CPU utilization per core within the system-wide CPU resources. cgroup_f061a397ac01.cpu_per_core MEM RAM utilization within the configured or system-wide (if not set) limits. When the RAM utilization of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_f061a397ac01.mem_utilization RAM usage within the configured or system-wide (if not set) limits. When the RAM usage of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_f061a397ac01.mem_usage_limit The amount of used RAM and swap memory. cgroup_f061a397ac01.mem_usage Memory usage statistics. The individual metrics are described in the memory.stat section for cgroup-v1 and cgroup-v2. cgroup_f061a397ac01.mem Dirty is the amount of memory waiting to be written to disk. Writeback is how much memory is actively being written to disk. cgroup_f061a397ac01.writeback Memory accounting statistics. In - a page is accounted as either mapped anon page (RSS) or cache page (Page Cache) to the cgroup. Out - a page is unaccounted from the cgroup. cgroup_f061a397ac01.mem_activity Memory page fault statistics. Pgfault - all page faults. Swap - major page faults. cgroup_f061a397ac01.pgfaults DISK The amount of data transferred to and from specific devices as seen by the CFQ scheduler. It is not updated when the CFQ scheduler is operating on a request queue. cgroup_f061a397ac01.io The number of I/O operations performed on specific devices as seen by the CFQ scheduler. cgroup_f061a397ac01.serviced_ops The amount of data transferred to and from specific devices as seen by the throttling policy. cgroup_f061a397ac01.throttle_io The number of I/O operations performed on specific devices as seen by the throttling policy. cgroup_f061a397ac01.throttle_serviced_ops The number of BIOS requests merged into requests for I/O operations. cgroup_f061a397ac01.merged_ops -------------------------------------------------------------------------------- F2E7352A20E2 Container resource utilization metrics. Netdata reads this information from cgroups (abbreviated from control groups), a Linux kernel feature that limits and accounts resource usage (CPU, memory, disk I/O, network, etc.) of a collection of processes. cgroups together with namespaces (that offer isolation between processes) provide what we usually call: containers. cgroup_f2e7352a20e2.cpu_limit cgroup_f2e7352a20e2.mem_usage_limit cgroup_f2e7352a20e2.throttle_io cgroup_f2e7352a20e2.throttle_io CPU Total CPU utilization within the configured or system-wide (if not set) limits. When the CPU utilization of a cgroup exceeds the limit for the configured period, the tasks belonging to its hierarchy will be throttled and are not allowed to run again until the next period. cgroup_f2e7352a20e2.cpu_limit Total CPU utilization within the system-wide CPU resources (all cores). The amount of time spent by tasks of the cgroup in user and kernel modes. cgroup_f2e7352a20e2.cpu Total CPU utilization per core within the system-wide CPU resources. cgroup_f2e7352a20e2.cpu_per_core MEM RAM utilization within the configured or system-wide (if not set) limits. When the RAM utilization of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_f2e7352a20e2.mem_utilization RAM usage within the configured or system-wide (if not set) limits. When the RAM usage of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_f2e7352a20e2.mem_usage_limit The amount of used RAM and swap memory. cgroup_f2e7352a20e2.mem_usage Memory usage statistics. The individual metrics are described in the memory.stat section for cgroup-v1 and cgroup-v2. cgroup_f2e7352a20e2.mem Dirty is the amount of memory waiting to be written to disk. Writeback is how much memory is actively being written to disk. cgroup_f2e7352a20e2.writeback Memory accounting statistics. In - a page is accounted as either mapped anon page (RSS) or cache page (Page Cache) to the cgroup. Out - a page is unaccounted from the cgroup. cgroup_f2e7352a20e2.mem_activity Memory page fault statistics. Pgfault - all page faults. Swap - major page faults. cgroup_f2e7352a20e2.pgfaults DISK The amount of data transferred to and from specific devices as seen by the CFQ scheduler. It is not updated when the CFQ scheduler is operating on a request queue. cgroup_f2e7352a20e2.io The number of I/O operations performed on specific devices as seen by the CFQ scheduler. cgroup_f2e7352a20e2.serviced_ops The amount of data transferred to and from specific devices as seen by the throttling policy. cgroup_f2e7352a20e2.throttle_io The number of I/O operations performed on specific devices as seen by the throttling policy. cgroup_f2e7352a20e2.throttle_serviced_ops The number of BIOS requests merged into requests for I/O operations. cgroup_f2e7352a20e2.merged_ops -------------------------------------------------------------------------------- F6F45786FE28 Container resource utilization metrics. Netdata reads this information from cgroups (abbreviated from control groups), a Linux kernel feature that limits and accounts resource usage (CPU, memory, disk I/O, network, etc.) of a collection of processes. cgroups together with namespaces (that offer isolation between processes) provide what we usually call: containers. cgroup_f6f45786fe28.cpu_limit cgroup_f6f45786fe28.mem_usage_limit cgroup_f6f45786fe28.throttle_io cgroup_f6f45786fe28.throttle_io CPU Total CPU utilization within the configured or system-wide (if not set) limits. When the CPU utilization of a cgroup exceeds the limit for the configured period, the tasks belonging to its hierarchy will be throttled and are not allowed to run again until the next period. cgroup_f6f45786fe28.cpu_limit Total CPU utilization within the system-wide CPU resources (all cores). The amount of time spent by tasks of the cgroup in user and kernel modes. cgroup_f6f45786fe28.cpu Total CPU utilization per core within the system-wide CPU resources. cgroup_f6f45786fe28.cpu_per_core MEM RAM utilization within the configured or system-wide (if not set) limits. When the RAM utilization of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_f6f45786fe28.mem_utilization RAM usage within the configured or system-wide (if not set) limits. When the RAM usage of a cgroup exceeds the limit, OOM killer will start killing the tasks belonging to the cgroup. cgroup_f6f45786fe28.mem_usage_limit The amount of used RAM and swap memory. cgroup_f6f45786fe28.mem_usage Memory usage statistics. The individual metrics are described in the memory.stat section for cgroup-v1 and cgroup-v2. cgroup_f6f45786fe28.mem Dirty is the amount of memory waiting to be written to disk. Writeback is how much memory is actively being written to disk. cgroup_f6f45786fe28.writeback Memory accounting statistics. In - a page is accounted as either mapped anon page (RSS) or cache page (Page Cache) to the cgroup. Out - a page is unaccounted from the cgroup. cgroup_f6f45786fe28.mem_activity Memory page fault statistics. Pgfault - all page faults. Swap - major page faults. cgroup_f6f45786fe28.pgfaults DISK The amount of data transferred to and from specific devices as seen by the CFQ scheduler. It is not updated when the CFQ scheduler is operating on a request queue. cgroup_f6f45786fe28.io The number of I/O operations performed on specific devices as seen by the CFQ scheduler. cgroup_f6f45786fe28.serviced_ops The amount of data transferred to and from specific devices as seen by the throttling policy. cgroup_f6f45786fe28.throttle_io The number of I/O operations performed on specific devices as seen by the throttling policy. cgroup_f6f45786fe28.throttle_serviced_ops The number of BIOS requests merged into requests for I/O operations. cgroup_f6f45786fe28.merged_ops -------------------------------------------------------------------------------- SENSORS Readings of the configured system sensors. VOLTAGE sensors.ads7846-spi-1-1_voltage -------------------------------------------------------------------------------- NETDATA MONITORING Performance metrics for the operation of netdata itself and its plugins. NETDATA netdata.net netdata.server_cpu netdata.uptime netdata.clients netdata.requests The netdata API response time measures the time netdata needed to serve requests. This time includes everything, from the reception of the first byte of a request, to the dispatch of the last byte of its reply, therefore it includes all network latencies involved (i.e. a client over a slow network will influence these metrics). netdata.response_time netdata.compression_ratio QUERIES netdata.queries netdata.db_points DBENGINE netdata.dbengine_compression_ratio netdata.page_cache_hit_ratio netdata.page_cache_stats netdata.dbengine_long_term_page_stats netdata.dbengine_io_throughput netdata.dbengine_io_operations netdata.dbengine_global_errors netdata.dbengine_global_file_descriptors netdata.dbengine_ram CGROUPS netdata.plugin_cgroups_cpu PROC netdata.plugin_proc_cpu netdata.plugin_proc_modules WEB netdata.web_thread1_cpu netdata.web_thread2_cpu netdata.web_thread3_cpu netdata.web_thread4_cpu netdata.web_thread5_cpu netdata.web_thread6_cpu STATSD netdata.plugin_statsd_charting_cpu netdata.plugin_statsd_collector1_cpu netdata.statsd_metrics netdata.statsd_useful_metrics netdata.statsd_events netdata.statsd_reads netdata.statsd_bytes netdata.statsd_packets netdata.tcp_connects netdata.tcp_connected netdata.private_charts DISKSPACE netdata.plugin_diskspace netdata.plugin_diskspace_dt TIMEX netdata.plugin_timex netdata.plugin_timex_dt TC.HELPER netdata.plugin_tc_cpu netdata.plugin_tc_time APPS.PLUGIN netdata.apps_cpu netdata.apps_sizes netdata.apps_fix netdata.apps_children_fix PYTHON.D netdata.runtime_sensors -------------------------------------------------------------------------------- * System Overview * cpu * load * disk * ram * swap * network * processes * idlejitter * interrupts * softirqs * softnet * entropy * uptime * clock synchronization * ipc semaphores * ipc shared memory * CPUs * utilization * interrupts * softirqs * softnet * cpufreq * Memory * system * kernel * slab * Disks * mmcblk1 * sdb * zram0 * zram1 * zram2 * zram3 * zram4 * zram5 * zram6 * zram7 * sda * / * /dev * /dev/shm * /etc/netdata * /var/cache/netdata * /var/lib/netdata * Networking Stack * tcp * broadcast * ecn * IPv4 Networking * sockets * packets * icmp * tcp * udp * IPv6 Networking * tcp6 * Network Interfaces * br-09badf13f34d * br-5b55b4414204 * br-77c3e60744dc * br-99fcfb471d7c * br-35501a5efc3f * br-a30aea43c2e1 * br-b8c09b3ac6db * br-d3119ad3368c * br-e0b9521f4fd3 * br-e878ee8e3899 * docker0 * enx001e063772ae * veth0aca2e4 * veth07a5d21 * veth1e98983 * veth5de6ff4 * veth6c20fac * veth7bffa9b * veth9acf72a * veth9bf1f16 * veth44d179c * veth587c8ff * veth5721f01 * veth96227f5 * vethc3d4af2 * vethe8018b9 * Firewall (netfilter) * connection tracker * systemd Services * cpu * mem * swap * disk * Applications * cpu * disk * mem * processes * swap * network * User Groups * cpu * disk * mem * processes * swap * net * Users * cpu * disk * mem * processes * swap * net * 6e344535a8be * cpu * mem * disk * 8d66473c29b4 * cpu * mem * disk * 9eeb72a6f133 * cpu * mem * disk * 27a1c59d725c * cpu * mem * disk * 30d4e3835cc8 * cpu * mem * disk * 53c538f6d014 * cpu * mem * disk * 93e27022812d * cpu * mem * disk * 8458a511ef53 * cpu * mem * disk * 9853e56cfe85 * cpu * mem * disk * aa55b6b437a9 * cpu * mem * disk * cb90733c95c3 * cpu * mem * disk * f061a397ac01 * cpu * mem * disk * f2e7352a20e2 * cpu * mem * disk * f6f45786fe28 * cpu * mem * disk * Sensors * voltage * Netdata Monitoring * netdata * queries * dbengine * cgroups * proc * web * statsd * diskspace * timex * tc.helper * apps.plugin * python.d * Add more charts * Add more alarms * Every second, Netdata collects 3,303 metrics on odrohc2, presents them in 729 charts and monitors them with 287 alarms. netdata v1.31.0-459-nightly * Do you like Netdata? Give us a star! And share the word! Netdata Copyright 2020, Netdata, Inc. Terms and conditions Privacy Policy Released under GPL v3 or later. Netdata uses third party tools. XSS PROTECTION This dashboard is about to render data from server: To protect your privacy, the dashboard will check all data transferred for cross site scripting (XSS). This is CPU intensive, so your browser might be a bit slower. If you trust the remote server, you can disable XSS protection. In this case, any remote dashboard decoration code (javascript) will also run. If you don't trust the remote server, you should keep the protection on. The dashboard will run slower and remote dashboard decoration code will not run, but better be safe than sorry... Keep protecting me I don't need this, the server is mine × PRINT THIS NETDATA DASHBOARD netdata dashboards cannot be captured, since we are lazy loading and hiding all but the visible charts. To capture the whole page with all the charts rendered, a new browser window will pop-up that will render all the charts at once. The new browser window will maintain the current pan and zoom settings of the charts. So, align the charts before proceeding. This process will put some CPU and memory pressure on your browser. For the netdata server, we will sequencially download all the charts, to avoid congesting network and server resources. Please, do not print netdata dashboards on paper! Print Close × PREPARING DASHBOARD FOR PRINTING... Please wait while we initialize and render all the charts on the dashboard. The print dialog will appear as soon as we finish rendering the page. × IMPORT A NETDATA SNAPSHOT netdata can export and import dashboard snapshots. Any netdata can import the snapshot of any other netdata. The snapshots are not uploaded to a server. They are handled entirely by your web browser, on your computer. Click here to select the netdata snapshot file to import Browse for a snapshot file (or drag it and drop it here), then click Import to render it. FilenameHostnameOrigin URLCharts InfoSnapshot InfoTime RangeComments Snapshot files contain both data and javascript code. Make sure you trust the files you import! Import Close × EXPORT A SNAPSHOT Please wait while we collect all the dashboard data... Select the desired resolution of the snapshot. This is the seconds of data per point. Filename Compression * Select Compression * * uncompressed * * pako.deflate (gzip, binary) * pako.deflate.base64 (gzip, ascii) * * lzstring.uri (LZ, ascii) * lzstring.utf16 (LZ, utf16) * lzstring.base64 (LZ, ascii) Comments Select snaphost resolution. This controls the size the snapshot file. The generated snapshot will include all charts of this dashboard, for the visible timeframe, so align, pan and zoom the charts as needed. The scroll position of the dashboard will also be saved. The snapshot will be downloaded as a file, to your computer, that can be imported back into any netdata dashboard (no need to import it back on this server). Snapshot files include all the information of the dashboard, including the URL of the origin server, its netdata unique ID, etc. So, if you share the snapshot file with third parties, they will be able to access the origin server, if this server is exposed on the internet. Snapshots are handled entirely by the web browser. The netdata servers are not aware of them. Export Cancel × NETDATA ALARMS * Active * All * Log loading... loading... loading... Close × NETDATA DASHBOARD OPTIONS These are browser settings. Each viewer has its own. They do not affect the operation of your netdata server. Settings take effect immediately and are saved permanently to browser local storage (except the refresh on focus / always option). To reset all options (including charts sizes) to their defaults, click here. * Performance * Synchronization * Visual * Locale On FocusAlways When to refresh the charts? When set to On Focus, the charts will stop being updated if the page / tab does not have the focus of the user. When set to Always, the charts will always be refreshed. Set it to On Focus it to lower the CPU requirements of the browser (and extend the battery of laptops and tablets) when this page does not have your focus. Set to Always to work on another window (i.e. change the settings of something) and have the charts auto-refresh in this window. Non ZeroAll Which dimensions to show? When set to Non Zero, dimensions that have all their values (within the current view) set to zero will not be transferred from the netdata server (except if all dimensions of the chart are zero, in which case this setting does nothing - all dimensions are transferred and shown). When set to All, all dimensions will always be shown. Set it to Non Zero to lower the data transferred between netdata and your browser, lower the CPU requirements of your browser (fewer lines to draw) and increase the focus on the legends (fewer entries at the legends). DestroyHide How to handle hidden charts? When set to Destroy, charts that are not in the current viewport of the browser (are above, or below the visible area of the page), will be destroyed and re-created if and when they become visible again. When set to Hide, the not-visible charts will be just hidden, to simplify the DOM and speed up your browser. Set it to Destroy, to lower the memory requirements of your browser. Set it to Hide for faster restoration of charts on page scrolling. AsyncSync Page scroll handling? When set to Sync, charts will be examined for their visibility immediately after scrolling. On slow computers this may impact the smoothness of page scrolling. To update the page when scrolling ends, set it to Async. Set it to Sync for immediate chart updates when scrolling. Set it to Async for smoother page scrolling on slower computers. ParallelSequential Which chart refresh policy to use? When set to parallel, visible charts are refreshed in parallel (all queries are sent to netdata server in parallel) and are rendered asynchronously. When set to sequential charts are refreshed one after another. Set it to parallel if your browser can cope with it (most modern browsers do), set it to sequential if you work on an older/slower computer. ResyncBest Effort Shall we re-sync chart refreshes? When set to Resync, the dashboard will attempt to re-synchronize all the charts so that they are refreshed concurrently. When set to Best Effort, each chart may be refreshed with a little time difference to the others. Normally, the dashboard starts refreshing them in parallel, but depending on the speed of your computer and the network latencies, charts start having a slight time difference. Setting this to Resync will attempt to re-synchronize the charts on every update. Setting it to Best Effort may lower the pressure on your browser and the network. SyncDon't Sync Sync hover selection on all charts? When enabled, a selection on one chart will automatically select the same time on all other visible charts and the legends of all visible charts will be updated to show the selected values. When disabled, only the chart getting the user's attention will be selected. Enable it to get better insights of the data. Disable it if you are on a very slow computer that cannot actually do it. RightBelow Where do you want to see the legend? Netdata can place the legend in two positions: Below charts (the default) or to the Right of charts. Switching this will reload the dashboard. DarkWhite Which theme to use? Netdata comes with two themes: Dark (the default) and White. Switching this will reload the dashboard. Help MeNo Help Do you need help? Netdata can show some help in some areas to help you use the dashboard. If all these balloons bother you, disable them using this switch. Switching this will reload the dashboard. PadDon't Pad Enable data padding when panning and zooming? When set to Pad the charts will be padded with more data, both before and after the visible area, thus giving the impression the whole database is loaded. This padding will happen only after the first pan or zoom operation on the chart (initially all charts have only the visible data). When set to Don't Pad only the visible data will be transfered from the netdata server, even after the first pan and zoom operation. SmoothRough Enable Bézier lines on charts? When set to Smooth the charts libraries that support it, will plot smooth curves instead of simple straight lines to connect the points. Keep in mind dygraphs, the main charting library in netdata dashboards, can only smooth line charts. It cannot smooth area or stacked charts. When set to Rough, this setting can lower the CPU resources consumed by your browser. These settings are applied gradually, as charts are updated. To force them, refresh the dashboard now. Scale UnitsFixed Units Enable auto-scaling of select units? When set to Scale Units the values shown will dynamically be scaled (e.g. 1000 kilobits will be shown as 1 megabit). Netdata can auto-scale these original units: kilobits/s, kilobytes/s, KB/s, KB, MB, and GB. When set to Fixed Units all the values will be rendered using the original units maintained by the netdata server. CelsiusFahrenheit Which units to use for temperatures? Set the temperature units of the dashboard. TimeSeconds Convert seconds to time? When set to Time, charts that present seconds will show DDd:HH:MM:SS. When set to Seconds, the raw number of seconds will be presented. Close × UPDATE CHECK Your netdata version: v1.31.0-459-nightly New version of netdata available! Latest version: v1.32.1-32-nightly Click here for the changes log and click here for directions on updating your netdata installation. We suggest to review the changes log for new features you may be interested, or important bug fixes you may need. Keeping your netdata updated is generally a good idea. -------------------------------------------------------------------------------- For progress reports and key netdata updates: Join the Netdata Community You can also follow netdata on twitter, follow netdata on facebook, or watch netdata on github. Check Now Close × SIGN IN Signing-in to netdata.cloud will synchronize the list of your netdata monitored nodes known at registry . This may include server hostnames, urls and identification GUIDs. After you upgrade all your netdata servers, your private registry will not be needed any more. Are you sure you want to proceed? Cancel Sign In × DELETE ? You are about to delete, from your personal list of netdata servers, the following server: Are you sure you want to do this? Keep in mind, this server will be added back if and when you visit it again. keep it delete it × SWITCH NETDATA REGISTRY IDENTITY You can copy and paste the following ID to all your browsers (e.g. work and home). All the browsers with the same ID will identify you, so please don't share this with others. Either copy this ID and paste it to another browser, or paste here the ID you have taken from another browser. Keep in mind that: * when you switch ID, your previous ID will be lost forever - this is irreversible. * both IDs (your old and the new) must list this netdata at their personal lists. * both IDs have to be known by the registry: . * to get a new ID, just clear your browser cookies. cancel impersonate × Checking known URLs for this server... Checks may fail if you are viewing an HTTPS page and the server to be checked is HTTP only. Close