monitoring.lahfa.xyz Open in urlscan Pro
2001:bc8:38ee::1 Public Scan

Back to summary

URL:
https://monitoring.lahfa.xyz/
Submission Tags: phishingrod
Submission: On October 16 via api (October 16th 2023, 10:19:07 am UTC) from DE — 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: 0px;"><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: 0px;"><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: 0px;"><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: 0px;"><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: 0px;"><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: 0px;"><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: 0px;"><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: 0px;"><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: 0px;"><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: 0px;"><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: 0px;"><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 transferred 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: 0px;"><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: 0px;"><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: 0px;"><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: 0px;"><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!
REPLICATED NODES

amadeus

askeladd
Live
borg-dc1
Live
core01
Live
media
Live
productivity
Live
public-infra
Live
zaku
Live
VISITED NODES

amadeuschevron_right
https://monitoring.lahfa.xyz/
Welcome back!Sign in again to enjoy the benefits of Netdata Cloud Sign in
amadeus
Connection to Cloud

UTC +2
Playing

10/16/23 • 12:1212:19
• last
7min
2
2
Sign in
Discover the free benefits of Netdata Cloud:
Home
Node View
Overview
Nodes
Dashboards
Alerts
Anomalies
Pricing
Privacy

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.
0.1Disk ReadMiB/s
0.1Disk WriteMiB/s
7.5CPU%0.0100.0
3.8Net Inboundmegabits/s
1.0Net Outboundmegabits/s
31.5Used 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.22%). 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
12:12:30
12:13:00
12:13:30
12:14:00
12:14:30
12:15:00
12:15:30
12:16:00
12:16:30
12:17:00
12:17:30
12:18:00
12:18:30
12:19:00

guest_nice

guest

steal

softirq

irq

user

system

nice

iowait
percentage
Mon, Oct 16, 2023|12:19:04

guest_nice0.0

guest0.0

steal0.0

softirq0.3

irq0.0

user3.3

system1.6

nice2.3

iowait0.0

CPU Pressure Stall Information. Some indicates the share of time in which at
least some tasks are stalled on CPU. The ratios are tracked as recent trends
over 10-, 60-, and 300-second windows.
CPU some pressure (system.cpu_some_pressure)
0.00
0.05
0.10
0.15
0.20
0.25
0.30
0.35
0.40
12:12:30
12:13:00
12:13:30
12:14:00
12:14:30
12:15:00
12:15:30
12:16:00
12:16:30
12:17:00
12:17:30
12:18:00
12:18:30
12:19:00

some 10

some 60

some 300
percentage
Mon, Oct 16, 2023|12:19:04

some 100.00

some 600.02

some 3000.00

The amount of time some processes have been waiting for CPU time.
CPU some pressure stall time (system.cpu_some_pressure_stall_time)
2.0
4.0
6.0
8.0
10.0
12.0
14.0
12:12:30
12:13:00
12:13:30
12:14:00
12:14:30
12:15:00
12:15:30
12:16:00
12:16:30
12:17:00
12:17:30
12:18:00
12:18:30
12:19:00

time
ms
Mon, Oct 16, 2023|12:19:04

time2.7

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

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.
system.io

Memory paged from/to disk. This is usually the total disk I/O of the system.
system.pgpgio

I/O Pressure Stall Information. Some indicates the share of time in which at
least some tasks are stalled on I/O. In this state the CPU is still doing
productive work. The ratios are tracked as recent trends over 10-, 60-, and
300-second windows.
system.io_some_pressure

The amount of time some processes have been waiting due to I/O congestion.
system.io_some_pressure_stall_time

I/O Pressure Stall Information. Full line indicates the share of time in which
all non-idle tasks are stalled on I/O resource simultaneously. In this state
actual CPU cycles are going to waste, and a workload that spends extended time
in this state is considered to be thrashing. This has severe impact on
performance. The ratios are tracked as recent trends over 10-, 60-, and
300-second windows.
system.io_full_pressure

The amount of time all non-idle processes have been stalled due to I/O
congestion.
system.io_full_pressure_stall_time

RAM

System Random Access Memory (i.e. physical memory) usage.
system.ram

Memory Pressure Stall Information. Some indicates the share of time in which at
least some tasks are stalled on memory. In this state the CPU is still doing
productive work. The ratios are tracked as recent trends over 10-, 60-, and
300-second windows.
system.memory_some_pressure

The amount of time some processes have been waiting due to memory congestion.
system.memory_some_pressure_stall_time

Memory Pressure Stall Information. Full indicates the share of time in which all
non-idle tasks are stalled on memory resource simultaneously. In this state
actual CPU cycles are going to waste, and a workload that spends extended time
in this state is considered to be thrashing. This has severe impact on
performance. The ratios are tracked as recent trends over 10-, 60-, and
300-second windows.
system.memory_full_pressure

The amount of time all non-idle processes have been stalled due to memory
congestion.
system.memory_full_pressure_stall_time

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

Total IPv6 Traffic.
system.ipv6

PROCESSES

System processes.

Running - running or ready to run (runnable). Blocked - currently blocked,
waiting for I/O to complete.

system.processes

The number of processes in different states.

Running - Process using the CPU at a particular moment. Sleeping
(uninterruptible) - Process will wake when a waited-upon resource becomes
available or after a time-out occurs during that wait. Mostly used by device
drivers waiting for disk or network I/O. Sleeping (interruptible) - Process is
waiting either for a particular time slot or for a particular event to occur.
Zombie - Process that has completed its execution, released the system
resources, but its entry is not removed from the process table. Usually occurs
in child processes when the parent process still needs to read its child’s exit
status. A process that stays a zombie for a long time is generally an error and
causes syst...

The number of processes in different states.

show more information
system.processes_state

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

FILES

system.file_nr_used

system.file_nr_utilization

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 as provided by the ntp_adjtime() system
call. An unsynchronized clock may be the result of synchronization issues by the
NTP daemon or a hardware clock fault. 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

The kernel code can operate in various modes and with various features enabled
or disabled, as selected by the ntp_adjtime() system call. The system clock
status shows the value of the time_status variable in the kernel. The bits of
the variable are used to control these functions and record error conditions as
they exist.

UNSYNC - set/cleared by the caller to indicate clock unsynchronized (e.g., when
no peers are reachable). This flag is usually controlled by an application
program, but the operating system may also set it. CLOCKERR - set/cleared by the
external hardware clock driver to indicate hardware fault.

Status map: 0 - bit unset, 1 - bit set.

system.clock_status

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

cpu.cpu8

cpu.cpu9

cpu.cpu10

cpu.cpu11

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

cpu.cpu8_interrupts

cpu.cpu9_interrupts

cpu.cpu10_interrupts

cpu.cpu11_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

cpu.cpu8_softirqs

cpu.cpu9_softirqs

cpu.cpu10_softirqs

cpu.cpu11_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.

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

cpu.cpu8_softnet_stat

cpu.cpu9_softnet_stat

cpu.cpu10_softnet_stat

cpu.cpu11_softnet_stat

THROTTLING

CPU throttling is commonly used to automatically slow down the computer when
possible to use less energy and conserve battery.

The number of adjustments made to the clock speed of the CPU based on it's core
temperature.
cpu.core_throttling

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.

OVERVIEW

Available Memory is estimated by the kernel, as the amount of RAM that can be
used by userspace processes, without causing swapping.
mem.available

Committed Memory, is the sum of all memory which has been allocated by
processes.
mem.committed

mem.directmaps

OOM KILLS

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

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).
mem.swap

mem.swap_cached

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.
mem.swapio

PAGE FAULTS

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

WRITEBACK

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

KERNEL

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

RECLAIMING

mem.reclaiming

CMA

mem.cma

HUGEPAGES

Hugepages is a feature that allows the kernel to utilize the multiple page size
capabilities of modern hardware architectures. The kernel creates multiple pages
of virtual memory, mapped from both physical RAM and swap. There is a mechanism
in the CPU architecture called "Translation Lookaside Buffers" (TLB) to manage
the mapping of virtual memory pages to actual physical memory addresses. The TLB
is a limited hardware resource, so utilizing a large amount of physical memory
with the default page size consumes the TLB and adds processing overhead. By
utilizing Huge Pages, the kernel is able to create pages of much larger sizes,
each page consuming a single resource in the TLB. Huge Pages are pinned to
physical RAM and cannot be swapped/paged out.

mem.thp

mem.thp_details

mem.thp_faults

mem.thp_file

mem.thp_collapse

mem.thp_split

mem.thp_compact

EDAC

mem.edac_mc0

mem.edac_mc0_dimm0

mem.edac_mc0_dimm3

--------------------------------------------------------------------------------

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.

AMADEUS-ROOT-1

disk.dm-0

disk_util.dm-0

The amount of data transferred to and from disk.
disk.dm-0

The amount of discarded data that are no longer in use by a mounted file system.
disk_ext.dm-0

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.dm-0

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.

show more information
disk_ext_ops.dm-0

I/O operations currently in progress. This metric is a snapshot - it is not an
average over the last interval.
disk_qops.dm-0

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.dm-0

Disk Busy Time measures the amount of time the disk was busy with something.
disk_busy.dm-0

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.dm-0

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.dm-0

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.dm-0

The average I/O operation size.
disk_avgsz.dm-0

The average discard operation size.
disk_ext_avgsz.dm-0

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.dm-0

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.dm-0

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.dm-0

AMADEUS-ROOT-2

disk.dm-1

disk_util.dm-1

The amount of data transferred to and from disk.
disk.dm-1

The amount of discarded data that are no longer in use by a mounted file system.
disk_ext.dm-1

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.dm-1

The number (after merges) of completed discard/flush requests.

show more information
disk_ext_ops.dm-1

I/O operations currently in progress. This metric is a snapshot - it is not an
average over the last interval.
disk_qops.dm-1

Disk Busy Time measures the amount of time the disk was busy with something.
disk_busy.dm-1

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.dm-1

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.dm-1

The average I/O operation size.
disk_avgsz.dm-1

The average discard operation size.
disk_ext_avgsz.dm-1

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.dm-1

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.dm-1

DEV-DISK-BYX2...FE235BAX2D03

disk.dm-2

disk_util.dm-2

The amount of data transferred to and from disk.
disk.dm-2

The amount of discarded data that are no longer in use by a mounted file system.
disk_ext.dm-2

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.dm-2

The number (after merges) of completed discard/flush requests.

show more information
disk_ext_ops.dm-2

I/O operations currently in progress. This metric is a snapshot - it is not an
average over the last interval.
disk_qops.dm-2

Disk Busy Time measures the amount of time the disk was busy with something.
disk_busy.dm-2

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.dm-2

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.dm-2

The average I/O operation size.
disk_avgsz.dm-2

The average discard operation size.
disk_ext_avgsz.dm-2

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.dm-2

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.dm-2

IPXE

disk.sr0

disk_util.sr0

The amount of data transferred to and from disk.
disk.sr0

The amount of discarded data that are no longer in use by a mounted file system.
disk_ext.sr0

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.sr0

The number (after merges) of completed discard/flush requests.

show more information
disk_ext_ops.sr0

I/O operations currently in progress. This metric is a snapshot - it is not an
average over the last interval.
disk_qops.sr0

Disk Busy Time measures the amount of time the disk was busy with something.
disk_busy.sr0

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.sr0

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.sr0

The average I/O operation size.
disk_avgsz.sr0

The average discard operation size.
disk_ext_avgsz.sr0

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.sr0

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.sr0

SDA

disk.sda

disk_util.sda

The amount of data transferred to and from disk.
disk.sda

The amount of discarded data that are no longer in use by a mounted file system.
disk_ext.sda

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.sda

The number (after merges) of completed discard/flush requests.

show more information
disk_ext_ops.sda

I/O operations currently in progress. This metric is a snapshot - it is not an
average over the last interval.
disk_qops.sda

Disk Busy Time measures the amount of time the disk was busy with something.
disk_busy.sda

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.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 I/O operation size.
disk_avgsz.sda

The average discard operation size.
disk_ext_avgsz.sda

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.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 I/O operations. This number can exceed
the interval if the disk is able to execute I/O operations in parallel.
disk_iotime.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

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.

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

Disk Busy Time measures the amount of time the disk was busy with something.
disk_busy.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 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

/BOOT

Disk space utilization. reserved for root is automatically reserved by the
system to prevent the root user from getting out of space.
disk_space._boot

/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

/RUN

Disk space utilization. reserved for root is automatically reserved by the
system to prevent the root user from getting out of space.
disk_space._run

/RUN/WRAPPERS

Disk space utilization. reserved for root is automatically reserved by the
system to prevent the root user from getting out of space.
disk_space._run_wrappers

--------------------------------------------------------------------------------

BTRFS FILESYSTEM

Disk space metrics for the BTRFS filesystem.

0488F610-2280...8CAF41D5082B

Physical disk usage of BTRFS. The disk space reported here is the raw physical
disk space assigned to the BTRFS volume (i.e. before any RAID levels). BTRFS
uses a two-stage allocator, first allocating large regions of disk space for one
type of block (data, metadata, or system), and then using a regular block
allocator inside those regions. unallocated is the physical disk space that is
not allocated yet and is available to become data, metadata or system on demand.
When unallocated is zero, all available disk space has been allocated to a
specific function. Healthy volumes should ideally have at least five percent of
their total space unallocated. You can keep your volume healthy by running the
btrfs balance command on it regularl...
Physical disk usage of BTRFS. The disk space reported here is the raw physical
disk space assigned to the BTRFS volume (i.e. before any RAID levels). BTRFS
uses a two-stage allocator, first allocating large regions of disk space for one
type of block (data, metadata, or system), and then using a regular block
allocator inside those regions. unallocated is the physical disk space that is
not allocated yet and is available to become data, metadata or system on demand.
When unallocated is zero, all available disk space has been allocated to a
specific function. Healthy volumes should ideally have at least five percent of
their total space unallocated. You can keep your volume healthy by running the
btrfs balance command on it regularly (check man btrfs-balance for more info).
Note that some of the space listed as unallocated may not actually be usable if
the volume uses devices of different sizes.
show more information
btrfs.disk_0488f610-2280-47b8-8684-8caf41d5082b

Logical disk usage for BTRFS data. Data chunks are used to store the actual file
data (file contents). The disk space reported here is the usable allocation
(i.e. after any striping or replication). Healthy volumes should ideally have no
more than a few GB of free space reported here persistently. Running btrfs
balance can help here.
btrfs.data_0488f610-2280-47b8-8684-8caf41d5082b

Logical disk usage for BTRFS metadata. Metadata chunks store most of the
filesystem internal structures, as well as information like directory structure
and file names. The disk space reported here is the usable allocation (i.e.
after any striping or replication). Healthy volumes should ideally have no more
than a few GB of free space reported here persistently. Running btrfs balance
can help here.
btrfs.metadata_0488f610-2280-47b8-8684-8caf41d5082b

Logical disk usage for BTRFS system. System chunks store information about the
allocation of other chunks. The disk space reported here is the usable
allocation (i.e. after any striping or replication). The values reported here
should be relatively small compared to Data and Metadata, and will scale with
the volume size and overall space usage.
btrfs.system_0488f610-2280-47b8-8684-8caf41d5082b

Tracks per-device error counts. Five types of errors are tracked: read errors,
write errors, flush errors, corruption errors, and generation errors. Read,
write, and flush are errors reported by the underlying block device when trying
to perform the associated operations on behalf of BTRFS. Corruption errors count
checksum mismatches, which usually are a result of either at-rest data
corruption or hardware problems. Generation errors count generational mismatches
within the internal data structures of the volume, and are also usually
indicative of at-rest data corruption or hardware problems. Note that errors
reported here may not trigger an associated IO error in userspace, as BTRFS has
relatively robust error recovery that allows...
Tracks per-device error counts. Five types of errors are tracked: read errors,
write errors, flush errors, corruption errors, and generation errors. Read,
write, and flush are errors reported by the underlying block device when trying
to perform the associated operations on behalf of BTRFS. Corruption errors count
checksum mismatches, which usually are a result of either at-rest data
corruption or hardware problems. Generation errors count generational mismatches
within the internal data structures of the volume, and are also usually
indicative of at-rest data corruption or hardware problems. Note that errors
reported here may not trigger an associated IO error in userspace, as BTRFS has
relatively robust error recovery that allows it to return correct data in most
multi-device setups.
show more information
btrfs.device_errors_dev1_0488f610-2280-47b8-8684-8caf41d5082b

6C1658A1-4674...85CA8498AC4C

--------------------------------------------------------------------------------

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 connection aborts.

BadData - happens while the connection is on FIN_WAIT1 and the kernel receives a
packet with a sequence number beyond the last one for this connection - the
kernel responds with RST (closes the connection). UserClosed - happens when the
kernel receives data on an already closed connection and responds with RST.
NoMemory - happens when there are too many orphaned sockets (not attached to an
fd) and the kernel has to drop a connection - sometimes it will send an RST,
sometimes it won't. Timeout - happens when a connection times out. Linger -
happens when the kernel killed a socket that was already closed by the
application and lingered around for long enough. Failed - happens when the
kernel attempted to se...

TCP connection aborts.

show more information
ip.tcpconnaborts

The accept queue of the kernel holds the fully established TCP connections,
waiting to be handled by the listening application.

Overflows - the number of established connections that could not be handled
because the receive queue of the listening application was full. Drops - number
of incoming connections that could not be handled, including SYN floods,
overflows, out of memory, security issues, no route to destination, reception of
related ICMP messages, socket is broadcast or multicast.

ip.tcp_accept_queue

TCP prevents out-of-order packets by either sequencing them in the correct order
or by requesting the retransmission of out-of-order packets.

Timestamp - detected re-ordering using the timestamp option. SACK - detected
re-ordering using Selective Acknowledgment algorithm. FACK - detected
re-ordering using Forward Acknowledgment algorithm. Reno - detected re-ordering
using Fast Retransmit algorithm.

ip.tcpreorders

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

SYN cookies are used to mitigate SYN flood.

Received - after sending a SYN cookie, it came back to us and passed the check.
Sent - an application was not able to accept a connection fast enough, so the
kernel could not store an entry in the queue for this connection. Instead of
dropping it, it sent a SYN cookie to the client. Failed - the MSS decoded from
the SYN cookie is invalid. When this counter is incremented, the received packet
won’t be treated as a SYN cookie.

ip.tcpsyncookies

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

ERRORS

The number of discarded IPv4 packets.

InDiscards, OutDiscards - inbound and outbound packets which were chosen to be
discarded even though no errors had been detected to prevent their being
deliverable to a higher-layer protocol. InHdrErrors - input packets that have
been discarded due to errors in their IP headers, including bad checksums,
version number mismatch, other format errors, time-to-live exceeded, errors
discovered in processing their IP options, etc. OutNoRoutes - packets that have
been discarded because no route could be found to transmit them to their
destination. This includes any packets which a host cannot route because all of
its default gateways are down. InAddrErrors - input packets that have been
discarded du...

The number of discarded IPv4 packets.

show more information
ipv4.errors

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 errors.

InErrs - TCP segments received in error (including header too small, checksum
errors, sequence errors, bad packets - for both IPv4 and IPv6). InCsumErrors -
TCP segments received with checksum errors (for both IPv4 and IPv6). RetransSegs
- TCP segments retransmitted.

ipv4.tcperrors

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

RAW

The number of used raw sockets.
ipv4.sockstat_raw_sockets

FRAGMENTS

IPv4 fragmentation statistics for this system.

OK - packets that have been successfully fragmented. Failed - packets that have
been discarded because they needed to be fragmented but could not be, e.g. due
to Don't Fragment (DF) flag was set. Created - fragments that have been
generated as a result of fragmentation.

ipv4.fragsout

IPv4 reassembly statistics for this system.

OK - packets that have been successfully reassembled. Failed - failures detected
by the IP reassembly algorithm. This is not necessarily a count of discarded IP
fragments since some algorithms can lose track of the number of fragments by
combining them as they are received. All - received IP fragments which needed to
be reassembled.

ipv4.fragsin

--------------------------------------------------------------------------------

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.

PACKETS

IPv6 packet 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. Delivers - packets
delivered to the upper layer protocols, e.g. TCP, UDP, ICMP, and so on.

ipv6.packets

Total number of received IPv6 packets with ECN bits set in the system.

CEP - congestion encountered. NoECTP - non ECN-capable transport. ECTP0 and
ECTP1 - ECN capable transport.

ipv6.ect

ERRORS

The number of discarded IPv6 packets.

InDiscards, OutDiscards - packets which were chosen to be discarded even though
no errors had been detected to prevent their being deliverable to a higher-layer
protocol. InHdrErrors - errors in IP headers, including bad checksums, version
number mismatch, other format errors, time-to-live exceeded, etc. InAddrErrors -
invalid IP address or the destination IP address is not a local address and IP
forwarding is not enabled. InUnknownProtos - unknown or unsupported protocol.
InTooBigErrors - the size exceeded the link MTU. InTruncatedPkts - packet frame
did not carry enough data. InNoRoutes - no route could be found while
forwarding. OutNoRoutes - no route could be found for packets generated by this
host.

ipv6.errors

FRAGMENTS6

IPv6 fragmentation statistics for this system.

OK - packets that have been successfully fragmented. Failed - packets that have
been discarded because they needed to be fragmented but could not be, e.g. due
to Don't Fragment (DF) flag was set. All - fragments that have been generated as
a result of fragmentation.

ipv6.fragsout

IPv6 reassembly statistics for this system.

OK - packets that have been successfully reassembled. Failed - failures detected
by the IP reassembly algorithm. This is not necessarily a count of discarded IP
fragments since some algorithms can lose track of the number of fragments by
combining them as they are received. Timeout - reassembly timeouts detected. All
- received IP fragments which needed to be reassembled.

ipv6.fragsin

TCP6

The number of TCP sockets in any state, excluding TIME-WAIT and CLOSED.
ipv6.sockstat6_tcp_sockets

UDP6

The number of used UDP sockets.
ipv6.sockstat6_udp_sockets

The number of transferred UDP packets.
ipv6.udppackets

The number of errors encountered during transferring UDP packets.

UDPLITE6

The number of errors encountered during transferring UDP-Lite packets.

ipv6.udpliteerrors

RAW6

The number of used raw sockets.
ipv6.sockstat6_raw_sockets

MULTICAST6

Total IPv6 multicast traffic.
ipv6.mcast

Total transferred IPv6 multicast packets.
ipv6.mcastpkts

ICMP6

The number of transferred ICMPv6 messages.

Received, Sent - ICMP messages which the host received and attempted to send.
Both these counters include errors.

ipv6.icmp

The number of ICMPv6 errors and error messages.

InErrors, OutErrors - bad ICMP messages (bad ICMP checksums, bad length, etc.).
InCsumErrors - wrong checksum.

ipv6.icmperrors

The number of ICMPv6 Echo messages.
ipv6.icmpechos

The number of transferred ICMPv6 Router Discovery messages.

Router Solicitations message is sent from a computer host to any routers on the
local area network to request that they advertise their presence on the network.
Router Advertisement message is sent by a router on the local area network to
announce its IP address as available for routing.

ipv6.icmprouter

The number of transferred ICMPv6 Neighbour Discovery messages.

Neighbor Solicitations are used by nodes to determine the link layer address of
a neighbor, or to verify that a neighbor is still reachable via a cached link
layer address. Neighbor Advertisements are used by nodes to respond to a
Neighbor Solicitation message.

ipv6.icmpneighbor

The number of transferred ICMPv6 Multicast Listener Discovery (MLD) messages.
ipv6.icmpmldv2

The number of transferred ICMPv6 messages of certain types.
ipv6.icmptypes

--------------------------------------------------------------------------------

NETWORK INTERFACES

Performance metrics for network interfaces.

Netdata retrieves this data reading the /proc/net/dev file and /sys/class/net/
directory.

ENO1

net.eno1

The amount of traffic transferred by the network interface.
net.eno1

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.eno1

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.eno1

The number of FIFO errors encountered by the network interface.

Inbound - packets dropped because they did not fit into buffers provided by the
host, e.g. packets larger than MTU or next buffer in the ring was not available
for a scatter transfer. Outbound - frame transmission errors due to device FIFO
underrun/underflow. This condition occurs when the device begins transmission of
a frame but is unable to deliver the entire frame to the transmitter in time for
transmission.

net_fifo.eno1

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.eno1

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.

net_duplex.eno1

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.

net_operstate.eno1

The current physical link state of the interface.
net_carrier.eno1

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.eno1

WGBUILD

net.wgbuild

The amount of traffic transferred by the network interface.
net.wgbuild

The number of packets that have been dropped at the network interface level.

net_drops.wgbuild

The current operational state of the interface.

net_operstate.wgbuild

The current physical link state of the interface.
net_carrier.wgbuild

WGMON

net.wgmon

The amount of traffic transferred by the network interface.
net.wgmon

The number of errors encountered by the network interface.

Inbound - bad packets received on this interface. It includes dropped packets
due to invalid length, CRC, frame alignment, and other errors. Outbound -
transmit problems. It includes frames transmission errors due to loss of
carrier, FIFO underrun/underflow, heartbeat, late collisions, and other
problems.

net_errors.wgmon

The number of packets that have been dropped at the network interface level.

net_drops.wgmon

The number of errors encountered by the network interface.

Frames - aggregated counter for dropped packets due to invalid length, FIFO
overflow, CRC, and frame alignment errors. Collisions - collisions during packet
transmissions. Carrier - aggregated counter for frame transmission errors due to
excessive collisions, loss of carrier, device FIFO underrun/underflow,
Heartbeat/SQE Test errors, and late collisions.

net_events.wgmon

The current operational state of the interface.

net_operstate.wgmon

The current physical link state of the interface.
net_carrier.wgmon

WGV4DELIVERY

net.wgv4delivery

The amount of traffic transferred by the network interface.
net.wgv4delivery

The current operational state of the interface.

net_operstate.wgv4delivery

The current physical link state of the interface.
net_carrier.wgv4delivery

WGV6DELIVERY

net.wgv6delivery

The amount of traffic transferred by the network interface.
net.wgv6delivery

The current operational state of the interface.

net_operstate.wgv6delivery

The current physical link state of the interface.
net_carrier.wgv6delivery

ENO2

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.

net_duplex.eno2

The current operational state of the interface.

net_operstate.eno2

The current physical link state of the interface.
net_carrier.eno2

WGMITM

The current operational state of the interface.

net_operstate.wgmitm

The current physical link state of the interface.
net_carrier.wgmitm

--------------------------------------------------------------------------------

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 (since v4.9) and Ignore (since v5.10) are
hardcoded to zeros in the latest kernel.

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

NETLINK

netfilter.netlink_new

netfilter.netlink_changes

netfilter.netlink_expect

netfilter.netlink_errors

netfilter.netlink_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

--------------------------------------------------------------------------------

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

apps.voluntary_ctxt_switches

apps.involuntary_ctxt_switches

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

MEM

Real memory (RAM) used by applications. This does not include shared memory.
apps.mem

apps.rss

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

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

FDS

apps.fds_open_limit

apps.fds_open

apps.fds_files

apps.fds_sockets

apps.fds_pipes

apps.fds_inotifies

apps.fds_eventfds

apps.fds_timerfds

apps.fds_signalfds

apps.fds_eventpolls

apps.fds_other

--------------------------------------------------------------------------------

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

groups.voluntary_ctxt_switches

groups.involuntary_ctxt_switches

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

MEM

Real memory (RAM) used per user group. This does not include shared memory.
groups.mem

groups.rss

Virtual memory allocated per user group since the Netdata restart. Please check
this article for more information.
groups.vmem

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

SWAP

The amount of swapped-out virtual memory by anonymous private pages. This does
not include shared swap memory.
groups.swap

FDS

groups.fds_open_limit

groups.fds_open

groups.fds_files

groups.fds_sockets

groups.fds_pipes

groups.fds_inotifies

groups.fds_eventfds

groups.fds_timerfds

groups.fds_signalfds

groups.fds_eventpolls

groups.fds_other

--------------------------------------------------------------------------------

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

users.voluntary_ctxt_switches

users.involuntary_ctxt_switches

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

MEM

Real memory (RAM) used per user. This does not include shared memory.
users.mem

users.rss

Virtual memory allocated per user since the Netdata restart. Please check this
article for more information.
users.vmem

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

SWAP

The amount of swapped-out virtual memory by anonymous private pages. This does
not include shared swap memory.
users.swap

FDS

users.fds_open_limit

users.fds_open

users.fds_files

users.fds_sockets

users.fds_pipes

users.fds_inotifies

users.fds_eventfds

users.fds_timerfds

users.fds_signalfds

users.fds_eventpolls

users.fds_other

--------------------------------------------------------------------------------

ANOMALY DETECTION

Charts relating to anomaly detection, increased anomalous dimensions or a higher
than usual anomaly_rate could be signs of some abnormal behaviour. Read our
anomaly detection guide for more details.

DIMENSIONS

Total count of dimensions considered anomalous or normal.
anomaly_detection.dimensions_on_1a51230c-254c-11ed-a0ed-0cc47a8686bc

ANOMALY RATE

Percentage of anomalous dimensions.
anomaly_detection.anomaly_rate_on_1a51230c-254c-11ed-a0ed-0cc47a8686bc

ANOMALY DETECTION

Flags (0 or 1) to show when an anomaly event has been triggered by the detector.
anomaly_detection.anomaly_detection_on_1a51230c-254c-11ed-a0ed-0cc47a8686bc

anomaly_detection.ml_running_on_1a51230c-254c-11ed-a0ed-0cc47a8686bc

--------------------------------------------------------------------------------

DOVECOT KURISU

SESSIONS

dovecot_kurisu.lahfa.xyz.sessions

LOGINS

dovecot_kurisu.lahfa.xyz.logins

dovecot_kurisu.lahfa.xyz.auth

COMMANDS

dovecot_kurisu.lahfa.xyz.commands

PAGE FAULTS

dovecot_kurisu.lahfa.xyz.faults

CONTEXT SWITCHES

dovecot_kurisu.lahfa.xyz.context_switches

DISK

dovecot_kurisu.lahfa.xyz.io

NETWORK

dovecot_kurisu.lahfa.xyz.net

SYSTEM

dovecot_kurisu.lahfa.xyz.syscalls

LOOKUPS

dovecot_kurisu.lahfa.xyz.lookup

CACHE

dovecot_kurisu.lahfa.xyz.cache

dovecot_kurisu.lahfa.xyz.auth_cache

--------------------------------------------------------------------------------

SENSORS

Readings of the configured system sensors.

TEMPERATURE

sensors.coretemp-isa-0000_temperature

sensors.i350bb-pci-0400_temperature

sensors.pch_haswell-virtual-0_temperature

--------------------------------------------------------------------------------

LOGIND

Keeps track of user logins and sessions by querying the systemd-logind API.

SESSIONS

Local and remote sessions.
logind.sessions

Sessions of each session type.

Graphical - sessions are running under one of X11, Mir, or Wayland. Console -
sessions are usually regular text mode local logins, but depending on how the
system is configured may have an associated GUI. Other - sessions are those that
do not fall into the above categories (such as sessions for cron jobs or systemd
timer units).

logind.sessions_type

Sessions in each session state.

Online - logged in and running in the background. Closing - nominally logged
out, but some processes belonging to it are still around. Active - logged in and
running in the foreground.

logind.sessions_state

USERS

Users in each user state.

Offline - users are not logged in. Closing - users are in the process of logging
out without lingering. Online - users are logged in, but have no active
sessions. Lingering - users are not logged in, but have one or more services
still running. Active - users are logged in, and have at least one active
session.

logind.users_state

--------------------------------------------------------------------------------

SYSTEMD UNITS SERVICE-UNITS

systemd provides a dependency system between various entities called "units" of
11 different types. Units encapsulate various objects that are relevant for
system boot-up and maintenance. Units may be active (meaning started, bound,
plugged in, depending on the unit type), or inactive (meaning stopped, unbound,
unplugged), as well as in the process of being activated or deactivated, i.e.
between the two states (these states are called activating, deactivating). A
special failed state is available as well, which is very similar to inactive and
is entered when the service failed in some way (process returned error code on
exit, or crashed, an operation timed out, or after too many restarts). For
details, see systemd(1).

SERVICE UNITS

systemdunits_service-units.unit_acme-comments.lahfa.xyz_service_state

systemdunits_service-units.unit_acme-dns.lahfa.xyz_service_state

systemdunits_service-units.unit_acme-ens.wtf_service_state

systemdunits_service-units.unit_acme-fixperms_service_state

systemdunits_service-units.unit_acme-grafana.lahfa.xyz_service_state

systemdunits_service-units.unit_acme-irc.ens.wtf_service_state

systemdunits_service-units.unit_acme-kurisu.lahfa.xyz_service_state

systemdunits_service-units.unit_acme-lockfiles_service_state

systemdunits_service-units.unit_acme-monitoring.lahfa.xyz_service_state

systemdunits_service-units.unit_acme-newsletter.lahfa.xyz_service_state

systemdunits_service-units.unit_acme-notifications.lahfa.xyz_service_state

systemdunits_service-units.unit_acme-ryan.lahfa.xyz_service_state

systemdunits_service-units.unit_acme-selfsigned-ca_service_state

systemdunits_service-units.unit_acme-selfsigned-comments.lahfa.xyz_service_state

systemdunits_service-units.unit_acme-selfsigned-dns.lahfa.xyz_service_state

systemdunits_service-units.unit_acme-selfsigned-ens.wtf_service_state

systemdunits_service-units.unit_acme-selfsigned-grafana.lahfa.xyz_service_state

systemdunits_service-units.unit_acme-selfsigned-irc.ens.wtf_service_state

systemdunits_service-units.unit_acme-selfsigned-kurisu.lahfa.xyz_service_state

systemdunits_service-units.unit_acme-selfsigned-monitoring.lahfa.xyz_service_state

systemdunits_service-units.unit_acme-selfsigned-newsletter.lahfa.xyz_service_state

systemdunits_service-units.unit_acme-selfsigned-notifications.lahfa.xyz_service_state

systemdunits_service-units.unit_acme-selfsigned-ryan.lahfa.xyz_service_state

systemdunits_service-units.unit_acme-selfsigned-spam.lahfa.xyz_service_state

systemdunits_service-units.unit_acme-selfsigned-status.lahfa.xyz_service_state

systemdunits_service-units.unit_acme-selfsigned-webmail.lahfa.xyz_service_state

systemdunits_service-units.unit_acme-spam.lahfa.xyz_service_state

systemdunits_service-units.unit_acme-status.lahfa.xyz_service_state

systemdunits_service-units.unit_acme-webmail.lahfa.xyz_service_state

systemdunits_service-units.unit_activate-virtual-mail-users_service_state

systemdunits_service-units.unit_audit_service_state

systemdunits_service-units.unit_auditd_service_state

systemdunits_service-units.unit_borgbackup-job-amadeus-borg-config_service_state

systemdunits_service-units.unit_borgbackup-job-amadeus-master-secrets_service_state

systemdunits_service-units.unit_borgbackup-job-amadeus-system_service_state

systemdunits_service-units.unit_borgbackup-job-dgnum.eu-vmail_service_state

systemdunits_service-units.unit_borgbackup-job-dkimkeys_service_state

systemdunits_service-units.unit_borgbackup-job-infra.dgnum.eu-vmail_service_state

systemdunits_service-units.unit_borgbackup-job-infra.lahfa.xyz-vmail_service_state

systemdunits_service-units.unit_borgbackup-job-lahfa.xyz-vmail_service_state

systemdunits_service-units.unit_borgbackup-job-mangaki.fr-vmail_service_state

systemdunits_service-units.unit_borgbackup-job-nixos.paris-vmail_service_state

systemdunits_service-units.unit_borgbackup-job-recursor.wf-vmail_service_state

systemdunits_service-units.unit_borgbackup-job-sieve-scripts_service_state

systemdunits_service-units.unit_borgbackup-job-thelounge-irc.ens.wtf_service_state

systemdunits_service-units.unit_charybdis-config-reload_service_state

systemdunits_service-units.unit_charybdis_service_state

systemdunits_service-units.unit_dbus_service_state

systemdunits_service-units.unit_dhcpcd_service_state

systemdunits_service-units.unit_dhparams-gen-charybdis_service_state

systemdunits_service-units.unit_dhparams-gen-dovecot2_service_state

systemdunits_service-units.unit_dhparams-init_service_state

systemdunits_service-units.unit_dovecot2_service_state

systemdunits_service-units.unit_dovecot-fts-xapian-optimize_service_state

systemdunits_service-units.unit_emergency_service_state

systemdunits_service-units.unit_fail2ban_service_state

systemdunits_service-units.unit_firewall_service_state

systemdunits_service-units.unit_generate-shutdown-ramfs_service_state

systemdunits_service-units.unit_getty@tty1_service_state

systemdunits_service-units.unit_grafana_service_state

systemdunits_service-units.unit_isso_service_state

systemdunits_service-units.unit_kmod-static-nodes_service_state

systemdunits_service-units.unit_kres-cache-gc_service_state

systemdunits_service-units.unit_kresd@1_service_state

systemdunits_service-units.unit_listmonk_service_state

systemdunits_service-units.unit_logrotate-checkconf_service_state

systemdunits_service-units.unit_logrotate_service_state

systemdunits_service-units.unit_modprobe@configfs_service_state

systemdunits_service-units.unit_modprobe@drm_service_state

systemdunits_service-units.unit_modprobe@efi_pstore_service_state

systemdunits_service-units.unit_modprobe@fuse_service_state

systemdunits_service-units.unit_mount-pstore_service_state

systemdunits_service-units.unit_netdata_service_state

systemdunits_service-units.unit_network-addresses-eno1_service_state

systemdunits_service-units.unit_network-addresses-eno2_service_state

systemdunits_service-units.unit_network-local-commands_service_state

systemdunits_service-units.unit_network-setup_service_state

systemdunits_service-units.unit_nginx-config-reload_service_state

systemdunits_service-units.unit_nginx_service_state

systemdunits_service-units.unit_nix-daemon_service_state

systemdunits_service-units.unit_nscd_service_state

systemdunits_service-units.unit_nsd_service_state

systemdunits_service-units.unit_ntfy-sh_service_state

systemdunits_service-units.unit_opendkim_service_state

systemdunits_service-units.unit_phpfpm-roundcube_service_state

systemdunits_service-units.unit_postfix-setup_service_state

systemdunits_service-units.unit_postfix_service_state

systemdunits_service-units.unit_postgresql_service_state

systemdunits_service-units.unit_redis-rspamd_service_state

systemdunits_service-units.unit_refresh-immae-zones_service_state

systemdunits_service-units.unit_reload-systemd-vconsole-setup_service_state

systemdunits_service-units.unit_rescue_service_state

systemdunits_service-units.unit_resolvconf_service_state

systemdunits_service-units.unit_roundcube-setup_service_state

systemdunits_service-units.unit_rspamd_service_state

systemdunits_service-units.unit_save-hwclock_service_state

systemdunits_service-units.unit_smartd_service_state

systemdunits_service-units.unit_sniproxy_service_state

systemdunits_service-units.unit_sshd_service_state

systemdunits_service-units.unit_systemd-ask-password-console_service_state

systemdunits_service-units.unit_systemd-ask-password-wall_service_state

systemdunits_service-units.unit_systemd-fsck-root_service_state

systemdunits_service-units.unit_systemd-journal-catalog-update_service_state

systemdunits_service-units.unit_systemd-journal-flush_service_state

systemdunits_service-units.unit_systemd-journald_service_state

systemdunits_service-units.unit_systemd-logind_service_state

systemdunits_service-units.unit_systemd-modules-load_service_state

systemdunits_service-units.unit_systemd-oomd_service_state

systemdunits_service-units.unit_systemd-pstore_service_state

systemdunits_service-units.unit_systemd-random-seed_service_state

systemdunits_service-units.unit_systemd-remount-fs_service_state

systemdunits_service-units.unit_systemd-rfkill_service_state

systemdunits_service-units.unit_systemd-sysctl_service_state

systemdunits_service-units.unit_systemd-timesyncd_service_state

systemdunits_service-units.unit_systemd-tmpfiles-clean_service_state

systemdunits_service-units.unit_systemd-tmpfiles-setup-dev-early_service_state

systemdunits_service-units.unit_systemd-tmpfiles-setup-dev_service_state

systemdunits_service-units.unit_systemd-tmpfiles-setup_service_state

systemdunits_service-units.unit_systemd-udev-trigger_service_state

systemdunits_service-units.unit_systemd-udevd_service_state

systemdunits_service-units.unit_systemd-update-done_service_state

systemdunits_service-units.unit_systemd-update-utmp_service_state

systemdunits_service-units.unit_systemd-user-sessions_service_state

systemdunits_service-units.unit_systemd-vconsole-setup_service_state

systemdunits_service-units.unit_thelounge_service_state

systemdunits_service-units.unit_tor_service_state

systemdunits_service-units.unit_unbound_service_state

systemdunits_service-units.unit_uptime-kuma_service_state

systemdunits_service-units.unit_user-runtime-dir@0_service_state

systemdunits_service-units.unit_user-runtime-dir@1000_service_state

systemdunits_service-units.unit_user@0_service_state

systemdunits_service-units.unit_user@1000_service_state

systemdunits_service-units.unit_wireguard-wgbuild-key_service_state

systemdunits_service-units.unit_wireguard-wgbuild-peer-++QmmJIXDDUrb9RSBfkQylrmNawAvhupXPt26wkAqnQ=_service_state

systemdunits_service-units.unit_wireguard-wgbuild_service_state

systemdunits_service-units.unit_wireguard-wgmitm-key_service_state

systemdunits_service-units.unit_wireguard-wgmitm-peer-VxqSLLIPhNQ7Vx4EA1csSFNL7TA5L--pJd1Fr53cKh8=_service_state

systemdunits_service-units.unit_wireguard-wgmitm-peer-wtPGcFerQmDdQYFjFLgPWczMEJ4wFGpFdFeo1+cseFE=_service_state

systemdunits_service-units.unit_wireguard-wgmitm_service_state

systemdunits_service-units.unit_wireguard-wgmon-key_service_state

systemdunits_service-units.unit_wireguard-wgmon-peer-1WfzmH1SYppDJoi2N97gBb4Bm2qMdcM127sedhVplD4=_service_state

systemdunits_service-units.unit_wireguard-wgmon-peer-6yTZwoo3ciT5uwtQ5ISKrd2nLNN7Q4ymtY-rLUA68k8=_service_state

systemdunits_service-units.unit_wireguard-wgmon-peer-77rph6FdBRaJvNiSXP+E6ABqL0g0vNJ-PcfJuYBc1V0=_service_state

systemdunits_service-units.unit_wireguard-wgmon-peer-+F0in1mIPucW6NUUX7-B+r1t9hofTFAus0OQbYsV1iI=_service_state

systemdunits_service-units.unit_wireguard-wgmon-peer-C1nFb1UXW2cpkRXa1d6yL4HtkFWZAuR6Sk7B1K9lPR8=_service_state

systemdunits_service-units.unit_wireguard-wgmon-peer-cG2WX127lqrzm8qAV60YxTjqk-jlB2PT+gqoWkPymUQ=_service_state

systemdunits_service-units.unit_wireguard-wgmon-peer-clMY-L3tR14-imMows6uXGITQLA+nGrF-TNJ11TpWhY=_service_state

systemdunits_service-units.unit_wireguard-wgmon-peer-eLVgRYeY9Any4zhUFdcBLKvxOm5r5HDRB-3j8QQI6iM=_service_state

systemdunits_service-units.unit_wireguard-wgmon-peer-hqkwp01dM2wsbXFkdIMyTUDR-Yu4+7eBVFrOC+CMonc=_service_state

systemdunits_service-units.unit_wireguard-wgmon-peer-jJGdOMU3Y5kzTS2yB60sa431h6zKbyFRWALo+bFjtTk=_service_state

systemdunits_service-units.unit_wireguard-wgmon-peer-kkq8b3u4ma-S3iLeVQ02uHgFTPvHBdr62yRqszzqtxA=_service_state

systemdunits_service-units.unit_wireguard-wgmon-peer-SZ6-Wa05W4QXdZoINod83JWnEiIl8IWqFUdFlCONLUw=_service_state

systemdunits_service-units.unit_wireguard-wgmon-peer-tq5HUeYu4ZpAVtflq77a4Kt-aeepC0t3bv1TN9957wo=_service_state

systemdunits_service-units.unit_wireguard-wgmon-peer-u12JkgsSP2jeUq26mu++7lv+1Q7SkP4fMURjSABdOUo=_service_state

systemdunits_service-units.unit_wireguard-wgmon-peer-ZD153pkaDeuGMi0Bx1LDw4gI+gKyVdwsoZWq1zeMVSk=_service_state

systemdunits_service-units.unit_wireguard-wgmon_service_state

systemdunits_service-units.unit_wireguard-wgv4delivery-key_service_state

systemdunits_service-units.unit_wireguard-wgv4delivery-peer-VSPHmUC++b9hdjBTYl3IMg9GJ8cvCoHckP3SrnCJ7Q0=_service_state

systemdunits_service-units.unit_wireguard-wgv4delivery_service_state

systemdunits_service-units.unit_wireguard-wgv6delivery-key_service_state

systemdunits_service-units.unit_wireguard-wgv6delivery-peer-VSPHmUC++b9hdjBTYl3IMg9GJ8cvCoHckP3SrnCJ7Q0=_service_state

systemdunits_service-units.unit_wireguard-wgv6delivery_service_state

--------------------------------------------------------------------------------

WHOISQUERY ENS-WTF

EXPIRATION TIME

whoisquery_ens-wtf.time_until_expiration

--------------------------------------------------------------------------------

WHOISQUERY HACKENS-ORG

EXPIRATION TIME

whoisquery_hackens-org.time_until_expiration

--------------------------------------------------------------------------------

WHOISQUERY INDUCTIVE-WF

EXPIRATION TIME

whoisquery_inductive-wf.time_until_expiration

--------------------------------------------------------------------------------

WHOISQUERY LAHFA-FR

EXPIRATION TIME

whoisquery_lahfa-fr.time_until_expiration

--------------------------------------------------------------------------------

WHOISQUERY LAHFA-XYZ

EXPIRATION TIME

whoisquery_lahfa-xyz.time_until_expiration

--------------------------------------------------------------------------------

WHOISQUERY MANGAKI-FR

EXPIRATION TIME

whoisquery_mangaki-fr.time_until_expiration

--------------------------------------------------------------------------------

WHOISQUERY NEWTYPE-FR

EXPIRATION TIME

whoisquery_newtype-fr.time_until_expiration

--------------------------------------------------------------------------------

WHOISQUERY NIXOS-PARIS

EXPIRATION TIME

whoisquery_nixos-paris.time_until_expiration

--------------------------------------------------------------------------------

WHOISQUERY WG2-DEV

EXPIRATION TIME

whoisquery_wg2-dev.time_until_expiration

--------------------------------------------------------------------------------

IPMI

The Intelligent Platform Management Interface (IPMI) is a set of computer
interface specifications for an autonomous computer subsystem that provides
management and monitoring capabilities independently of the host system's CPU,
firmware (BIOS or UEFI) and operating system.

STATES

ipmi.sensor_state_i4_n1_t2_u1_CPU Temp

ipmi.sensor_state_i71_n11_t2_u1_System Temp

ipmi.sensor_state_i138_n12_t2_u1_Peripheral Temp

ipmi.sensor_state_i205_n176_t2_u1_DIMMA1 Temp

ipmi.sensor_state_i272_n177_t255_u1_DIMMA2 Temp

ipmi.sensor_state_i339_n180_t2_u1_DIMMB1 Temp

ipmi.sensor_state_i406_n181_t255_u1_DIMMB2 Temp

ipmi.sensor_state_i540_n32_t2_u3_Vcpu

ipmi.sensor_state_i607_n36_t2_u3_VDIMMAB

ipmi.sensor_state_i674_n48_t2_u3_12V

ipmi.sensor_state_i741_n49_t2_u3_5VCC

ipmi.sensor_state_i808_n50_t2_u3_3.3VCC

ipmi.sensor_state_i875_n51_t2_u3_VBAT

ipmi.sensor_state_i942_n55_t2_u3_5V Dual

ipmi.sensor_state_i1009_n57_t2_u3_3.3VSB

ipmi.sensor_state_i1076_n60_t2_u3_1.5V PCH

ipmi.sensor_state_i1143_n61_t2_u3_1.2V BMC

ipmi.sensor_state_i1210_n62_t2_u3_1.05V PCH

ipmi.sensor_state_i473_n65_t2_u5_FAN1

ipmi.sensor_state_i1277_n171_t255_u0_PS Status

TEMPERATURES

ipmi.sensor_temperature_c_i4_n1_t2_u1_CPU Temp

ipmi.sensor_temperature_c_i71_n11_t2_u1_System Temp

ipmi.sensor_temperature_c_i138_n12_t2_u1_Peripheral Temp

ipmi.sensor_temperature_c_i205_n176_t2_u1_DIMMA1 Temp

ipmi.sensor_temperature_c_i339_n180_t2_u1_DIMMB1 Temp

VOLTAGES

ipmi.sensor_voltage_i540_n32_t2_u3_Vcpu

ipmi.sensor_voltage_i607_n36_t2_u3_VDIMMAB

ipmi.sensor_voltage_i674_n48_t2_u3_12V

ipmi.sensor_voltage_i741_n49_t2_u3_5VCC

ipmi.sensor_voltage_i808_n50_t2_u3_3.3VCC

ipmi.sensor_voltage_i875_n51_t2_u3_VBAT

ipmi.sensor_voltage_i942_n55_t2_u3_5V Dual

ipmi.sensor_voltage_i1009_n57_t2_u3_3.3VSB

ipmi.sensor_voltage_i1076_n60_t2_u3_1.5V PCH

ipmi.sensor_voltage_i1143_n61_t2_u3_1.2V BMC

ipmi.sensor_voltage_i1210_n62_t2_u3_1.05V PCH

FANS

ipmi.sensor_fan_speed_i473_n65_t2_u5_FAN1

EVENTS

ipmi.events

--------------------------------------------------------------------------------

NETDATA MONITORING

Performance metrics for the operation of netdata itself and its plugins.

NETDATA

netdata.server_cpu

netdata.memory

netdata.memory_buffers

netdata.uptime

API

netdata.clients

netdata.requests

netdata.net

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_read

netdata.db_points_stored

SQLITE3

netdata.sqlite3_queries

netdata.sqlite3_queries_by_status

netdata.sqlite3_rows

netdata.sqlite3_metatada_cache

netdata.sqlite3_context_cache

STATSD

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

DBENGINE MEMORY

netdata.dbengine_memory

netdata.dbengine_buffers

DBENGINE METRICS

netdata.dbengine_metrics

netdata.dbengine_metrics_registry_operations

netdata.dbengine_metrics_registry_references

DBENGINE QUERY ROUTER

netdata.dbengine_cache_hit_ratio

netdata.dbengine_queries

netdata.dbengine_queries_running

netdata.dbengine_query_pages_metadata_source

netdata.dbengine_query_pages_data_source

netdata.dbengine_query_next_page

netdata.dbengine_query_next_page_issues

netdata.dbengine_query_pages_disk_load

netdata.dbengine_events

netdata.dbengine_prep_timings

netdata.dbengine_query_timings

DBENGINE MAIN CACHE

netdata.dbengine_main_cache_hit_ratio

netdata.dbengine_main_cache_operations

netdata.dbengine_main_cache_memory

netdata.dbengine_main_target_memory

netdata.dbengine_main_cache_pages

netdata.dbengine_main_cache_memory_changes

netdata.dbengine_main_cache_memory_migrations

netdata.dbengine_main_cache_events

netdata.dbengine_main_waste_events

netdata.dbengine_main_cache_workers

DBENGINE OPEN CACHE

netdata.dbengine_open_cache_hit_ratio

netdata.dbengine_open_cache_operations

netdata.dbengine_open_cache_memory

netdata.dbengine_open_target_memory

netdata.dbengine_open_cache_pages

netdata.dbengine_open_cache_memory_changes

netdata.dbengine_open_cache_memory_migrations

netdata.dbengine_open_cache_events

netdata.dbengine_open_waste_events

netdata.dbengine_open_cache_workers

DBENGINE EXTENT CACHE

netdata.dbengine_extent_cache_hit_ratio

netdata.dbengine_extent_cache_operations

netdata.dbengine_extent_cache_memory

netdata.dbengine_extent_target_memory

netdata.dbengine_extent_cache_pages

netdata.dbengine_extent_cache_memory_changes

netdata.dbengine_extent_cache_memory_migrations

netdata.dbengine_extent_cache_events

netdata.dbengine_extent_waste_events

netdata.dbengine_extent_cache_workers

DBENGINE IO

netdata.dbengine_compression_ratio

netdata.dbengine_io_throughput

netdata.dbengine_io_operations

netdata.dbengine_global_errors

netdata.dbengine_global_file_descriptors

APPS.PLUGIN

netdata.apps_cpu

netdata.apps_sizes

netdata.apps_fix

netdata.apps_children_fix

GO.D

netdata.execution_time_of_logind

netdata.execution_time_of_systemdunits_service-units

netdata.execution_time_of_whoisquery_ens-wtf

netdata.execution_time_of_whoisquery_hackens-org

netdata.execution_time_of_whoisquery_inductive-wf

netdata.execution_time_of_whoisquery_lahfa-fr

netdata.execution_time_of_whoisquery_lahfa-xyz

netdata.execution_time_of_whoisquery_mangaki-fr

netdata.execution_time_of_whoisquery_newtype-fr

netdata.execution_time_of_whoisquery_nixos-paris

netdata.execution_time_of_whoisquery_wg2-dev

PYTHON.D

netdata.runtime_dovecot_kurisu.lahfa.xyz

netdata.runtime_sensors

PLUGINS

netdata.freeipmi_availability_status

MACHINE LEARNING

netdata.machine_learning_status_on_1a51230c-254c-11ed-a0ed-0cc47a8686bc

netdata.ml_models_consulted

netdata.metric_types_on_1a51230c-254c-11ed-a0ed-0cc47a8686bc

netdata.training_status_on_1a51230c-254c-11ed-a0ed-0cc47a8686bc

netdata.training_queue_0_stats

netdata.training_queue_1_stats

netdata.training_queue_2_stats

netdata.training_queue_3_stats

netdata.training_queue_0_time_stats

netdata.training_queue_1_time_stats

netdata.training_queue_2_time_stats

netdata.training_queue_3_time_stats

netdata.training_queue_0_results

netdata.training_queue_1_results

netdata.training_queue_2_results

netdata.training_queue_3_results

DICTIONARIES COLLECTORS

netdata.dictionaries.collectors.dictionaries

netdata.dictionaries.collectors.items

netdata.dictionaries.collectors.ops

netdata.dictionaries.collectors.callbacks

netdata.dictionaries.collectors.memory

DICTIONARIES CONTEXTS

netdata.dictionaries.context.dictionaries

netdata.dictionaries.context.items

netdata.dictionaries.context.ops

netdata.dictionaries.context.callbacks

netdata.dictionaries.context.memory

DICTIONARIES FUNCTIONS

netdata.dictionaries.functions.dictionaries

netdata.dictionaries.functions.items

netdata.dictionaries.functions.ops

netdata.dictionaries.functions.callbacks

netdata.dictionaries.functions.memory

DICTIONARIES HEALTH

netdata.dictionaries.health.dictionaries

netdata.dictionaries.health.items

netdata.dictionaries.health.ops

netdata.dictionaries.health.callbacks

netdata.dictionaries.health.memory

DICTIONARIES HOSTS

netdata.dictionaries.rrdhost.dictionaries

netdata.dictionaries.rrdhost.items

netdata.dictionaries.rrdhost.ops

netdata.dictionaries.rrdhost.memory

netdata.dictionaries.rrdhost.spins

DICTIONARIES LABELS

netdata.dictionaries.labels.dictionaries

netdata.dictionaries.labels.items

netdata.dictionaries.labels.ops

netdata.dictionaries.labels.callbacks

netdata.dictionaries.labels.memory

DICTIONARIES OTHER

netdata.dictionaries.other.dictionaries

netdata.dictionaries.other.ops

netdata.dictionaries.other.memory

DICTIONARIES RRD

netdata.dictionaries.rrdset_rrddim.dictionaries

netdata.dictionaries.rrdset_rrddim.items

netdata.dictionaries.rrdset_rrddim.ops

netdata.dictionaries.rrdset_rrddim.callbacks

netdata.dictionaries.rrdset_rrddim.memory

netdata.dictionaries.rrdset_rrddim.spins

HEARTBEAT

netdata.heartbeat

STRINGS

netdata.strings_ops

netdata.strings_entries

netdata.strings_memory

WORKERS

netdata.workers_cpu

WORKERS ACLK HOST SYNC

netdata.workers_time_aclksync

netdata.workers_cpu_aclksync

netdata.workers_jobs_by_type_aclksync

netdata.workers_busy_time_by_type_aclksync

WORKERS CONTEXTS

netdata.workers_time_rrdcontext

netdata.workers_cpu_rrdcontext

netdata.workers_jobs_by_type_rrdcontext

netdata.workers_busy_time_by_type_rrdcontext

netdata.workers_rrdcontext_value_hub_queue_size

netdata.workers_rrdcontext_value_post_processing_queue_size

WORKERS DBENGINE INSTANCES

netdata.workers_time_dbengine

netdata.workers_cpu_dbengine

netdata.workers_jobs_by_type_dbengine

netdata.workers_busy_time_by_type_dbengine

netdata.workers_dbengine_value_opcodes_waiting

netdata.workers_dbengine_value_works_dispatched

netdata.workers_dbengine_value_works_executing

WORKERS GLOBAL STATISTICS

netdata.workers_time_stats

netdata.workers_cpu_stats

netdata.workers_jobs_by_type_stats

netdata.workers_busy_time_by_type_stats

netdata.workers_threads_stats

WORKERS HEALTH ALARMS

netdata.workers_time_health

netdata.workers_cpu_health

netdata.workers_jobs_by_type_health

netdata.workers_busy_time_by_type_health

WORKERS LIBUV THREADPOOL

netdata.workers_time_libuv

netdata.workers_cpu_libuv

netdata.workers_jobs_by_type_libuv

netdata.workers_busy_time_by_type_libuv

netdata.workers_threads_libuv

WORKERS METADATA SYNC

netdata.workers_time_metasync

netdata.workers_cpu_metasync

netdata.workers_jobs_by_type_metasync

netdata.workers_busy_time_by_type_metasync

WORKERS ML DETECTION

netdata.workers_time_mldetect

netdata.workers_cpu_mldetect

netdata.workers_jobs_by_type_mldetect

netdata.workers_busy_time_by_type_mldetect

WORKERS ML TRAINING

netdata.workers_time_mltrain

netdata.workers_cpu_mltrain

netdata.workers_jobs_by_type_mltrain

netdata.workers_busy_time_by_type_mltrain

netdata.workers_threads_mltrain

WORKERS PLUGIN CGROUPS

netdata.workers_time_cgroups

netdata.workers_cpu_cgroups

netdata.workers_jobs_by_type_cgroups

netdata.workers_busy_time_by_type_cgroups

WORKERS PLUGIN CGROUPS FIND

netdata.workers_time_cgroupsdisc

netdata.workers_cpu_cgroupsdisc

netdata.workers_jobs_by_type_cgroupsdisc

netdata.workers_busy_time_by_type_cgroupsdisc

WORKERS PLUGIN DISKSPACE

netdata.workers_time_diskspace

netdata.workers_cpu_diskspace

netdata.workers_jobs_by_type_diskspace

netdata.workers_busy_time_by_type_diskspace

WORKERS PLUGIN IDLEJITTER

netdata.workers_time_idlejitter

netdata.workers_cpu_idlejitter

netdata.workers_jobs_by_type_idlejitter

netdata.workers_busy_time_by_type_idlejitter

WORKERS PLUGIN PROC

netdata.workers_time_proc

netdata.workers_cpu_proc

netdata.workers_jobs_by_type_proc

netdata.workers_busy_time_by_type_proc

WORKERS PLUGIN PROC NETDEV

netdata.workers_time_netdev

netdata.workers_cpu_netdev

netdata.workers_jobs_by_type_netdev

netdata.workers_busy_time_by_type_netdev

WORKERS PLUGIN STATSD

netdata.workers_time_statsd

netdata.workers_cpu_statsd

netdata.workers_jobs_by_type_statsd

netdata.workers_busy_time_by_type_statsd

WORKERS PLUGIN STATSD FLUSH

netdata.workers_time_statsdflush

netdata.workers_cpu_statsdflush

netdata.workers_jobs_by_type_statsdflush

netdata.workers_busy_time_by_type_statsdflush

WORKERS PLUGIN TC

netdata.workers_time_tc

netdata.workers_cpu_tc

netdata.workers_jobs_by_type_tc

netdata.workers_busy_time_by_type_tc

netdata.workers_tc_value_tc_script_execution_time

netdata.workers_tc_value_number_of_devices

netdata.workers_tc_value_number_of_classes

WORKERS PLUGIN TIMEX

netdata.workers_time_timex

netdata.workers_cpu_timex

netdata.workers_jobs_by_type_timex

netdata.workers_busy_time_by_type_timex

WORKERS PLUGINS.D

netdata.workers_time_pluginsd

netdata.workers_cpu_pluginsd

netdata.workers_jobs_by_type_pluginsd

netdata.workers_busy_time_by_type_pluginsd

netdata.workers_threads_pluginsd

WORKERS REPLICATION SENDER

netdata.workers_time_replication

netdata.workers_cpu_replication

netdata.workers_jobs_by_type_replication

netdata.workers_busy_time_by_type_replication

netdata.workers_replication_value_pending_requests

netdata.workers_replication_value_no_room_requests

netdata.workers_replication_value_completion

netdata.workers_replication_rate_added_requests

netdata.workers_replication_rate_finished_requests

netdata.workers_replication_rate_sender_resets

netdata.workers_replication_value_senders_full

WORKERS SERVICE

netdata.workers_time_service

netdata.workers_cpu_service

netdata.workers_jobs_by_type_service

netdata.workers_busy_time_by_type_service

WORKERS STREAMING RECEIVE

netdata.workers_time_streamrcv

netdata.workers_cpu_streamrcv

netdata.workers_jobs_by_type_streamrcv

netdata.workers_busy_time_by_type_streamrcv

netdata.workers_threads_streamrcv

netdata.workers_streamrcv_value_replication_completion

netdata.workers_streamrcv_rate_uncompressed_bytes

netdata.workers_streamrcv_rate_received_bytes

WORKERS WEB SERVER

netdata.workers_time_web

netdata.workers_cpu_web

netdata.workers_jobs_by_type_web

netdata.workers_busy_time_by_type_web

netdata.workers_threads_web

--------------------------------------------------------------------------------

* System Overview
* cpu
* load
* disk
* ram
* network
* processes
* idlejitter
* interrupts
* softirqs
* softnet
* entropy
* files
* uptime
* clock synchronization
* ipc semaphores
* ipc shared memory
* CPUs
* utilization
* interrupts
* softirqs
* softnet
* throttling
* cpufreq
* Memory
* overview
* OOM kills
* swap
* page faults
* writeback
* kernel
* slab
* reclaiming
* cma
* hugepages
* edac
* Disks
* amadeus-root-1
* amadeus-root-2
* dev-disk-byx2...fe235bax2d03
* ipxe
* sda
* sdb
* /boot
* /dev
* /dev/shm
* /run
* /run/wrappers
* BTRFS filesystem
* 0488f610-2280...8caf41d5082b
* 6c1658a1-4674...85ca8498ac4c
* Networking Stack
* tcp
* broadcast
* ecn
* IPv4 Networking
* sockets
* packets
* errors
* icmp
* tcp
* udp
* raw
* fragments
* IPv6 Networking
* packets
* errors
* fragments6
* tcp6
* udp6
* udplite6
* raw6
* multicast6
* icmp6
* Network Interfaces
* eno1
* wgbuild
* wgmon
* wgv4delivery
* wgv6delivery
* eno2
* wgmitm
* Firewall (netfilter)
* connection tracker
* netlink
* systemd Services
* cpu
* mem
* swap
* disk
* Applications
* cpu
* disk
* mem
* processes
* swap
* fds
* User Groups
* cpu
* disk
* mem
* processes
* swap
* fds
* Users
* cpu
* disk
* mem
* processes
* swap
* fds
* Anomaly Detection
* dimensions
* anomaly rate
* anomaly detection
* Dovecot kurisu
* sessions
* logins
* commands
* page faults
* context switches
* disk
* network
* system
* lookups
* cache
* Sensors
* temperature
* Logind
* sessions
* users
* systemd units service-units
* service units
* whoisquery ens-wtf
* expiration time
* whoisquery hackens-org
* expiration time
* whoisquery inductive-wf
* expiration time
* whoisquery lahfa-fr
* expiration time
* whoisquery lahfa-xyz
* expiration time
* whoisquery mangaki-fr
* expiration time
* whoisquery newtype-fr
* expiration time
* whoisquery nixos-paris
* expiration time
* whoisquery wg2-dev
* expiration time
* IPMI
* states
* temperatures
* voltages
* fans
* events
* Netdata Monitoring
* netdata
* api
* queries
* sqlite3
* statsd
* dbengine memory
* dbengine metrics
* dbengine query router
* dbengine main cache
* dbengine open cache
* dbengine extent cache
* dbengine io
* apps.plugin
* go.d
* python.d
* plugins
* machine learning
* dictionaries collectors
* dictionaries contexts
* dictionaries functions
* dictionaries health
* dictionaries hosts
* dictionaries labels
* dictionaries other
* dictionaries rrd
* heartbeat
* strings
* workers
* workers aclk host sync
* workers contexts
* workers dbengine instances
* workers global statistics
* workers health alarms
* workers libuv threadpool
* workers metadata sync
* workers ML detection
* workers ML training
* workers plugin cgroups
* workers plugin cgroups find
* workers plugin diskspace
* workers plugin idlejitter
* workers plugin proc
* workers plugin proc netdev
* workers plugin statsd
* workers plugin statsd flush
* workers plugin tc
* workers plugin timex
* workers plugins.d
* workers replication sender
* workers service
* workers streaming receive
* workers web server
* Add more charts
* Add more alarms
* Every second, Netdata collects 6,189 metrics on amadeus, presents them in 927
charts and monitors them with 173 alarms.
netdata
v1.42.4
* Do you like Netdata?
Give us a star!

And share the word!

Netdata

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 sequentially download all the charts, to avoid
congesting network and server resources.
Please, do not print netdata dashboards on paper!

Print Close
×

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 transferred 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.42.4

You already have the latest netdata!

No update yet?
We probably need some motivation to keep going on!

If you haven't already, give netdata a at its github page.

--------------------------------------------------------------------------------

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
×

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.

LEARN ABOUT NETDATA CLOUD!

Netdata Cloud is a FREE service that complements the Netdata Agent, to provide:
* Infrastructure level dashboards (each chart aggregates data from multiple
nodes)
* Central dispatch of alert notifications
* Custom dashboards editor
* Intelligence assisted troubleshooting, to help surface the root cause of
issues

Have a look, you will be surprised!

Remember my choice
Wow! Let’s go to Netdata Cloud
Later, stay at the agent dashboard

monitoring.lahfa.xyz Open in urlscan Pro 2001:bc8:38ee::1 Public Scan

Form analysis 5 forms found in the DOM

#

Text Content

monitoring.lahfa.xyz Open in urlscan Pro
2001:bc8:38ee::1 Public Scan

Form analysis
5 forms found in the DOM