tc class utilization using its ' +
'tc-helper plugin. ' +
'If you also use FireQOS for setting up QoS, ' +
'netdata automatically collects interface and class names. If your QoS configuration includes overheads ' +
'calculation, the values shown here will include these overheads (the total bandwidth for the same ' +
'interface as reported in the Network Interfaces section, will be lower than the total bandwidth ' +
'reported here). QoS data collection may have a slight time difference compared to the interface ' +
'(QoS data collection uses a BASH script, so a shift in data collection of a few milliseconds ' +
'should be justified).'
},
'net': {
title: 'Network Interfaces',
icon: '',
info: 'Performance metrics for network interfaces.
'+ 'Netdata retrieves this data reading the /proc/net/dev file and /sys/class/net/ directory.
Performance and exception statistics for '+
'Infiniband ports. '+
'The individual port and hardware counter descriptions can be found in the '+
'Mellanox knowledge base.'
},
'wireless': {
title: 'Wireless Interfaces',
icon: '',
info: 'Performance metrics for wireless interfaces.'
},
'ip': {
title: 'Networking Stack',
icon: '',
info: function (os) {
if (os === "linux")
return '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.';
else
return 'Metrics for the networking stack of the system.';
}
},
'ipv4': {
title: 'IPv4 Networking',
icon: '',
info: '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).'
},
'ipv6': {
title: 'IPv6 Networking',
icon: '',
info: '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.'
},
'sctp': {
title: 'SCTP Networking',
icon: '',
info: '
Stream Control Transmission Protocol (SCTP) '+ 'is a computer network protocol which operates at the transport layer and serves a role similar to the popular '+ 'protocols TCP and UDP. SCTP provides some of the features of both UDP and TCP: it is message-oriented like UDP '+ 'and ensures reliable, in-sequence transport of messages with congestion control like TCP. '+ 'It differs from those protocols by providing multi-homing and redundant paths to increase resilience and reliability.
'+ 'Netdata collects SCTP metrics reading the /proc/net/sctp/snmp file.
IPVS (IP Virtual Server) '+ 'implements transport-layer load balancing inside the Linux kernel, so called Layer-4 switching. '+ 'IPVS running on a host acts as a load balancer at the front of a cluster of real servers, '+ 'it can direct requests for TCP/UDP based services to the real servers, '+ 'and makes services of the real servers to appear as a virtual service on a single IP address.
'+ 'Netdata collects summary statistics, reading /proc/net/ip_vs_stats. '+
'To display the statistics information of services and their servers, run ipvsadm -Ln --stats '+
'or ipvsadm -Ln --rate for the rate statistics. '+
'For details, see ipvsadm(8).
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.'
},
'mount': {
title: 'Mount Points',
icon: '',
info: ''
},
'mdstat': {
title: 'MD arrays',
icon: '',
info: 'RAID devices are virtual devices created from two or more real block devices. '+ 'Linux Software RAID devices are '+ 'implemented through the md (Multiple Devices) device driver.
'+ 'Netdata monitors the current status of MD arrays reading /proc/mdstat and '+
'/sys/block/%s/md/mismatch_cnt files.
ping, but much better performing when pinging multiple hosts. fping versions after 3.15 can be directly used as netdata plugins.'
},
'gearman': {
title: 'Gearman',
icon: '',
info: 'Gearman is a job server that allows you to do work in parallel, to load balance processing, and to call functions between languages.'
},
'ioping': {
title: 'ioping',
icon: '',
info: 'Disk latency statistics, via ioping. ioping is a program to read/write data probes from/to a disk.'
},
'httpcheck': {
title: 'Http Check',
icon: '',
info: 'Web Service availability and latency monitoring using HTTP checks. This plugin is a specialized version of the port check plugin.'
},
'memcached': {
title: 'memcached',
icon: '',
info: 'Performance metrics for memcached. Memcached is a general-purpose distributed memory caching system. It is often used to speed up dynamic database-driven websites by caching data and objects in RAM to reduce the number of times an external data source (such as a database or API) must be read.'
},
'monit': {
title: 'monit',
icon: '',
info: 'Statuses of checks in monit. Monit is a utility for managing and monitoring processes, programs, files, directories and filesystems on a Unix system. Monit conducts automatic maintenance and repair and can execute meaningful causal actions in error situations.'
},
'mysql': {
title: 'MySQL',
icon: '',
info: 'Performance metrics for mysql, the open-source relational database management system (RDBMS).'
},
'postgres': {
title: 'Postgres',
icon: '',
info: 'Performance metrics for PostgresSQL, the object-relational database (ORDBMS).'
},
'redis': {
title: 'Redis',
icon: '',
info: 'Performance metrics for redis. Redis (REmote DIctionary Server) is a software project that implements data structure servers. It is open-source, networked, in-memory, and stores keys with optional durability.'
},
'rethinkdbs': {
title: 'RethinkDB',
icon: '',
info: 'Performance metrics for rethinkdb. RethinkDB is the first open-source scalable database built for realtime applications'
},
'retroshare': {
title: 'RetroShare',
icon: '',
info: 'Performance metrics for RetroShare. RetroShare is open source software for encrypted filesharing, serverless email, instant messaging, online chat, and BBS, based on a friend-to-friend network built on GNU Privacy Guard (GPG).'
},
'riakkv': {
title: 'Riak KV',
icon: '',
info: 'Metrics for Riak KV, the distributed key-value store.'
},
'ipfs': {
title: 'IPFS',
icon: '',
info: 'Performance metrics for the InterPlanetary File System (IPFS), a content-addressable, peer-to-peer hypermedia distribution protocol.'
},
'phpfpm': {
title: 'PHP-FPM',
icon: '',
info: 'Performance metrics for PHP-FPM, an alternative FastCGI implementation for PHP.'
},
'pihole': {
title: 'Pi-hole',
icon: '',
info: 'Metrics for Pi-hole, a black hole for Internet advertisements.' +
' The metrics returned by Pi-Hole API is all from the last 24 hours.'
},
'portcheck': {
title: 'Port Check',
icon: '',
info: 'Service availability and latency monitoring using port checks.'
},
'postfix': {
title: 'postfix',
icon: '',
info: undefined
},
'dovecot': {
title: 'Dovecot',
icon: '',
info: undefined
},
'hddtemp': {
title: 'HDD Temp',
icon: '',
info: undefined
},
'nginx': {
title: 'nginx',
icon: '',
info: undefined
},
'apache': {
title: 'Apache',
icon: '',
info: undefined
},
'lighttpd': {
title: 'Lighttpd',
icon: '',
info: undefined
},
'web_log': {
title: undefined,
icon: '',
info: 'Information extracted from a server log file. web_log plugin incrementally parses the server log file to provide, in real-time, a break down of key server performance metrics. For web servers, an extended log file format may optionally be used (for nginx and apache) offering timing information and bandwidth for both requests and responses. web_log plugin may also be configured to provide a break down of requests per URL pattern (check /etc/netdata/python.d/web_log.conf).'
},
'named': {
title: 'named',
icon: '',
info: undefined
},
'squid': {
title: 'squid',
icon: '',
info: undefined
},
'nut': {
title: 'UPS',
icon: '',
info: undefined
},
'apcupsd': {
title: 'UPS',
icon: '',
info: undefined
},
'smawebbox': {
title: 'Solar Power',
icon: '',
info: undefined
},
'fronius': {
title: 'Fronius',
icon: '',
info: undefined
},
'stiebeleltron': {
title: 'Stiebel Eltron',
icon: '',
info: undefined
},
'snmp': {
title: 'SNMP',
icon: '',
info: undefined
},
'go_expvar': {
title: 'Go - expvars',
icon: '',
info: 'Statistics about running Go applications exposed by the expvar package.'
},
'chrony': {
icon: '',
info: 'chronyd parameters about the system’s clock performance.'
},
'couchdb': {
icon: '',
info: 'Performance metrics for CouchDB, the open-source, JSON document-based database with an HTTP API and multi-master replication.'
},
'beanstalk': {
title: 'Beanstalkd',
icon: '',
info: 'Provides statistics on the beanstalkd server and any tubes available on that server using data pulled from beanstalkc'
},
'rabbitmq': {
title: 'RabbitMQ',
icon: '',
info: 'Performance data for the RabbitMQ open-source message broker.'
},
'ceph': {
title: 'Ceph',
icon: '',
info: 'Provides statistics on the ceph cluster server, the open-source distributed storage system.'
},
'ntpd': {
title: 'ntpd',
icon: '',
info: 'Provides statistics for the internal variables of the Network Time Protocol daemon ntpd and optional including the configured peers (if enabled in the module configuration). The module presents the performance metrics as shown by ntpq (the standard NTP query program) using NTP mode 6 UDP packets to communicate with the NTP server.'
},
'spigotmc': {
title: 'Spigot MC',
icon: '',
info: 'Provides basic performance statistics for the Spigot Minecraft server.'
},
'unbound': {
title: 'Unbound',
icon: '',
info: undefined
},
'boinc': {
title: 'BOINC',
icon: '',
info: 'Provides task counts for BOINC distributed computing clients.'
},
'w1sensor': {
title: '1-Wire Sensors',
icon: '',
info: 'Data derived from 1-Wire sensors. Currently temperature sensors are automatically detected.'
},
'logind': {
title: 'Logind',
icon: '',
info: undefined
},
'powersupply': {
title: 'Power Supply',
icon: '',
info: 'Statistics for the various system power supplies. Data collected from Linux power supply class.'
},
'xenstat': {
title: 'Xen Node',
icon: '',
info: 'General statistics for the Xen node. Data collected using xenstat library.'
},
'xendomain': {
title: '',
icon: '',
info: 'Xen domain resource utilization metrics. Netdata reads this information using xenstat library which gives access to the resource usage information (CPU, memory, disk I/O, network) for a virtual machine.'
},
'wmi': {
title: 'wmi',
icon: '',
info: undefined
},
'perf': {
title: 'Perf Counters',
icon: '',
info: 'Performance Monitoring Counters (PMC). Data collected using perf_event_open() system call which utilises Hardware Performance Monitoring Units (PMU).'
},
'vsphere': {
title: 'vSphere',
icon: '',
info: 'Performance statistics for ESXI hosts and virtual machines. Data collected from VMware vCenter Server using govmomi library.'
},
'vcsa': {
title: 'VCSA',
icon: '',
info: 'vCenter Server Appliance health statistics. Data collected from Health API.'
},
'zookeeper': {
title: 'Zookeeper',
icon: '',
info: 'Provides health statistics for Zookeeper server. Data collected through the command port using mntr command.'
},
'hdfs': {
title: 'HDFS',
icon: '',
info: 'Provides Hadoop Distributed File System performance statistics. Module collects metrics over Java Management Extensions through the web interface of an HDFS daemon.'
},
'am2320': {
title: 'AM2320 Sensor',
icon: '',
info: 'Readings from the external AM2320 Sensor.'
},
'scaleio': {
title: 'ScaleIO',
icon: '',
info: 'Performance and health statistics for various ScaleIO components. Data collected via VxFlex OS Gateway REST API.'
},
'squidlog': {
title: 'Squid log',
icon: '',
info: undefined
},
'cockroachdb': {
title: 'CockroachDB',
icon: '',
info: 'Performance and health statistics for various CockroachDB components.'
},
'ebpf': {
title: 'eBPF',
icon: '',
info: 'Monitor system calls, internal functions, bytes read, bytes written and errors using eBPF.'
},
'filesystem': {
title: 'Filesystem',
icon: '',
},
'vernemq': {
title: 'VerneMQ',
icon: '',
info: 'Performance data for the VerneMQ open-source MQTT broker.'
},
'pulsar': {
title: 'Pulsar',
icon: '',
info: 'Summary, namespaces and topics performance data for the Apache Pulsar pub-sub messaging system.'
},
'anomalies': {
title: 'Anomalies',
icon: '',
info: 'Anomaly scores relating to key system metrics. A high anomaly probability indicates strange behaviour and may trigger an anomaly prediction from the trained models. Read the anomalies collector docs for more details.'
},
'alarms': {
title: 'Alarms',
icon: '',
info: 'Charts showing alarm status over time. More details here.'
},
'statsd': {
title: 'StatsD',
icon: '',
info:'StatsD is an industry-standard technology stack for monitoring applications and instrumenting any piece of software to deliver custom metrics. Netdata allows the user to organize the metrics in different charts and visualize any application metric easily. Read more on Netdata Learn.'
},
'supervisord': {
title: 'Supervisord',
icon: '',
info: 'Detailed statistics for each group of processes controlled by Supervisor. ' +
'Netdata collects these metrics using getAllProcessInfo method.'
},
'systemdunits': {
title: 'systemd units',
icon: '',
info: '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).'
},
'changefinder': {
title: 'ChangeFinder',
icon: '',
info: 'Online changepoint detection using machine learning. More details here.'
},
'zscores': {
title: 'Z-Scores',
icon: '',
info: 'Z scores scores relating to key system metrics.'
},
'anomaly_detection': {
title: 'Anomaly Detection',
icon: '',
info: '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.'
},
'fail2ban': {
title: 'Fail2ban',
icon: '',
info: 'Netdata keeps track of the current jail status by reading the Fail2ban log file.'
},
};
// ----------------------------------------------------------------------------
// submenus
// information to be shown, just below each submenu
// information about the submenus
netdataDashboard.submenu = {
'web_log.squid_bandwidth': {
title: 'bandwidth',
info: 'Bandwidth of responses (sent) by squid. This chart may present unusual spikes, since the bandwidth is accounted at the time the log line is saved by the server, even if the time needed to serve it spans across a longer duration. We suggest to use QoS (e.g. FireQOS) for accurate accounting of the server bandwidth.'
},
'web_log.squid_responses': {
title: 'responses',
info: 'Information related to the responses sent by squid.'
},
'web_log.squid_requests': {
title: 'requests',
info: 'Information related to the requests squid has received.'
},
'web_log.squid_hierarchy': {
title: 'hierarchy',
info: 'Performance metrics for the squid hierarchy used to serve the requests.'
},
'web_log.squid_squid_transport': {
title: 'transport'
},
'web_log.squid_squid_cache': {
title: 'cache',
info: 'Performance metrics for the performance of the squid cache.'
},
'web_log.squid_timings': {
title: 'timings',
info: 'Duration of squid requests. Unrealistic spikes may be reported, since squid logs the total time of the requests, when they complete. Especially for HTTPS, the clients get a tunnel from the proxy and exchange requests directly with the upstream servers, so squid cannot evaluate the individual requests and reports the total time the tunnel was open.'
},
'web_log.squid_clients': {
title: 'clients'
},
'web_log.bandwidth': {
info: 'Bandwidth of requests (received) and responses (sent). received requires an extended log format (without it, the web server log does not have this information). This chart may present unusual spikes, since the bandwidth is accounted at the time the log line is saved by the web server, even if the time needed to serve it spans across a longer duration. We suggest to use QoS (e.g. FireQOS) for accurate accounting of the web server bandwidth.'
},
'web_log.urls': {
info: 'Number of requests for each URL pattern defined in /etc/netdata/python.d/web_log.conf. This chart counts all requests matching the URL patterns defined, independently of the web server response codes (i.e. both successful and unsuccessful).'
},
'web_log.clients': {
info: 'Charts showing the number of unique client IPs, accessing the web server.'
},
'web_log.timings': {
info: 'Web server response timings - the time the web server needed to prepare and respond to requests. This requires an extended log format and its meaning is web server specific. For most web servers this accounts the time from the reception of a complete request, to the dispatch of the last byte of the response. So, it includes the network delays of responses, but it does not include the network delays of requests.'
},
'mem.ksm': {
title: 'deduper (ksm)',
info: 'Kernel Same-page Merging '+
'(KSM) performance monitoring, read from several files in /sys/kernel/mm/ksm/. '+
'KSM is a memory-saving de-duplication feature in the Linux kernel. '+
'The KSM daemon ksmd periodically scans those areas of user memory which have been registered with it, '+
'looking for pages of identical content which can be replaced by a single write-protected page.'
},
'mem.hugepages': {
info: '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.numa': {
info: 'Non-Uniform Memory Access (NUMA) is a hierarchical memory design the memory access time is dependent on locality. Under NUMA, a processor can access its own local memory faster than non-local memory (memory local to another processor or memory shared between processors). The individual metrics are described in the Linux kernel documentation.'
},
'mem.ecc': {
info: 'ECC memory '+ 'is a type of computer data storage that uses an error correction code (ECC) to detect '+ 'and correct n-bit data corruption which occurs in memory. '+ 'Typically, ECC memory maintains a memory system immune to single-bit errors: '+ 'the data that is read from each word is always the same as the data that had been written to it, '+ 'even if one of the bits actually stored has been flipped to the wrong state.
'+ 'Memory errors can be classified into two types: '+
'Soft errors, which randomly corrupt bits but do not leave physical damage. '+
'Soft errors are transient in nature and are not repeatable, can be because of electrical or '+
'magnetic interference. '+
'Hard errors, which corrupt bits in a repeatable manner because '+
'of a physical/hardware defect or an environmental problem.'
},
'mem.pagetype': {
info: 'Statistics of free memory available from '+
'memory buddy allocator. '+
'The buddy allocator is the system memory allocator. '+
'The whole memory space is split in physical pages, which are grouped by '+
'NUMA node, zone, '+
'migrate type, and size of the block. '+
'By keeping pages grouped based on their ability to move, '+
'the kernel can reclaim pages within a page block to satisfy a high-order allocation. '+
'When the kernel or an application requests some memory, the buddy allocator provides a page that matches closest the request.'
},
'ip.ecn': {
info: '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.'
},
'ip.multicast': {
info: 'IP multicast is a technique for '+
'one-to-many communication over an IP network. '+
'Multicast uses network infrastructure efficiently by requiring the source to send a packet only once, '+
'even if it needs to be delivered to a large number of receivers. '+
'The nodes in the network take care of replicating the packet to reach multiple receivers only when necessary.'
},
'ip.broadcast': {
info: '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.'
},
'netfilter.conntrack': {
title: 'connection tracker',
info: '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.'
},
'netfilter.nfacct': {
title: 'bandwidth accounting',
info: 'The following information is read using the nfacct.plugin.'
},
'netfilter.synproxy': {
title: 'DDoS protection',
info: 'DDoS protection performance metrics. SYNPROXY '+
'is a TCP SYN packets proxy. '+
'It is used to protect any TCP server (like a web server) from SYN floods and similar DDoS attacks. '+
'SYNPROXY intercepts new TCP connections and handles the initial 3-way handshake using syncookies '+
'instead of conntrack to establish the connection. '+
'It is optimized to handle millions of packets per second utilizing all CPUs available without '+
'any concurrency locking between the connections. '+
'It can be used for any kind of TCP traffic (even encrypted), '+
'since it does not interfere with the content itself.'
},
'ipfw.dynamic_rules': {
title: 'dynamic rules',
info: 'Number of dynamic rules, created by correspondent stateful firewall rules.'
},
'system.softnet_stat': {
title: 'softnet',
info: function (os) {
if (os === 'linux')
return '
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).
'; else return 'Statistics for CPUs SoftIRQs related to network receive work.'; } }, 'system.clock synchronization': { info: '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.' }, 'cpu.softnet_stat': { title: 'softnet', info: function (os) { if (os === 'linux') return 'Statistics for CPUs SoftIRQs related to network receive work. '+ 'Total for all CPU cores can be found at System / softnet statistics. '+ 'More information about identifying and troubleshooting network driver related issues can be found at '+ 'Red Hat Enterprise Linux Network Performance Tuning Guide.
'+ 'Processed - packets processed. '+ 'Dropped - packets dropped because the network device backlog was full. '+ 'Squeezed - number of times the network device budget was consumed or the time limit was reached, '+ 'but more work was available. '+ 'ReceivedRPS - number of times this CPU has been woken up to process packets via an Inter-processor Interrupt. '+ 'FlowLimitCount - number of times the flow limit has been reached (flow limiting is an optional '+ 'Receive Packet Steering feature).
'; else return 'Statistics for per CPUs core SoftIRQs related to network receive work. Total for all CPU cores can be found at System / softnet statistics.'; } }, 'go_expvar.memstats': { title: 'memory statistics', info: 'Go runtime memory statistics. See runtime.MemStats documentation for more info about each chart and the values.' }, 'couchdb.dbactivity': { title: 'db activity', info: 'Overall database reads and writes for the entire server. This includes any external HTTP traffic, as well as internal replication traffic performed in a cluster to ensure node consistency.' }, 'couchdb.httptraffic': { title: 'http traffic breakdown', info: 'All HTTP traffic, broken down by type of request (GET, PUT, POST, etc.) and response status code (200, 201, 4xx, etc.)ntpq -c rl. System variables are assigned an association ID of zero and can also be shown in the readvar billboard ntpq -c "rv 0". These variables are used in the Clock Discipline Algorithm, to calculate the lowest and most stable offset.'
},
'ntpd.peers': {
title: 'peers',
info: 'Statistics of the peer variables for each peer configured in /etc/ntp.conf as shown by the readvar billboard ntpq -c "rv <association>", while each peer is assigned a nonzero association ID as shown by ntpq -c "apeers". The module periodically scans for new/changed peers (default: every 60s). ntpd selects the best possible peer from the available peers to synchronize the clock. A minimum of at least 3 peers is required to properly identify the best possible peer.'
},
'mem.page_cache': {
title: 'page cache (eBPF)',
info: 'Monitor calls to functions used to manipulate Linux page cache. When integration with apps is enabled, Netdata also shows page cache manipulation per application.'
},
'apps.page_cache': {
title: 'page cache (eBPF)',
info: 'Netdata also gives a summary for these charts in Memory submenu.'
},
'filesystem.vfs': {
title: 'vfs (eBPF)',
info: 'Monitor calls to functions used to manipulate File Systems. When integration with apps is enabled, Netdata also shows Virtual File System per application.'
},
'apps.vfs': {
title: 'vfs (eBPF)',
info: 'Netdata also gives a summary for these charts in Filesystem submenu.'
},
'filesystem.ext4_latency': {
title: 'ext4 latency (eBPF)',
info: 'Latency is the time it takes for an event to be completed. We calculate the difference between the calling and return times, this spans disk I/O, file system operations (lock, I/O), run queue latency and all events related to the monitored action. Based on the eBPF ext4dist from BCC tools.'
},
'filesystem.xfs_latency': {
title: 'xfs latency (eBPF)',
info: 'Latency is the time it takes for an event to be completed. We calculate the difference between the calling and return times, this spans disk I/O, file system operations (lock, I/O), run queue latency and all events related to the monitored action. Based on the eBPF xfsdist from BCC tools.'
},
'filesystem.nfs_latency': {
title: 'nfs latency (eBPF)',
info: 'Latency is the time it takes for an event to be completed. We calculate the difference between the calling and return times, this spans disk I/O, file system operations (lock, I/O), run queue latency and all events related to the monitored action. Based on the eBPF nfsdist from BCC tools.'
},
'filesystem.zfs_latency': {
title: 'zfs latency (eBPF)',
info: 'Latency is the time it takes for an event to be completed. We calculate the difference between the calling and return times, this spans disk I/O, file system operations (lock, I/O), run queue latency and all events related to the monitored action. Based on the eBPF zfsdist from BCC tools.'
},
'filesystem.btrfs_latency': {
title: 'btrfs latency (eBPF)',
info: 'Latency is the time it takes for an event to be completed. We calculate the difference between the calling and return times, we get the logarithmic for the final result and we sum one value to the respective bin. Based on the eBPF btrfsdist from BCC tools.'
},
'filesystem.file_access': {
title: 'file access (eBPF)',
info: 'When integration with apps is enabled, Netdata also shows file access per application.'
},
'apps.file_access': {
title: 'file access (eBPF)',
info: 'Netdata also gives a summary for this chart on Filesystem submenu (more details on eBPF plugin file chart section).'
},
'ip.kernel': {
title: 'kernel functions (eBPF)',
info: 'Next charts are made when ebpf.plugin is running on your host. When integration with apps is enabled, Netdata also shows calls for kernel functions per application.'
},
'apps.net': {
title: 'network',
info: 'Netdata also gives a summary for eBPF charts in Networking Stack submenu.'
},
'system.ipc semaphores': {
info: '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.'
},
'system.ipc shared memory': {
info: '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.'
},
'system.ipc message queues': {
info: 'System V message queues is an inter-process communication (IPC) mechanism. '+
'It allow processes to exchange data in the form of messages. '+
'For details, see svipc(7). ' +
'To see the host IPC messages information, run ipcs -uq. For limits, run ipcs -lq.'
},
'system.interrupts': {
info: '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).'
},
'system.softirqs': {
info: '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.'
},
'cpu.softirqs': {
info: 'Total number of software interrupts per CPU. '+
'To see the total number for the system check the softirqs section.'
},
'cpu.interrupts': {
info: '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.throttling': {
info: ' CPU throttling is commonly used to automatically slow down the computer '+
'when possible to use less energy and conserve battery.'
},
'cpu.cpuidle': {
info: 'Idle States (C-states) '+
'are used to save power when the processor is idle.'
},
'services.net': {
title: 'network (eBPF)',
},
'services.page_cache': {
title: 'pache cache (eBPF)',
},
};
// ----------------------------------------------------------------------------
// chart
// information works on the context of a chart
// Its purpose is to set:
//
// info: the text above the charts
// heads: the representation of the chart at the top the subsection (second level menu)
// mainheads: the representation of the chart at the top of the section (first level menu)
// colors: the dimension colors of the chart (the default colors are appended)
// height: the ratio of the chart height relative to the default
//
var cgroupCPULimitIsSet = 0;
var cgroupMemLimitIsSet = 0;
netdataDashboard.context = {
'system.cpu': {
info: function (os) {
void (os);
return '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.'
+ netdataDashboard.sparkline('/sys/block, but do not exist in /sys/devices/virtual/block.';
else
return s;
}
},
'system.pgpgio': {
info: 'Memory paged from/to disk. This is usually the total disk I/O of the system.'
},
'system.swapio': {
info: 'System swap I/O.
'+ 'In - pages the system has swapped in from disk to RAM. '+ 'Out - pages the system has swapped out from RAM to disk.' }, 'system.pgfaults': { info: 'Total page faults. Major page faults indicates that the system is using its swap. You can find which applications use the swap at the Applications Monitoring section.' }, 'system.entropy': { colors: '#CC22AA', info: '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, likehaveged, although these are generally useful only in servers.'
},
'system.clock_sync_state': {
info:'The system clock synchronization state. '+ 'It is strongly recommended having the clock in sync with reliable NTP servers. Otherwise, '+ 'it leads to unpredictable problems. '+ 'It can take several minutes (usually up to 17) before NTP daemon selects a server to synchronize with. '+ '
State map: 0 - not synchronized, 1 - synchronized.
' }, 'system.clock_sync_offset': { info: '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.forks': { colors: '#5555DD', info: 'The number of new processes created.' }, 'system.intr': { colors: '#DD5555', info: 'Total number of CPU interrupts. Checksystem.interrupts that gives more detail about each interrupt and also the CPUs section where interrupts are analyzed per CPU core.'
},
'system.interrupts': {
info: '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.hardirq_latency': {
info: 'Total time spent servicing hardware interrupts. Based on the eBPF hardirqs from BCC tools.'
},
'system.softirqs': {
info: '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.softirq_latency': { info: 'Total time spent servicing software interrupts. Based on the eBPF softirqs from BCC tools.' }, 'system.processes': { info: 'System processes.
'+ 'Running - running or ready to run (runnable). '+ 'Blocked - currently blocked, waiting for I/O to complete.
' }, 'system.active_processes': { info: 'The total number of processes in the system.' }, 'system.ctxt': { info: '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.idlejitter': { info: '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.net': { info: function (os) { var s = 'Total bandwidth of all physical network interfaces. This does not includelo, VPNs, network bridges, IFB devices, bond interfaces, etc. Only the bandwidth of physical network interfaces is aggregated.';
if (os === 'linux')
return s + ' Physical are all the network interfaces that are listed in /proc/net/dev, but do not exist in /sys/devices/virtual/net.';
else
return s;
}
},
'system.ip': {
info: 'Total IP traffic in the system.'
},
'system.ipv4': {
info: 'Total IPv4 Traffic.'
},
'system.ipv6': {
info: 'Total IPv6 Traffic.'
},
'system.ram': {
info: 'System Random Access Memory (i.e. physical memory) usage.'
},
'system.swap': {
info: 'System swap memory usage. Swap space is used when the amount of physical memory (RAM) is full. When the system needs more memory resources and the RAM is full, inactive pages in memory are moved to the swap space (usually a disk, a disk partition or a file).'
},
'system.swapcalls': {
info: 'Monitor calls to functions swap_readpage and swap_writepage. When integration with apps is enabled, Netdata also shows swap access per application.'
},
'system.ipc_semaphores': {
info: '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_semaphore_arrays': {
info: '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.shared_memory_segments': {
info: '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_bytes': {
info: '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_calls': {
info: 'Monitor calls to functions shmget, shmat, shmdt, and shmctl. When integration with apps is enabled, Netdata also shows shared memory system call usage per application.'
},
'system.message_queue_messages': {
info: 'Number of messages that are currently present in System V IPC message queues.'
},
'system.message_queue_bytes': {
info: 'Amount of memory currently used by messages in System V IPC message queues.'
},
'system.uptime': {
info: 'The amount of time the system has been running, including time spent in suspend.'
},
'system.process_thread': {
title : 'Task creation',
info: 'Number of times that either do_fork, or kernel_clone if you are running kernel newer than 5.9.16, is called to create a new task, which is the common name used to define process and tasks inside the kernel. Netdata identifies the threads monitoring tracepoint sched_process_fork. This chart is provided by eBPF plugin.'
},
'system.exit': {
title : 'Exit monitoring',
info: 'Calls for the functions responsible for closing (do_exit) and releasing (release_task) tasks. This chart is provided by eBPF plugin.'
},
'system.task_error': {
title : 'Task error',
info: 'Number of errors to create a new process or thread. This chart is provided by eBPF plugin.'
},
'system.process_status': {
title : 'Task status',
info: 'Difference between the number of process created and the number of threads created per period(process dimension), it also shows the number of possible zombie process running on system. This chart is provided by eBPF plugin.'
},
// ------------------------------------------------------------------------
// CPU charts
'cpu.cpu': {
commonMin: true,
commonMax: true,
valueRange: "[0, 100]"
},
'cpu.interrupts': {
commonMin: true,
commonMax: true
},
'cpu.softirqs': {
commonMin: true,
commonMax: true
},
'cpu.softnet_stat': {
commonMin: true,
commonMax: true
},
'cpu.core_throttling': {
info: 'The number of adjustments made to the clock speed of the CPU based on it\'s core temperature.'
},
'cpu.package_throttling': {
info: 'The number of adjustments made to the clock speed of the CPU based on it\'s package (chip) temperature.'
},
'cpufreq.cpufreq': {
info: 'The frequency measures the number of cycles your CPU executes per second.'
},
'cpuidle.cpuidle': {
info: 'The percentage of time spent in C-states.'
},
// ------------------------------------------------------------------------
// MEMORY
'mem.ksm': {
info: 'Memory pages merging statistics. '+ 'A high ratio of Sharing to Shared indicates good sharing, '+ 'but a high ratio of Unshared to Sharing indicates wasted effort.
'+ 'Shared - used shared pages. '+ 'Unshared - memory no longer shared (pages are unique but repeatedly checked for merging). '+ 'Sharing - memory currently shared (how many more sites are sharing the pages, i.e. how much saved). '+ 'Volatile - volatile pages (changing too fast to be placed in a tree).
' }, 'mem.ksm_savings': { heads: [ netdataDashboard.gaugeChart('Saved', '12%', 'savings', '#0099CC') ], info: 'The amount of memory saved by KSM.
'+ 'Savings - saved memory. '+ 'Offered - memory marked as mergeable.
' }, 'mem.ksm_ratios': { heads: [ function (os, id) { void (os); return ''; } ], info: 'The effectiveness of KSM. '+ 'This is the percentage of the mergeable pages that are currently merged.' }, 'mem.zram_usage': { info: 'ZRAM total RAM usage metrics. ZRAM uses some memory to store metadata about stored memory pages, thus introducing an overhead which is proportional to disk size. It excludes same-element-filled-pages since no memory is allocated for them.' }, 'mem.zram_savings': { info: 'Displays original and compressed memory data sizes.' }, 'mem.zram_ratio': { heads: [ netdataDashboard.gaugeChart('Compression Ratio', '12%', 'ratio', '#0099CC') ], info: 'Compression ratio, calculated as100 * original_size / compressed_size. More means better compression and more RAM savings.'
},
'mem.zram_efficiency': {
heads: [
netdataDashboard.gaugeChart('Efficiency', '12%', 'percent', NETDATA.colors[0])
],
commonMin: true,
commonMax: true,
valueRange: "[0, 100]",
info: 'Memory usage efficiency, calculated as 100 * compressed_size / total_mem_used.'
},
'mem.pgfaults': {
info: '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.committed': { colors: NETDATA.colors[3], info: 'Committed Memory, is the sum of all memory which has been allocated by processes.' }, 'mem.oom_kill': { info: '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.numa': { info: 'NUMA balancing statistics.
'+ 'Local - pages successfully allocated on this node, by a process on this node. '+ 'Foreign - pages initially intended for this node that were allocated to another node instead. '+ 'Interleave - interleave policy pages successfully allocated to this node. '+ 'Other - pages allocated on this node, by a process on another node. '+ 'PteUpdates - base pages that were marked for NUMA hinting faults. '+ 'HugePteUpdates - transparent huge pages that were marked for NUMA hinting faults. '+ 'In Combination with pte_updates the total address space that was marked can be calculated. '+ 'HintFaults - NUMA hinting faults that were trapped. '+ 'HintFaultsLocal - hinting faults that were to local nodes. '+ 'In combination with HintFaults, the percentage of local versus remote faults can be calculated. '+ 'A high percentage of local hinting faults indicates that the workload is closer to being converged. '+ 'PagesMigrated - pages were migrated because they were misplaced. '+ 'As migration is a copying operation, it contributes the largest part of the overhead created by NUMA balancing.
' }, 'mem.available': { info: 'Available Memory is estimated by the kernel, as the amount of RAM that can be used by userspace processes, without causing swapping.' }, 'mem.writeback': { info: 'Dirty is the amount of memory waiting to be written to disk. Writeback is how much memory is actively being written to disk.' }, 'mem.kernel': { info: '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.slab': { info: '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.hugepages': { info: 'Dedicated (or Direct) HugePages is memory reserved for applications configured to utilize huge pages. Hugepages are used memory, even if there are free hugepages available.' }, 'mem.transparent_hugepages': { info: 'Transparent HugePages (THP) is backing virtual memory with huge pages, supporting automatic promotion and demotion of page sizes. It works for all applications for anonymous memory mappings and tmpfs/shmem.' }, 'mem.hwcorrupt': { info: 'The amount of memory with physical corruption problems, identified by ECC and set aside by the kernel so it does not get used.' }, 'mem.ecc_ce': { info: 'The number of correctable (single-bit) ECC errors. '+ 'These errors do not affect the normal operation of the system '+ 'because they are still being corrected. '+ 'Periodic correctable errors may indicate that one of the memory modules is slowly failing.' }, 'mem.ecc_ue': { info: 'The number of uncorrectable (multi-bit) ECC errors. '+ 'An uncorrectable error is a fatal issue that will typically lead to an OS crash.' }, 'mem.pagetype_global': { info: 'The amount of memory available in blocks of certain size.' }, 'mem.cachestat_ratio': { info: 'When the processor needs to read or write a location in main memory, it checks for a corresponding entry in the page cache. If the entry is there, a page cache hit has occurred and the read is from the cache. If the entry is not there, a page cache miss has occurred and the kernel allocates a new entry and copies in data from the disk. Netdata calculates the percentage of accessed files that are cached on memory. The ratio is calculated counting the accessed cached pages (without counting dirty pages and pages added because of read misses) divided by total access without dirty pages.' }, 'mem.cachestat_dirties': { info: 'Number of dirty(modified) pages cache. Pages in the page cache modified after being brought in are called dirty pages. Since non-dirty pages in the page cache have identical copies in secondary storage (e.g. hard disk drive or solid-state drive), discarding and reusing their space is much quicker than paging out application memory, and is often preferred over flushing the dirty pages into secondary storage and reusing their space.' }, 'mem.cachestat_hits': { info: 'When the processor needs to read or write a location in main memory, it checks for a corresponding entry in the page cache. If the entry is there, a page cache hit has occurred and the read is from the cache. Hits show pages accessed that were not modified (we are excluding dirty pages), this counting also excludes the recent pages inserted for read.' }, 'mem.cachestat_misses': { info: 'When the processor needs to read or write a location in main memory, it checks for a corresponding entry in the page cache. If the entry is not there, a page cache miss has occurred and the cache allocates a new entry and copies in data for the main memory. Misses count page insertions to the memory not related to writing.' }, 'mem.sync': { info: 'System calls for sync() and syncfs() which flush the file system buffers to storage devices. Performance perturbations might be caused by these calls. Thesync() calls are based on the eBPF syncsnoop from BCC tools.'
},
'mem.file_sync': {
info: 'System calls for fsync() and fdatasync() transfer all modified page caches for the files on disk devices. These calls block until the device reports that the transfer has been completed.'
},
'mem.memory_map': {
info: 'System calls for msync() which flushes changes made to the in-core copy of a file that was mapped.'
},
'mem.file_segment': {
info: 'System calls for sync_file_range() permits fine control when synchronizing the open file referred to by the file descriptor fd with disk. This system call is extremely dangerous and should not be used in portable programs.'
},
'filesystem.dc_hit_ratio': {
info: 'Percentage of file accesses that were present in the directory cache. 100% means that every file that was accessed was present in the directory cache. If files are not present in the directory cache 1) they are not present in the file system, 2) the files were not accessed before. Read more about directory cache. When integration with apps is enabled, Netdata also shows directory cache per application.'
},
'filesystem.dc_reference': {
info: 'Counters of file accesses. Reference is when there is a file access and the file is not present in the directory cache. Miss is when there is file access and the file is not found in the filesystem. Slow is when there is a file access and the file is present in the filesystem but not in the directory cache. Read more about directory cache.'
},
'md.health': {
info: 'Number of failed devices per MD array. '+
'Netdata retrieves this data from the [n/m] field of the md status line. '+
'It means that ideally the array would have n devices however, currently, m devices are in use. '+
'failed disks is n-m.'
},
'md.disks': {
info: 'Number of devices in use and in the down state. '+
'Netdata retrieves this data from the [n/m] field of the md status line. '+
'It means that ideally the array would have n devices however, currently, m devices are in use. '+
'inuse is m, down is n-m.'
},
'md.status': {
info: 'Completion progress of the ongoing operation.'
},
'md.expected_time_until_operation_finish': {
info: 'Estimated time to complete the ongoing operation. '+
'The time is only an approximation since the operation speed will vary according to other I/O demands.'
},
'md.operation_speed': {
info: 'Speed of the ongoing operation. '+
'The system-wide rebuild speed limits are specified in /proc/sys/dev/raid/{speed_limit_min,speed_limit_max} files. '+
'These options are good for tweaking rebuilt process and may increase overall system load, cpu and memory usage.'
},
'md.mismatch_cnt': {
info: 'When performing check and repair, and possibly when performing resync, md will count the number of errors that are found. '+
'A count of mismatches is recorded in the sysfs file md/mismatch_cnt. '+
'This value is the number of sectors that were re-written, or (for check) would have been re-written. '+
'It may be larger than the number of actual errors by a factor of the number of sectors in a page. '+
'Mismatches can not be interpreted very reliably on RAID1 or RAID10, especially when the device is used for swap. '+
'On a truly clean RAID5 or RAID6 array, any mismatches should indicate a hardware problem at some level - '+
'software issues should never cause such a mismatch. '+
'For details, see md(4).'
},
'md.flush': {
info: 'Number of flush counts per MD array. Based on the eBPF mdflush from BCC tools.'
},
// ------------------------------------------------------------------------
// IP
'ip.inerrors': {
info: 'The number of errors encountered during the reception of IP packets.
' + 'NoRoutes - packets that were dropped because there was no route to send them. ' + 'Truncated - packets which is being discarded because the datagram frame didn\'t carry enough data. ' + 'Checksum - packets that were dropped because they had wrong checksum.' }, 'ip.mcast': { info: 'Total multicast traffic in the system.' }, 'ip.mcastpkts': { info: 'Total transferred multicast packets in the system.' }, 'ip.bcast': { info: 'Total broadcast traffic in the system.' }, 'ip.bcastpkts': { info: 'Total transferred broadcast packets in the system.' }, 'ip.ecnpkts': { info: '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.tcpreorders': { info: '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.tcpofo': { info: '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.tcpsyncookies': { info: '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.tcpmemorypressures': { info: 'The number of times a socket was put in memory pressure due to a non fatal memory allocation failure '+ '(the kernel attempts to work around this situation by reducing the send buffers, etc).' }, 'ip.tcpconnaborts': { info: '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 send an RST but failed because there was no memory available.
' }, 'ip.tcp_functions': { title : 'TCP calls', info: 'Successful or failed calls to functionstcp_sendmsg, tcp_cleanup_rbuf, and tcp_close.'
},
'ip.total_tcp_bandwidth': {
title : 'TCP bandwidth',
info: 'Bytes sent and received by functions tcp_sendmsg and tcp_cleanup_rbuf. We use tcp_cleanup_rbuf instead of tcp_recvmsg, because the last one misses tcp_read_sock() traffic and we would also need to have more probes to get the socket and package size.'
},
'ip.tcp_error': {
title : 'TCP errors',
info: 'Failed calls to functions tcp_sendmsg, tcp_cleanup_rbuf, and tcp_close.'
},
'ip.tcp_retransmit': {
title : 'TCP retransmit',
info: 'Number of packets retransmitted by function tcp_retransmit_skb.'
},
'ip.udp_functions': {
title : 'UDP calls',
info: 'Successful or failed calls to functions udp_sendmsg and udp_recvmsg.'
},
'ip.total_udp_bandwidth': {
title : 'UDP bandwidth',
info: 'Bytes sent and received by functions udp_sendmsg and udp_recvmsg.'
},
'ip.udp_error': {
title : 'UDP errors',
info: 'Failed calls to functions udp_sendmsg and udp_recvmsg.'
},
'ip.tcp_syn_queue': {
info: 'The SYN queue of the kernel tracks TCP handshakes until connections get fully established. ' + 'It overflows when too many incoming TCP connection requests hang in the half-open state and the server ' + 'is not configured to fall back to SYN cookies. Overflows are usually caused by SYN flood DoS attacks.
' + 'Drops - number of connections dropped because the SYN queue was full and SYN cookies were disabled. ' + 'Cookies - number of SYN cookies sent because the SYN queue was full.
' }, 'ip.tcp_accept_queue': { info: '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.' }, // ------------------------------------------------------------------------ // IPv4 'ipv4.packets': { info: '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.fragsout': { info: '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.fragsin': { info: '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.errors': { info: '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 due to invalid IP address or '+ 'the destination IP address is not a local address and IP forwarding is not enabled. '+ 'InUnknownProtos - input packets which were discarded because of an unknown or unsupported protocol.
' }, 'ipv4.icmp': { info: '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_errors': { info: '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.icmpmsg': { info: 'The number of transferred '+ 'IPv4 ICMP control messages.' }, 'ipv4.udppackets': { info: 'The number of transferred UDP packets.' }, 'ipv4.udperrors': { info: '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.udplite': { info: 'The number of transferred UDP-Lite packets.' }, 'ipv4.udplite_errors': { info: 'The number of errors encountered during transferring UDP-Lite 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.tcppackets': { info: '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.tcpsock': { info: '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.tcpopens': { info: 'TCP connection statistics.
'+ 'Active - number of outgoing TCP connections attempted by this host. '+ 'Passive - number of incoming TCP connections accepted by this host.
' }, 'ipv4.tcperrors': { info: '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.tcphandshake': { info: '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.sockstat_sockets': { info: 'The total number of used sockets for all '+ 'address families '+ 'in this system.' }, 'ipv4.sockstat_tcp_sockets': { info: '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_mem': { info: 'The amount of memory used by allocated TCP sockets.' }, 'ipv4.sockstat_udp_sockets': { info: 'The number of used UDP sockets.' }, 'ipv4.sockstat_udp_mem': { info: 'The amount of memory used by allocated UDP sockets.' }, 'ipv4.sockstat_udplite_sockets': { info: 'The number of used UDP-Lite sockets.' }, 'ipv4.sockstat_raw_sockets': { info: 'The number of used raw sockets.' }, 'ipv4.sockstat_frag_sockets': { info: 'The number of entries in hash tables that are used for packet reassembly.' }, 'ipv4.sockstat_frag_mem': { info: 'The amount of memory used for packet reassembly.' }, // ------------------------------------------------------------------------ // IPv6 'ipv6.packets': { info: '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.fragsout': { info: '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.fragsin': { info: '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.errors': { info: '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.udppackets': { info: 'The number of transferred UDP packets.' }, 'ipv6.udperrors': { info: '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.' }, 'ipv6.udplitepackets': { info: 'The number of transferred UDP-Lite packets.' }, 'ipv6.udpliteerrors': { info: 'The number of errors encountered during transferring UDP-Lite 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.
' }, 'ipv6.mcast': { info: 'Total IPv6 multicast traffic.' }, 'ipv6.bcast': { info: 'Total IPv6 broadcast traffic.' }, 'ipv6.mcastpkts': { info: 'Total transferred IPv6 multicast packets.' }, 'ipv6.icmp': { info: 'The number of transferred ICMPv6 messages.
'+ 'Received, Sent - ICMP messages which the host received and attempted to send. '+ 'Both these counters include errors.
' }, 'ipv6.icmpredir': { info: 'The number of transferred ICMPv6 Redirect messages. '+ 'These messages inform a host to update its routing information (to send packets on an alternative route).' }, 'ipv6.icmpechos': { info: 'The number of ICMPv6 Echo messages.' }, 'ipv6.icmperrors': { info: 'The number of ICMPv6 errors and '+ 'error messages.
'+ 'InErrors, OutErrors - bad ICMP messages (bad ICMP checksums, bad length, etc.). '+ 'InCsumErrors - wrong checksum.
' }, 'ipv6.groupmemb': { info: 'The number of transferred ICMPv6 Group Membership messages.
'+ 'Multicast routers send Group Membership Query messages to learn which groups have members on each of their '+ 'attached physical networks. Host computers respond by sending a Group Membership Report for each '+ 'multicast group joined by the host. A host computer can also send a Group Membership Report when '+ 'it joins a new multicast group. '+ 'Group Membership Reduction messages are sent when a host computer leaves a multicast group.
' }, 'ipv6.icmprouter': { info: '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.icmpneighbor': { info: '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.icmpmldv2': { info: 'The number of transferred ICMPv6 '+ 'Multicast Listener Discovery (MLD) messages.' }, 'ipv6.icmptypes': { info: 'The number of transferred ICMPv6 messages of '+ 'certain types.' }, 'ipv6.ect': { info: '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.sockstat6_tcp_sockets': { info: 'The number of TCP sockets in any '+ 'state, '+ 'excluding TIME-WAIT and CLOSED.' }, 'ipv6.sockstat6_udp_sockets': { info: 'The number of used UDP sockets.' }, 'ipv6.sockstat6_udplite_sockets': { info: 'The number of used UDP-Lite sockets.' }, 'ipv6.sockstat6_raw_sockets': { info: 'The number of used raw sockets.' }, 'ipv6.sockstat6_frag_sockets': { info: 'The number of entries in hash tables that are used for packet reassembly.' }, // ------------------------------------------------------------------------ // SCTP 'sctp.established': { info: 'The number of associations for which the current state is either '+ 'ESTABLISHED, SHUTDOWN-RECEIVED or SHUTDOWN-PENDING.' }, 'sctp.transitions': { info: 'The number of times that associations have made a direct transition between states.
'+ 'Active - from COOKIE-ECHOED to ESTABLISHED. The upper layer initiated the association attempt. '+ 'Passive - from CLOSED to ESTABLISHED. The remote endpoint initiated the association attempt. '+ 'Aborted - from any state to CLOSED using the primitive ABORT. Ungraceful termination of the association. '+ 'Shutdown - from SHUTDOWN-SENT or SHUTDOWN-ACK-SENT to CLOSED. Graceful termination of the association.
' }, 'sctp.packets': { info: 'The number of transferred SCTP packets.
'+ 'Received - includes duplicate packets. '+ 'Sent - includes retransmitted DATA chunks.
' }, 'sctp.packet_errors': { info: 'The number of errors encountered during receiving SCTP packets.
'+ 'Invalid - packets for which the receiver was unable to identify an appropriate association. '+ 'Checksum - packets with an invalid checksum.
' }, 'sctp.fragmentation': { info: 'The number of fragmented and reassembled SCTP messages.
'+ 'Reassembled - reassembled user messages, after conversion into DATA chunks. '+ 'Fragmented - user messages that have to be fragmented because of the MTU.
' }, 'sctp.chunks': { info: 'The number of transferred control, ordered, and unordered DATA chunks. '+ 'Retransmissions and duplicates are not included.' }, // ------------------------------------------------------------------------ // Netfilter Connection Tracker 'netfilter.conntrack_sockets': { info: 'The number of entries in the conntrack table.' }, 'netfilter.conntrack_new': { info: '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_changes': { info: '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_expect': { info: '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_search': { info: '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_errors': { info: '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.synproxy_syn_received': { info: 'The number of initial TCP SYN packets received from clients.' }, 'netfilter.synproxy_conn_reopened': { info: 'The number of reopened connections by new TCP SYN packets directly from the TIME-WAIT state.' }, 'netfilter.synproxy_cookies': { info: 'SYNPROXY cookie statistics.
'+ 'Valid, Invalid - result of cookie validation in TCP ACK packets received from clients. '+ 'Retransmits - TCP SYN packets retransmitted to the server. '+ 'It happens when the client repeats TCP ACK and the connection to the server is not yet established.
' }, // ------------------------------------------------------------------------ // APPS (Applications, Groups, Users) // APPS cpu 'apps.cpu': { info: 'Total CPU utilization (all cores). It includes user, system and guest time.' }, 'groups.cpu': { info: 'Total CPU utilization (all cores). It includes user, system and guest time.' }, 'users.cpu': { info: 'Total CPU utilization (all cores). It includes user, system and guest time.' }, 'apps.cpu_user': { info: 'The amount of time the CPU was busy executing code in '+ 'user mode (all cores).' }, 'groups.cpu_user': { info: 'The amount of time the CPU was busy executing code in '+ 'user mode (all cores).' }, 'users.cpu_user': { info: 'The amount of time the CPU was busy executing code in '+ 'user mode (all cores).' }, 'apps.cpu_system': { info: 'The amount of time the CPU was busy executing code in '+ 'kernel mode (all cores).' }, 'groups.cpu_system': { info: 'The amount of time the CPU was busy executing code in '+ 'kernel mode (all cores).' }, 'users.cpu_system': { info: 'The amount of time the CPU was busy executing code in '+ 'kernel mode (all cores).' }, 'apps.cpu_guest': { info: 'The amount of time spent running a virtual CPU for a guest operating system (all cores).' }, 'groups.cpu_guest': { info: 'The amount of time spent running a virtual CPU for a guest operating system (all cores).' }, 'users.cpu_guest': { info: 'The amount of time spent running a virtual CPU for a guest operating system (all cores).' }, // APPS disk 'apps.preads': { info: 'The amount of data that has been read from the storage layer. '+ 'Actual physical disk I/O was required.' }, 'groups.preads': { info: 'The amount of data that has been read from the storage layer. '+ 'Actual physical disk I/O was required.' }, 'users.preads': { info: 'The amount of data that has been read from the storage layer. '+ 'Actual physical disk I/O was required.' }, 'apps.pwrites': { info: 'The amount of data that has been written to the storage layer. '+ 'Actual physical disk I/O was required.' }, 'groups.pwrites': { info: 'The amount of data that has been written to the storage layer. '+ 'Actual physical disk I/O was required.' }, 'users.pwrites': { info: 'The amount of data that has been written to the storage layer. '+ 'Actual physical disk I/O was required.' }, 'apps.lreads': { info: 'The amount of data that has been read from the storage layer. '+ 'It includes things such as terminal I/O and is unaffected by whether or '+ 'not actual physical disk I/O was required '+ '(the read might have been satisfied from pagecache).' }, 'groups.lreads': { info: 'The amount of data that has been read from the storage layer. '+ 'It includes things such as terminal I/O and is unaffected by whether or '+ 'not actual physical disk I/O was required '+ '(the read might have been satisfied from pagecache).' }, 'users.lreads': { info: '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.lwrites': { info: 'The amount of data that has been written or shall be written to the storage layer. '+ 'It includes things such as terminal I/O and is unaffected by whether or '+ 'not actual physical disk I/O was required.' }, 'groups.lwrites': { info: 'The amount of data that has been written or shall be written to the storage layer. '+ 'It includes things such as terminal I/O and is unaffected by whether or '+ 'not actual physical disk I/O was required.' }, 'users.lwrites': { info: '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.files': { info: 'The number of open files and directories.' }, 'groups.files': { info: 'The number of open files and directories.' }, 'users.files': { info: 'The number of open files and directories.' }, // APPS mem 'apps.mem': { info: 'Real memory (RAM) used by applications. This does not include shared memory.' }, 'groups.mem': { info: 'Real memory (RAM) used per user group. This does not include shared memory.' }, 'users.mem': { info: 'Real memory (RAM) used per user group. This does not include shared memory.' }, 'apps.vmem': { info: 'Virtual memory allocated by applications. '+ 'Check this article for more information.' }, 'groups.vmem': { info: 'Virtual memory allocated per user group since the Netdata restart. Please check this article for more information.' }, 'users.vmem': { info: 'Virtual memory allocated per user group since the Netdata restart. Please check this article for more information.' }, 'apps.minor_faults': { info: 'The number of minor faults '+ 'which have not required loading a memory page from the disk. '+ 'Minor page faults occur when a process needs data that is in memory and is assigned to another process. '+ 'They share memory pages between multiple processes – '+ 'no additional data needs to be read from disk to memory.' }, 'groups.minor_faults': { info: 'The number of minor faults '+ 'which have not required loading a memory page from the disk. '+ 'Minor page faults occur when a process needs data that is in memory and is assigned to another process. '+ 'They share memory pages between multiple processes – '+ 'no additional data needs to be read from disk to memory.' }, 'users.minor_faults': { info: '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 processes 'apps.threads': { info: 'The number of threads.' }, 'groups.threads': { info: 'The number of threads.' }, 'users.threads': { info: 'The number of threads.' }, 'apps.processes': { info: 'The number of processes.' }, 'groups.processes': { info: 'The number of processes.' }, 'users.processes': { info: 'The number of processes.' }, 'apps.uptime': { info: 'The period of time within which at least one process in the group has been running.' }, 'groups.uptime': { info: 'The period of time within which at least one process in the group has been running.' }, 'users.uptime': { info: 'The period of time within which at least one process in the group has been running.' }, 'apps.uptime_min': { info: 'The shortest uptime among processes in the group.' }, 'groups.uptime_min': { info: 'The shortest uptime among processes in the group.' }, 'users.uptime_min': { info: 'The shortest uptime among processes in the group.' }, 'apps.uptime_avg': { info: 'The average uptime of processes in the group.' }, 'groups.uptime_avg': { info: 'The average uptime of processes in the group.' }, 'users.uptime_avg': { info: 'The average uptime of processes in the group.' }, 'apps.uptime_max': { info: 'The longest uptime among processes in the group.' }, 'groups.uptime_max': { info: 'The longest uptime among processes in the group.' }, 'users.uptime_max': { info: 'The longest uptime among processes in the group.' }, 'apps.pipes': { info: 'The number of open '+ 'pipes. '+ 'A pipe is a unidirectional data channel that can be used for interprocess communication.' }, 'groups.pipes': { info: 'The number of open '+ 'pipes. '+ 'A pipe is a unidirectional data channel that can be used for interprocess communication.' }, 'users.pipes': { info: 'The number of open '+ 'pipes. '+ 'A pipe is a unidirectional data channel that can be used for interprocess communication.' }, // APPS swap 'apps.swap': { info: 'The amount of swapped-out virtual memory by anonymous private pages. '+ 'This does not include shared swap memory.' }, 'groups.swap': { info: 'The amount of swapped-out virtual memory by anonymous private pages. '+ 'This does not include shared swap memory.' }, 'users.swap': { info: 'The amount of swapped-out virtual memory by anonymous private pages. '+ 'This does not include shared swap memory.' }, 'apps.major_faults': { info: 'The number of major faults '+ 'which have required loading a memory page from the disk. '+ 'Major page faults occur because of the absence of the required page from the RAM. '+ 'They are expected when a process starts or needs to read in additional data and '+ 'in these cases do not indicate a problem condition. '+ 'However, a major page fault can also be the result of reading memory pages that have been written out '+ 'to the swap file, which could indicate a memory shortage.' }, 'groups.major_faults': { info: 'The number of major faults '+ 'which have required loading a memory page from the disk. '+ 'Major page faults occur because of the absence of the required page from the RAM. '+ 'They are expected when a process starts or needs to read in additional data and '+ 'in these cases do not indicate a problem condition. '+ 'However, a major page fault can also be the result of reading memory pages that have been written out '+ 'to the swap file, which could indicate a memory shortage.' }, 'users.major_faults': { info: '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 net 'apps.sockets': { info: 'The number of open sockets. '+ 'Sockets are a way to enable inter-process communication between programs running on a server, '+ 'or between programs running on separate servers. This includes both network and UNIX sockets.' }, 'groups.sockets': { info: 'The number of open sockets. '+ 'Sockets are a way to enable inter-process communication between programs running on a server, '+ 'or between programs running on separate servers. This includes both network and UNIX sockets.' }, 'users.sockets': { info: 'The number of open sockets. '+ 'Sockets are a way to enable inter-process communication between programs running on a server, '+ 'or between programs running on separate servers. This includes both network and UNIX sockets.' }, // Apps eBPF stuff 'apps.file_open': { info: 'Calls to the internal functiondo_sys_open (for kernels newer than 5.5.19 we add a kprobe to do_sys_openat2. ), which is the common function called from' +
' open(2) ' +
' and openat(2). '
},
'apps.file_open_error': {
info: 'Failed calls to the internal function do_sys_open (for kernels newer than 5.5.19 we add a kprobe to do_sys_openat2. ).'
},
'apps.file_closed': {
info: 'Calls to the internal function __close_fd or close_fd according to your kernel version, which is called from' +
' close(2). '
},
'apps.file_close_error': {
info: 'Failed calls to the internal function __close_fd or close_fd according to your kernel version.'
},
'apps.file_deleted': {
info: 'Calls to the function vfs_unlink. This chart does not show all events that remove files from the filesystem, because filesystems can create their own functions to remove files.'
},
'apps.vfs_write_call': {
info: 'Successful calls to the function vfs_write. This chart may not show all filesystem events if it uses other functions to store data on disk.'
},
'apps.vfs_write_error': {
info: 'Failed calls to the function vfs_write. This chart may not show all filesystem events if it uses other functions to store data on disk.'
},
'apps.vfs_read_call': {
info: 'Successful calls to the function vfs_read. This chart may not show all filesystem events if it uses other functions to store data on disk.'
},
'apps.vfs_read_error': {
info: 'Failed calls to the function vfs_read. This chart may not show all filesystem events if it uses other functions to store data on disk.'
},
'apps.vfs_write_bytes': {
info: 'Total of bytes successfully written using the function vfs_write.'
},
'apps.vfs_read_bytes': {
info: 'Total of bytes successfully read using the function vfs_read.'
},
'apps.process_create': {
info: 'Calls to either do_fork, or kernel_clone if you are running kernel newer than 5.9.16, to create a new task, which is the common name used to define process and tasks inside the kernel. This chart is provided by eBPF plugin.'
},
'apps.thread_create': {
info: 'Calls to either do_fork, or kernel_clone if you are running kernel newer than 5.9.16, to create a new task, which is the common name used to define process and tasks inside the kernel. Netdata identifies the threads monitoring tracepoint sched_process_fork. This chart is provided by eBPF plugin.'
},
'apps.task_exit': {
info: 'Calls to the function responsible for closing (do_exit) tasks. This chart is provided by eBPF plugin.'
},
'apps.task_close': {
info: 'Calls to the function responsible for releasing (release_task) tasks. This chart is provided by eBPF plugin.'
},
'apps.task_error': {
info: 'Number of errors to create a new process or thread. This chart is provided by eBPF plugin.'
},
'apps.total_bandwidth_sent': {
info: 'Bytes sent by functions tcp_sendmsg and udp_sendmsg.'
},
'apps.total_bandwidth_recv': {
info: 'Bytes received by functions tcp_cleanup_rbuf and udp_recvmsg. We use tcp_cleanup_rbuf instead tcp_recvmsg, because this last misses tcp_read_sock() traffic and we would also need to have more probes to get the socket and package size.'
},
'apps.bandwidth_tcp_send': {
info: 'The function tcp_sendmsg is used to collect number of bytes sent from TCP connections.'
},
'apps.bandwidth_tcp_recv': {
info: 'The function tcp_cleanup_rbuf is used to collect number of bytes received from TCP connections.'
},
'apps.bandwidth_tcp_retransmit': {
info: 'The function tcp_retransmit_skb is called when the host did not receive the expected return from a packet sent.'
},
'apps.bandwidth_udp_send': {
info: 'The function udp_sendmsg is used to collect number of bytes sent from UDP connections.'
},
'apps.bandwidth_udp_recv': {
info: 'The function udp_recvmsg is used to collect number of bytes received from UDP connections.'
},
'apps.dc_hit_ratio': {
info: 'Percentage of file accesses that were present in the directory cache. 100% means that every file that was accessed was present in the directory cache. If files are not present in the directory cache 1) they are not present in the file system, 2) the files were not accessed before. Read more about directory cache. Netdata also gives a summary for these charts in Filesystem submenu.'
},
'apps.dc_reference': {
info: 'Counters of file accesses. Reference is when there is a file access, see the filesystem.dc_reference chart for more context. Read more about directory cache.'
},
'apps.dc_not_cache': {
info: 'Counters of file accesses. Slow is when there is a file access and the file is not present in the directory cache, see the filesystem.dc_reference chart for more context. Read more about directory cache.'
},
'apps.dc_not_found': {
info: 'Counters of file accesses. Miss is when there is file access and the file is not found in the filesystem, see the filesystem.dc_reference chart for more context. Read more about directory cache.'
},
// ------------------------------------------------------------------------
// NETWORK QoS
'tc.qos': {
heads: [
function (os, id) {
void (os);
if (id.match(/.*-ifb$/))
return netdataDashboard.gaugeChart('Inbound', '12%', '', '#5555AA');
else
return netdataDashboard.gaugeChart('Outbound', '12%', '', '#AA9900');
}
]
},
// ------------------------------------------------------------------------
// NETWORK INTERFACES
'net.net': {
mainheads: [
function (os, id) {
void (os);
if (id.match(/^cgroup_.*/)) {
var iface;
try {
iface = ' ' + id.substring(id.lastIndexOf('.net_') + 5, id.length);
} catch (e) {
iface = '';
}
return netdataDashboard.gaugeChart('Received' + iface, '12%', 'received');
} else
return '';
},
function (os, id) {
void (os);
if (id.match(/^cgroup_.*/)) {
var iface;
try {
iface = ' ' + id.substring(id.lastIndexOf('.net_') + 5, id.length);
} catch (e) {
iface = '';
}
return netdataDashboard.gaugeChart('Sent' + iface, '12%', 'sent');
} else
return '';
}
],
heads: [
function (os, id) {
void (os);
if (!id.match(/^cgroup_.*/))
return netdataDashboard.gaugeChart('Received', '12%', 'received');
else
return '';
},
function (os, id) {
void (os);
if (!id.match(/^cgroup_.*/))
return netdataDashboard.gaugeChart('Sent', '12%', 'sent');
else
return '';
}
],
info: 'The amount of traffic transferred by the network interface.'
},
'net.packets': {
info: '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.errors': {
info: '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.fifo': { info: '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.drops': { info: '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.compressed': { info: 'The number of correctly transferred compressed packets by the network interface. '+ 'These counters are only meaningful for interfaces which support packet compression (e.g. CSLIP, PPP).' }, 'net.events': { info: '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.duplex': { info: 'The interface\'s latest or current '+ 'duplex that the network adapter '+ 'negotiated with the device it is connected to.
'+ 'Unknown - the duplex mode can not be determined. '+ 'Half duplex - the communication is one direction at a time. '+ 'Full duplex - the interface is able to send and receive data simultaneously.
'+ 'State map: 0 - unknown, 1 - half, 2 - full.
' }, 'net.operstate': { info: 'The current '+ 'operational state of the interface.
'+ 'Unknown - the state can not be determined. '+ 'NotPresent - the interface has missing (typically, hardware) components. '+ 'Down - the interface is unable to transfer data on L1, e.g. ethernet is not plugged or interface is administratively down. '+ 'LowerLayerDown - the interface is down due to state of lower-layer interface(s). '+ 'Testing - the interface is in testing mode, e.g. cable test. It can’t be used for normal traffic until tests complete. '+ 'Dormant - the interface is L1 up, but waiting for an external event, e.g. for a protocol to establish. '+ 'Up - the interface is ready to pass packets and can be used.
'+ 'State map: 0 - unknown, 1 - notpresent, 2 - down, 3 - lowerlayerdown, 4 - testing, 5 - dormant, 6 - up.
' }, 'net.carrier': { info: 'The current physical link state of the interface.
'+ 'State map: 0 - down, 1 - up.
' }, 'net.speed': { info: '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.mtu': { info: '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.' }, // ------------------------------------------------------------------------ // WIRELESS NETWORK INTERFACES 'wireless.link_quality': { info: 'Overall quality of the link. '+ 'May be based on the level of contention or interference, the bit or frame error rate, '+ 'how good the received signal is, some timing synchronisation, or other hardware metric.' }, 'wireless.signal_level': { info: 'Received signal strength '+ '(RSSI).' }, 'wireless.noise_level': { info: 'Background noise level (when no packet is transmitted).' }, 'wireless.discarded_packets': { info: 'The number of discarded packets.
'+ 'NWID - received packets with a different NWID or ESSID. '+ 'Used to detect configuration problems or adjacent network existence (on the same frequency). '+ 'Crypt - received packets that the hardware was unable to code/encode. '+ 'This can be used to detect invalid encryption settings. '+ 'Frag - received packets for which the hardware was not able to properly re-assemble '+ 'the link layer fragments (most likely one was missing). '+ 'Retry - packets that the hardware failed to deliver. '+ 'Most MAC protocols will retry the packet a number of times before giving up. '+ 'Misc - other packets lost in relation with specific wireless operations.' }, 'wireless.missed_beacons': { info: 'The number of periodic '+ 'beacons '+ 'from the Cell or the Access Point have been missed. '+ 'Beacons are sent at regular intervals to maintain the cell coordination, '+ 'failure to receive them usually indicates that the card is out of range.' }, // ------------------------------------------------------------------------ // INFINIBAND 'ib.bytes': { info: 'The amount of traffic transferred by the port.' }, 'ib.packets': { info: 'The number of packets transferred by the port.' }, 'ib.errors': { info: 'The number of errors encountered by the port.' }, 'ib.hwerrors': { info: 'The number of hardware errors encountered by the port.' }, 'ib.hwpackets': { info: 'The number of hardware packets transferred by the port.' }, // ------------------------------------------------------------------------ // NETFILTER 'netfilter.sockets': { colors: '#88AA00', heads: [ netdataDashboard.gaugeChart('Active Connections', '12%', '', '#88AA00') ] }, 'netfilter.new': { heads: [ netdataDashboard.gaugeChart('New Connections', '12%', 'new', '#5555AA') ] }, // ------------------------------------------------------------------------ // IPVS 'ipvs.sockets': { info: 'Total created connections for all services and their servers. '+ 'To see the IPVS connection table, runipvsadm -Lnc.'
},
'ipvs.packets': {
info: 'Total transferred packets for all services and their servers.'
},
'ipvs.net': {
info: 'Total network traffic for all services and their servers.'
},
// ------------------------------------------------------------------------
// DISKS
'disk.util': {
colors: '#FF5588',
heads: [
netdataDashboard.gaugeChart('Utilization', '12%', '', '#FF5588')
],
info: '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.busy': {
colors: '#FF5588',
info: 'Disk Busy Time measures the amount of time the disk was busy with something.'
},
'disk.backlog': {
colors: '#0099CC',
info: '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.io': {
heads: [
netdataDashboard.gaugeChart('Read', '12%', 'reads'),
netdataDashboard.gaugeChart('Write', '12%', 'writes')
],
info: 'The amount of data transferred to and from disk.'
},
'disk_ext.io': {
info: 'The amount of discarded data that are no longer in use by a mounted file system.'
},
'disk.ops': {
info: '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_ext.ops': {
info: 'The number (after merges) of completed discard/flush requests.
'+ 'Discard commands inform disks which blocks of data are no longer considered to be in use and therefore can be erased internally. '+ 'They are useful for solid-state drivers (SSDs) and thinly-provisioned storage. '+ 'Discarding/trimming enables the SSD to handle garbage collection more efficiently, '+ 'which would otherwise slow future write operations to the involved blocks down.
'+ 'Flush operations transfer all modified in-core data (i.e., modified buffer cache pages) to the disk device '+ 'so that all changed information can be retrieved even if the system crashes or is rebooted. '+ 'Flush requests are executed by disks. Flush requests are not tracked for partitions. '+ 'Before being merged, flush operations are counted as writes.
' }, 'disk.qops': { info: 'I/O operations currently in progress. This metric is a snapshot - it is not an average over the last interval.' }, 'disk.iotime': { height: 0.5, info: '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_ext.iotime': { height: 0.5, info: '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.mops': { height: 0.5, info: '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_ext.mops': { height: 0.5, info: 'The number of merged discard disk operations. Discard operations which are adjacent to each other may be merged for efficiency.' }, 'disk.svctm': { height: 0.5, info: '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.latency_io': { height: 0.5, info: 'Disk I/O latency is the time it takes for an I/O request to be completed. Latency is the single most important metric to focus on when it comes to storage performance, under most circumstances. For hard drives, an average latency somewhere between 10 to 20 ms can be considered acceptable. For SSD (Solid State Drives), depending on the workload it should never reach higher than 1-3 ms. In most cases, workloads will experience less than 1ms latency numbers. The dimensions refer to time intervals. This chart is based on the bio_tracepoints tool of the ebpf_exporter.' }, 'disk.avgsz': { height: 0.5, info: 'The average I/O operation size.' }, 'disk_ext.avgsz': { height: 0.5, info: 'The average discard operation size.' }, 'disk.await': { height: 0.5, info: '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_ext.await': { height: 0.5, info: '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.space': { info: 'Disk space utilization. reserved for root is automatically reserved by the system to prevent the root user from getting out of space.' }, 'disk.inodes': { info: '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.bcache_hit_ratio': { info: 'Bcache (block cache) is a cache in the block layer of Linux kernel, '+ 'which is used for accessing secondary storage devices. '+ 'It allows one or more fast storage devices, such as flash-based solid-state drives (SSDs), '+ 'to act as a cache for one or more slower storage devices, such as hard disk drives (HDDs).
'+ 'Percentage of data requests that were fulfilled right from the block cache. '+ 'Hits and misses are counted per individual IO as bcache sees them. '+ 'A partial hit is counted as a miss.
' }, 'disk.bcache_rates': { info: 'Throttling rates. '+ 'To avoid congestions bcache tracks latency to the cache device, and gradually throttles traffic if the latency exceeds a threshold. ' + 'If the writeback percentage is nonzero, bcache tries to keep around this percentage of the cache dirty by '+ 'throttling background writeback and using a PD controller to smoothly adjust the rate.' }, 'disk.bcache_size': { info: 'The amount of dirty data for this backing device in the cache.' }, 'disk.bcache_usage': { info: 'The percentage of cache device which does not contain dirty data, and could potentially be used for writeback.' }, 'disk.bcache_cache_read_races': { info: 'Read races happen when a bucket was reused and invalidated while data was being read from the cache. '+ 'When this occurs the data is reread from the backing device. '+ 'IO errors are decayed by the half life. '+ 'If the decaying count reaches the limit, dirty data is written out and the cache is disabled.' }, 'disk.bcache': { info: 'Hits and misses are counted per individual IO as bcache sees them; a partial hit is counted as a miss. '+ 'Collisions happen when data was going to be inserted into the cache from a cache miss, '+ 'but raced with a write and data was already present. '+ 'Cache miss reads are rounded up to the readahead size, but without overlapping existing cache entries.' }, 'disk.bcache_bypass': { info: 'Hits and misses for IO that is intended to skip the cache.' }, 'disk.bcache_cache_alloc': { info: 'Working set size.
'+ 'Unused is the percentage of the cache that does not contain any data. '+ 'Dirty is the data that is modified in the cache but not yet written to the permanent storage. '+ 'Clean data matches the data stored on the permanent storage. '+ 'Metadata is bcache\'s metadata overhead.
' }, // ------------------------------------------------------------------------ // NFS client 'nfs.net': { info: 'The number of received UDP and TCP packets.' }, 'nfs.rpc': { info: 'Remote Procedure Call (RPC) statistics.
'+ 'Calls - all RPC calls. '+ 'Retransmits - retransmitted calls. '+ 'AuthRefresh - authentication refresh calls (validating credentials with the server).' }, 'nfs.proc2': { info: 'NFSv2 RPC calls. The individual metrics are described in '+ 'RFC1094.' }, 'nfs.proc3': { info: 'NFSv3 RPC calls. The individual metrics are described in '+ 'RFC1813.' }, 'nfs.proc4': { info: 'NFSv4 RPC calls. The individual metrics are described in '+ 'RFC8881.' }, // ------------------------------------------------------------------------ // NFS server 'nfsd.readcache': { info: 'Reply cache statistics. '+ 'The reply cache keeps track of responses to recently performed non-idempotent transactions, and '+ 'in case of a replay, the cached response is sent instead of attempting to perform the operation again.
'+ 'Hits - client did not receive a reply and re-transmitted its request. This event is undesirable. '+ 'Misses - an operation that requires caching (idempotent). '+ 'Nocache - an operation that does not require caching (non-idempotent).' }, 'nfsd.filehandles': { info: 'File handle statistics. '+ 'File handles are small pieces of memory that keep track of what file is opened.
'+ 'Stale - happen when a file handle references a location that has been recycled. '+ 'This also occurs when the server loses connection and '+ 'applications are still using files that are no longer accessible.' }, 'nfsd.io': { info: 'The amount of data transferred to and from disk.' }, 'nfsd.threads': { info: 'The number of threads used by the NFS daemon.' }, 'nfsd.readahead': { info: '
Read-ahead cache statistics. '+ 'NFS read-ahead predictively requests blocks from a file in advance of I/O requests by the application. '+ 'It is designed to improve client sequential read throughput.
'+ '10%-100% - histogram of depth the block was found. '+ 'This means how far the cached block is from the original block that was first requested. '+ 'Misses - not found in the read-ahead cache.
' }, 'nfsd.net': { info: 'The number of received UDP and TCP packets.' }, 'nfsd.rpc': { info: 'Remote Procedure Call (RPC) statistics.
'+ 'Calls - all RPC calls. '+ 'BadAuth - bad authentication. '+ 'It does not count if you try to mount from a machine that it\'s not in your exports file. '+ 'BadFormat - other errors.' }, 'nfsd.proc2': { info: 'NFSv2 RPC calls. The individual metrics are described in '+ 'RFC1094.' }, 'nfsd.proc3': { info: 'NFSv3 RPC calls. The individual metrics are described in '+ 'RFC1813.' }, 'nfsd.proc4': { info: 'NFSv4 RPC calls. The individual metrics are described in '+ 'RFC8881.' }, 'nfsd.proc4ops': { info: 'NFSv4 RPC operations. The individual metrics are described in '+ 'RFC8881.' }, // ------------------------------------------------------------------------ // ZFS 'zfs.arc_size': { info: 'The size of the ARC.
'+ 'Arcsz - actual size. '+ 'Target - target size that the ARC is attempting to maintain (adaptive). '+ 'Min - minimum size limit. When the ARC is asked to shrink, it will stop shrinking at this value. '+ 'Min - maximum size limit.
' }, 'zfs.l2_size': { info: 'The size of the L2ARC.
'+ 'Actual - size of compressed data. '+ 'Size - size of uncompressed data.
' }, 'zfs.reads': { info: 'The number of read requests.
'+ 'ARC - all prefetch and demand requests. '+ 'Demand - triggered by an application request. '+ 'Prefetch - triggered by the prefetch mechanism, not directly from an application request. '+ 'Metadata - metadata read requests. '+ 'L2 - L2ARC read requests.
' }, 'zfs.bytes': { info: 'The amount of data transferred to and from the L2ARC cache devices.' }, 'zfs.hits': { info: 'Hit rate of the ARC read requests.
'+ 'Hits - a data block was in the ARC DRAM cache and returned. '+ 'Misses - a data block was not in the ARC DRAM cache. '+ 'It will be read from the L2ARC cache devices (if available and the data is cached on them) or the pool disks.
' }, 'zfs.dhits': { info: 'Hit rate of the ARC data and metadata demand read requests. '+ 'Demand requests are triggered by an application request.
'+ 'Hits - a data block was in the ARC DRAM cache and returned. '+ 'Misses - a data block was not in the ARC DRAM cache. '+ 'It will be read from the L2ARC cache devices (if available and the data is cached on them) or the pool disks.
' }, 'zfs.phits': { info: 'Hit rate of the ARC data and metadata prefetch read requests. '+ 'Prefetch requests are triggered by the prefetch mechanism, not directly from an application request.
'+ 'Hits - a data block was in the ARC DRAM cache and returned. '+ 'Misses - a data block was not in the ARC DRAM cache. '+ 'It will be read from the L2ARC cache devices (if available and the data is cached on them) or the pool disks.
' }, 'zfs.mhits': { info: 'Hit rate of the ARC metadata read requests.
'+ 'Hits - a data block was in the ARC DRAM cache and returned. '+ 'Misses - a data block was not in the ARC DRAM cache. '+ 'It will be read from the L2ARC cache devices (if available and the data is cached on them) or the pool disks.
' }, 'zfs.l2hits': { info: 'Hit rate of the L2ARC lookups.
'+ 'Hits - a data block was in the L2ARC cache and returned. '+ 'Misses - a data block was not in the L2ARC cache. '+ 'It will be read from the pool disks.' }, 'zfs.demand_data_hits': { info: 'Hit rate of the ARC data demand read requests. '+ 'Demand requests are triggered by an application request.
'+ 'Hits - a data block was in the ARC DRAM cache and returned. '+ 'Misses - a data block was not in the ARC DRAM cache. '+ 'It will be read from the L2ARC cache devices (if available and the data is cached on them) or the pool disks.' }, 'zfs.prefetch_data_hits': { info: 'Hit rate of the ARC data prefetch read requests. '+ 'Prefetch requests are triggered by the prefetch mechanism, not directly from an application request.
'+ 'Hits - a data block was in the ARC DRAM cache and returned. '+ 'Misses - a data block was not in the ARC DRAM cache. '+ 'It will be read from the L2ARC cache devices (if available and the data is cached on them) or the pool disks.
' }, 'zfs.list_hits': { info: 'MRU (most recently used) and MFU (most frequently used) cache list hits. '+ 'MRU and MFU lists contain metadata for requested blocks which are cached. '+ 'Ghost lists contain metadata of the evicted pages on disk.' }, 'zfs.arc_size_breakdown': { info: 'The size of MRU (most recently used) and MFU (most frequently used) cache.' }, 'zfs.memory_ops': { info: 'Memory operation statistics.
'+ 'Direct - synchronous memory reclaim. Data is evicted from the ARC and free slabs reaped. '+ 'Throttled - number of times that ZFS had to limit the ARC growth. '+ 'A constant increasing of the this value can indicate excessive pressure to evict data from the ARC. '+ 'Indirect - asynchronous memory reclaim. It reaps free slabs from the ARC cache.
' }, 'zfs.important_ops': { info: 'Eviction and insertion operation statistics.
'+ 'EvictSkip - skipped data eviction operations. '+ 'Deleted - old data is evicted (deleted) from the cache. '+ 'MutexMiss - an attempt to get hash or data block mutex when it is locked during eviction. '+ 'HashCollisions - occurs when two distinct data block numbers have the same hash value.
' }, 'zfs.actual_hits': { info: 'MRU and MFU cache hit rate.
'+ 'Hits - a data block was in the ARC DRAM cache and returned. '+ 'Misses - a data block was not in the ARC DRAM cache. '+ 'It will be read from the L2ARC cache devices (if available and the data is cached on them) or the pool disks.
' }, 'zfs.hash_elements': { info: 'Data Virtual Address (DVA) hash table element statistics.
'+ 'Current - current number of elements. '+ 'Max - maximum number of elements seen.
' }, 'zfs.hash_chains': { info: 'Data Virtual Address (DVA) hash table chain statistics. '+ 'A chain is formed when two or more distinct data block numbers have the same hash value.
'+ 'Current - current number of chains. '+ 'Max - longest length seen for a chain. '+ 'If the value is high, performance may degrade as the hash locks are held longer while the chains are walked.
' }, // ------------------------------------------------------------------------ // ZFS pools 'zfspool.state': { info: 'ZFS pool state. '+ 'The overall health of a pool, as reported byzpool status, '+
'is determined by the aggregate state of all devices within the pool. ' +
'For states description, '+
'see ZFS documentation.'
},
// ------------------------------------------------------------------------
// MYSQL
'mysql.net': {
info: 'The amount of data sent to mysql clients (out) and received from mysql clients (in).'
},
'mysql.queries': {
info: 'The number of statements executed by the server.-1: unknown, ' +
'0: primary (primary group configuration, quorum present), ' +
'1: non-primary (non-primary group configuration, quorum lost), ' +
'2: disconnected(not connected to group, retrying).'
},
'mysql.galera_cluster_state': {
info:
'0: Undefined, ' +
'1: Joining, ' +
'2: Donor/Desynced, ' +
'3: Joined, ' +
'4: Synced, ' +
'5: Inconsistent.'
},
'mysql.galera_cluster_weight': {
info: 'The value is counted as a sum of pc.weight of the nodes in the current Primary Component.'
},
'mysql.galera_connected': {
info: '0 means that the node has not yet connected to any of the cluster components. ' +
'This may be due to misconfiguration.'
},
'mysql.open_transactions': {
info: 'The number of locally running transactions which have been registered inside the wsrep provider. ' +
'This means transactions which have made operations which have caused write set population to happen. ' +
'Transactions which are read only are not counted.'
},
// ------------------------------------------------------------------------
// POSTGRESQL
'postgres.db_stat_blks': {
info: 'Blocks reads from disk or cache.response time describes the time passed between request and response. ' +
'Currently, the accuracy of the response time is low and should be used as reference only.'
},
'httpcheck.responselength': {
info: 'The response length counts the number of characters in the response body. For static pages, this should be mostly constant.'
},
'httpcheck.status': {
valueRange: "[0, 1]",
info: 'This chart verifies the response of the webserver. Each status dimension will have a value of 1 if triggered. ' +
'Dimension success is 1 only if all constraints are satisfied. ' +
'This chart is most useful for alarms or third-party apps.'
},
// ------------------------------------------------------------------------
// NETDATA
'netdata.response_time': {
info: '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.ebpf_threads': {
info: 'Show total number of threads and number of active threads. For more details about the threads, see the official documentation.'
},
'netdata.ebpf_load_methods': {
info: 'Show number of threads loaded using legacy code (independent binary) or CO-RE (Compile Once Run Everywhere).'
},
// ------------------------------------------------------------------------
// RETROSHARE
'retroshare.bandwidth': {
info: 'RetroShare inbound and outbound traffic.',
mainheads: [
netdataDashboard.gaugeChart('Received', '12%', 'bandwidth_down_kb'),
netdataDashboard.gaugeChart('Sent', '12%', 'bandwidth_up_kb')
]
},
'retroshare.peers': {
info: 'Number of (connected) RetroShare friends.',
mainheads: [
function (os, id) {
void (os);
return '';
}
]
},
'retroshare.dht': {
info: 'Statistics about RetroShare\'s DHT. These values are estimated!'
},
// ------------------------------------------------------------------------
// fping
'fping.quality': {
colors: NETDATA.colors[10],
height: 0.5
},
'fping.packets': {
height: 0.5
},
// ------------------------------------------------------------------------
// containers
'cgroup.cpu_limit': {
valueRange: "[0, null]",
mainheads: [
function (os, id) {
void (os);
cgroupCPULimitIsSet = 1;
return '';
}
],
info: 'Total CPU utilization within the configured or system-wide (if not set) limits. '+
'When the CPU utilization of a cgroup exceeds the limit for the configured period, '+
'the tasks belonging to its hierarchy will be throttled and are not allowed to run again until the next period.'
},
'cgroup.cpu': {
mainheads: [
function (os, id) {
void (os);
if (cgroupCPULimitIsSet === 0) {
return '';
} else
return '';
}
],
info: 'Total CPU utilization within the system-wide CPU resources (all cores). '+
'The amount of time spent by tasks of the cgroup in '+
'user and kernel modes.'
},
'cgroup.cpu_per_core': {
info: 'Total CPU utilization per core within the system-wide CPU resources.'
},
'cgroup.cpu_pressure': {
info: 'CPU Pressure Stall Information. '+
'Some indicates the share of time in which at least some tasks are stalled on CPU. '+
'The ratios (in %) are tracked as recent trends over 10-, 60-, and 300-second windows.'
},
'cgroup.mem_utilization': {
info: 'RAM utilization within the configured or system-wide (if not set) limits. '+
'When the RAM utilization of a cgroup exceeds the limit, '+
'OOM killer will start killing the tasks belonging to the cgroup.'
},
'cgroup.mem_usage_limit': {
mainheads: [
function (os, id) {
void (os);
cgroupMemLimitIsSet = 1;
return '';
}
],
info: 'RAM usage within the configured or system-wide (if not set) limits. '+
'When the RAM usage of a cgroup exceeds the limit, '+
'OOM killer will start killing the tasks belonging to the cgroup.'
},
'cgroup.mem_usage': {
mainheads: [
function (os, id) {
void (os);
if (cgroupMemLimitIsSet === 0) {
return '';
} else
return '';
}
],
info: 'The amount of used RAM and swap memory.'
},
'cgroup.mem': {
info: 'Memory usage statistics. '+
'The individual metrics are described in the memory.stat section for '+
'cgroup-v1 '+
'and '+
'cgroup-v2.'
},
'cgroup.mem_failcnt': {
info: 'The number of memory usage hits limits.'
},
'cgroup.writeback': {
info: 'Dirty is the amount of memory waiting to be written to disk. Writeback is how much memory is actively being written to disk.'
},
'cgroup.mem_activity': {
info: 'Memory accounting statistics.
'+ 'In - a page is accounted as either mapped anon page (RSS) or cache page (Page Cache) to the cgroup. '+ 'Out - a page is unaccounted from the cgroup.
' }, 'cgroup.pgfaults': { info: 'Memory page fault statistics.
'+ 'Pgfault - all page faults. '+ 'Swap - major page faults.
' }, 'cgroup.memory_pressure': { info: 'Memory Pressure Stall Information. '+ 'Some indicates the share of time in which at least some tasks are stalled on memory. '+ 'The ratios (in %) are tracked as recent trends over 10-, 60-, and 300-second windows.' }, 'cgroup.memory_full_pressure': { info: 'Memory Pressure Stall Information. '+ 'Full indicates the share of time in which all non-idle tasks are stalled on memory 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. '+ 'The ratios (in %) are tracked as recent trends over 10-, 60-, and 300-second windows.' }, 'cgroup.io': { info: 'The amount of data transferred to and from specific devices as seen by the CFQ scheduler. '+ 'It is not updated when the CFQ scheduler is operating on a request queue.' }, 'cgroup.serviced_ops': { info: 'The number of I/O operations performed on specific devices as seen by the CFQ scheduler.' }, 'cgroup.queued_ops': { info: 'The number of requests queued for I/O operations.' }, 'cgroup.merged_ops': { info: 'The number of BIOS requests merged into requests for I/O operations.' }, 'cgroup.throttle_io': { mainheads: [ function (os, id) { void (os); return ''; }, function (os, id) { void (os); return ''; } ], info: 'The amount of data transferred to and from specific devices as seen by the throttling policy.' }, 'cgroup.throttle_serviced_ops': { info: 'The number of I/O operations performed on specific devices as seen by the throttling policy.' }, 'cgroup.io_pressure': { info: 'I/O Pressure Stall Information. '+ 'Some indicates the share of time in which at least some tasks are stalled on I/O. '+ 'The ratios (in %) are tracked as recent trends over 10-, 60-, and 300-second windows.' }, 'cgroup.io_full_pressure': { info: 'I/O Pressure Stall Information. '+ 'Full indicates the share of time in which all non-idle tasks are stalled on I/O 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. '+ 'The ratios (in %) are tracked as recent trends over 10-, 60-, and 300-second windows.' }, 'cgroup.swap_read': { info: 'The functionswap_readpage is called when the kernel reads a page from swap memory. This chart is provided by eBPF plugin.'
},
'cgroup.swap_write': {
info: 'The function swap_writepage is called when the kernel writes a page to swap memory. This chart is provided by eBPF plugin.'
},
'cgroup.fd_open': {
info: 'Calls to the internal function do_sys_open (for kernels newer than 5.5.19 we add a kprobe to do_sys_openat2. ), which is the common function called from' +
' open(2) ' +
' and openat(2). '
},
'cgroup.fd_open_error': {
info: 'Failed calls to the internal function do_sys_open (for kernels newer than 5.5.19 we add a kprobe to do_sys_openat2. ).'
},
'cgroup.fd_close': {
info: 'Calls to the internal function __close_fd or close_fd according to your kernel version, which is called from' +
' close(2). '
},
'cgroup.fd_close_error': {
info: 'Failed calls to the internal function __close_fd or close_fd according to your kernel version.'
},
'cgroup.vfs_unlink': {
info: 'Calls to the function vfs_unlink. This chart does not show all events that remove files from the filesystem, because filesystems can create their own functions to remove files.'
},
'cgroup.vfs_write': {
info: 'Successful calls to the function vfs_write. This chart may not show all filesystem events if it uses other functions to store data on disk.'
},
'cgroup.vfs_write_error': {
info: 'Failed calls to the function vfs_write. This chart may not show all filesystem events if it uses other functions to store data on disk.'
},
'cgroup.vfs_read': {
info: 'Successful calls to the function vfs_read. This chart may not show all filesystem events if it uses other functions to store data on disk.'
},
'cgroup.vfs_read_error': {
info: 'Failed calls to the function vfs_read. This chart may not show all filesystem events if it uses other functions to store data on disk.'
},
'cgroup.vfs_write_bytes': {
info: 'Total of bytes successfully written using the function vfs_write.'
},
'cgroup.vfs_read_bytes': {
info: 'Total of bytes successfully read using the function vfs_read.'
},
'cgroup.process_create': {
info: 'Calls to either do_fork, or kernel_clone if you are running kernel newer than 5.9.16, to create a new task, which is the common name used to define process and tasks inside the kernel. Netdata identifies the process by counting the number of calls to sys_clone that do not have the flag CLONE_THREAD set.'
},
'cgroup.thread_create': {
info: 'Calls to either do_fork, or kernel_clone if you are running kernel newer than 5.9.16, to create a new task, which is the common name used to define process and tasks inside the kernel. Netdata identifies the threads by counting the number of calls to sys_clone that have the flag CLONE_THREAD set.'
},
'cgroup.task_exit': {
info: 'Calls to the function responsible for closing (do_exit) tasks.'
},
'cgroup.task_close': {
info: 'Calls to the functions responsible for releasing (release_task) tasks.'
},
'cgroup.task_error': {
info: 'Number of errors to create a new process or thread. This chart is provided by eBPF plugin.'
},
'cgroup.dc_ratio': {
info: 'Percentage of file accesses that were present in the directory cache. 100% means that every file that was accessed was present in the directory cache. If files are not present in the directory cache 1) they are not present in the file system, 2) the files were not accessed before. Read more about directory cache. Netdata also gives a summary for these charts in Filesystem submenu.'
},
'cgroup.dc_reference': {
info: 'Counters of file accesses. Reference is when there is a file access, see the filesystem.dc_reference chart for more context. Read more about directory cache.'
},
'cgroup.dc_not_cache': {
info: 'Counters of file accesses. Slow is when there is a file access and the file is not present in the directory cache, see the filesystem.dc_reference chart for more context. Read more about directory cache.'
},
'cgroup.dc_not_found': {
info: 'Counters of file accesses. Miss is when there is file access and the file is not found in the filesystem, see the filesystem.dc_reference chart for more context. Read more about directory cache.'
},
'cgroup.shmget': {
info: 'Number of times the syscall shmget is called. Netdata also gives a summary for these charts in System overview.'
},
'cgroup.shmat': {
info: 'Number of times the syscall shmat is called.'
},
'cgroup.shmdt': {
info: 'Number of times the syscall shmdt is called.'
},
'cgroup.shmctl': {
info: 'Number of times the syscall shmctl is called.'
},
'cgroup.net_bytes_send': {
info: 'Bytes sent by functions tcp_sendmsg.'
},
'cgroup.net_bytes_recv': {
info: 'Bytes received by functions tcp_cleanup_rbuf . We use tcp_cleanup_rbuf instead tcp_recvmsg, because this last misses tcp_read_sock() traffic and we would also need to have more probes to get the socket and package size.'
},
'cgroup.net_tcp_send': {
info: 'The function tcp_sendmsg is used to collect number of bytes sent from TCP connections.'
},
'cgroup.net_tcp_recv': {
info: 'The function tcp_cleanup_rbuf is used to collect number of bytes received from TCP connections.'
},
'cgroup.net_retransmit': {
info: 'The function tcp_retransmit_skb is called when the host did not receive the expected return from a packet sent.'
},
'cgroup.net_udp_send': {
info: 'The function udp_sendmsg is used to collect number of bytes sent from UDP connections.'
},
'cgroup.net_udp_recv': {
info: 'The function udp_recvmsg is used to collect number of bytes received from UDP connections.'
},
'cgroup.cachestat_ratio': {
info: 'When the processor needs to read or write a location in main memory, it checks for a corresponding entry in the page cache. If the entry is there, a page cache hit has occurred and the read is from the cache. If the entry is not there, a page cache miss has occurred and the kernel allocates a new entry and copies in data from the disk. Netdata calculates the percentage of accessed files that are cached on memory. The ratio is calculated counting the accessed cached pages (without counting dirty pages and pages added because of read misses) divided by total access without dirty pages.'
},
'cgroup.cachestat_dirties': {
info: 'Number of dirty(modified) pages cache. Pages in the page cache modified after being brought in are called dirty pages. Since non-dirty pages in the page cache have identical copies in secondary storage (e.g. hard disk drive or solid-state drive), discarding and reusing their space is much quicker than paging out application memory, and is often preferred over flushing the dirty pages into secondary storage and reusing their space.'
},
'cgroup.cachestat_hits': {
info: 'When the processor needs to read or write a location in main memory, it checks for a corresponding entry in the page cache. If the entry is there, a page cache hit has occurred and the read is from the cache. Hits show pages accessed that were not modified (we are excluding dirty pages), this counting also excludes the recent pages inserted for read.'
},
'cgroup.cachestat_misses': {
info: 'When the processor needs to read or write a location in main memory, it checks for a corresponding entry in the page cache. If the entry is not there, a page cache miss has occurred and the cache allocates a new entry and copies in data for the main memory. Misses count page insertions to the memory not related to writing.'
},
// ------------------------------------------------------------------------
// containers (systemd)
'services.cpu': {
info: '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.mem_usage': {
info: 'The amount of used RAM.'
},
'services.mem_rss': {
info: 'The amount of used '+
'RSS memory. '+
'It includes transparent hugepages.'
},
'services.mem_mapped': {
info: 'The size of '+
'memory-mapped files.'
},
'services.mem_cache': {
info: 'The amount of used '+
'page cache memory.'
},
'services.mem_writeback': {
info: 'The amount of file/anon cache that is '+
'queued for syncing '+
'to disk.'
},
'services.mem_pgfault': {
info: 'The number of '+
'page faults. '+
'It includes both minor and major page faults.'
},
'services.mem_pgmajfault': {
info: 'The number of '+
'major '+
'page faults.'
},
'services.mem_pgpgin': {
info: 'The amount of memory charged to the cgroup. '+
'The charging event happens each time a page is accounted as either '+
'mapped anon page(RSS) or cache page(Page Cache) to the cgroup.'
},
'services.mem_pgpgout': {
info: 'The amount of memory uncharged from the cgroup. '+
'The uncharging event happens each time a page is unaccounted from the cgroup.'
},
'services.mem_failcnt': {
info: 'The number of memory usage hits limits.'
},
'services.swap_usage': {
info: 'The amount of used '+
'swap '+
'memory.'
},
'services.io_read': {
info: '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_write': {
info: '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_ops_read': {
info: 'The number of read operations performed on specific devices as seen by the CFQ scheduler.'
},
'services.io_ops_write': {
info: 'The number write operations performed on specific devices as seen by the CFQ scheduler.'
},
'services.throttle_io_read': {
info: 'The amount of data transferred from specific devices as seen by the throttling policy.'
},
'services.throttle_io_write': {
info: 'The amount of data transferred to specific devices as seen by the throttling policy.'
},
'services.throttle_io_ops_read': {
info: 'The number of read operations performed on specific devices as seen by the throttling policy.'
},
'services.throttle_io_ops_write': {
info: 'The number of write operations performed on specific devices as seen by the throttling policy.'
},
'services.queued_io_ops_read': {
info: 'The number of queued read requests.'
},
'services.queued_io_ops_write': {
info: 'The number of queued write requests.'
},
'services.merged_io_ops_read': {
info: 'The number of read requests merged.'
},
'services.merged_io_ops_write': {
info: 'The number of write requests merged.'
},
'services.swap_read': {
info: 'The function swap_readpage is called when the kernel reads a page from swap memory. This chart is provided by eBPF plugin.'
},
'services.swap_write': {
info: 'The function swap_writepage is called when the kernel writes a page to swap memory. This chart is provided by eBPF plugin.'
},
'services.fd_open': {
info: 'Calls to the internal function do_sys_open (for kernels newer than 5.5.19 we add a kprobe to do_sys_openat2. ), which is the common function called from' +
' open(2) ' +
' and openat(2). '
},
'services.fd_open_error': {
info: 'Failed calls to the internal function do_sys_open (for kernels newer than 5.5.19 we add a kprobe to do_sys_openat2. ).'
},
'services.fd_close': {
info: 'Calls to the internal function __close_fd or close_fd according to your kernel version, which is called from' +
' close(2). '
},
'services.fd_close_error': {
info: 'Failed calls to the internal function __close_fd or close_fd according to your kernel version.'
},
'services.vfs_unlink': {
info: 'Calls to the function vfs_unlink. This chart does not show all events that remove files from the filesystem, because filesystems can create their own functions to remove files.'
},
'services.vfs_write': {
info: 'Successful calls to the function vfs_write. This chart may not show all filesystem events if it uses other functions to store data on disk.'
},
'services.vfs_write_error': {
info: 'Failed calls to the function vfs_write. This chart may not show all filesystem events if it uses other functions to store data on disk.'
},
'services.vfs_read': {
info: 'Successful calls to the function vfs_read. This chart may not show all filesystem events if it uses other functions to store data on disk.'
},
'services.vfs_read_error': {
info: 'Failed calls to the function vfs_read. This chart may not show all filesystem events if it uses other functions to store data on disk.'
},
'services.vfs_write_bytes': {
info: 'Total of bytes successfully written using the function vfs_write.'
},
'services.vfs_read_bytes': {
info: 'Total of bytes successfully read using the function vfs_read.'
},
'services.process_create': {
info: 'Calls to either do_fork, or kernel_clone if you are running kernel newer than 5.9.16, to create a new task, which is the common name used to define process and tasks inside the kernel. Netdata identifies the process by counting the number of calls to sys_clone that do not have the flag CLONE_THREAD set.'
},
'services.thread_create': {
info: 'Calls to either do_fork, or kernel_clone if you are running kernel newer than 5.9.16, to create a new task, which is the common name used to define process and tasks inside the kernel. Netdata identifies the threads by counting the number of calls to sys_clone that have the flag CLONE_THREAD set.'
},
'services.task_exit': {
info: 'Calls to the functions responsible for closing (do_exit) tasks.'
},
'services.task_close': {
info: 'Calls to the functions responsible for releasing (release_task) tasks.'
},
'services.task_error': {
info: 'Number of errors to create a new process or thread. This chart is provided by eBPF plugin.'
},
'services.dc_ratio': {
info: 'Percentage of file accesses that were present in the directory cache. 100% means that every file that was accessed was present in the directory cache. If files are not present in the directory cache 1) they are not present in the file system, 2) the files were not accessed before. Read more about directory cache. Netdata also gives a summary for these charts in Filesystem submenu.'
},
'services.dc_reference': {
info: 'Counters of file accesses. Reference is when there is a file access, see the filesystem.dc_reference chart for more context. Read more about directory cache.'
},
'services.dc_not_cache': {
info: 'Counters of file accesses. Slow is when there is a file access and the file is not present in the directory cache, see the filesystem.dc_reference chart for more context. Read more about directory cache.'
},
'services.dc_not_found': {
info: 'Counters of file accesses. Miss is when there is file access and the file is not found in the filesystem, see the filesystem.dc_reference chart for more context. Read more about directory cache.'
},
'services.shmget': {
info: 'Number of times the syscall shmget is called. Netdata also gives a summary for these charts in System overview.'
},
'services.shmat': {
info: 'Number of times the syscall shmat is called.'
},
'services.shmdt': {
info: 'Number of times the syscall shmdt is called.'
},
'services.shmctl': {
info: 'Number of times the syscall shmctl is called.'
},
'services.net_bytes_send': {
info: 'Bytes sent by functions tcp_sendmsg.'
},
'services.net_bytes_recv': {
info: 'Bytes received by functions tcp_cleanup_rbuf . We use tcp_cleanup_rbuf instead tcp_recvmsg, because this last misses tcp_read_sock() traffic and we would also need to have more probes to get the socket and package size.'
},
'services.net_tcp_send': {
info: 'The function tcp_sendmsg is used to collect number of bytes sent from TCP connections.'
},
'services.net_tcp_recv': {
info: 'The function tcp_cleanup_rbuf is used to collect number of bytes received from TCP connections.'
},
'services.net_retransmit': {
info: 'The function tcp_retransmit_skb is called when the host did not receive the expected return from a packet sent.'
},
'services.net_udp_send': {
info: 'The function udp_sendmsg is used to collect number of bytes sent from UDP connections.'
},
'services.net_udp_recv': {
info: 'The function udp_recvmsg is used to collect number of bytes received from UDP connections.'
},
'services.cachestat_ratio': {
info: 'When the processor needs to read or write a location in main memory, it checks for a corresponding entry in the page cache. If the entry is there, a page cache hit has occurred and the read is from the cache. If the entry is not there, a page cache miss has occurred and the kernel allocates a new entry and copies in data from the disk. Netdata calculates the percentage of accessed files that are cached on memory. The ratio is calculated counting the accessed cached pages (without counting dirty pages and pages added because of read misses) divided by total access without dirty pages.'
},
'services.cachestat_dirties': {
info: 'Number of dirty(modified) pages cache. Pages in the page cache modified after being brought in are called dirty pages. Since non-dirty pages in the page cache have identical copies in secondary storage (e.g. hard disk drive or solid-state drive), discarding and reusing their space is much quicker than paging out application memory, and is often preferred over flushing the dirty pages into secondary storage and reusing their space.'
},
'services.cachestat_hits': {
info: 'When the processor needs to read or write a location in main memory, it checks for a corresponding entry in the page cache. If the entry is there, a page cache hit has occurred and the read is from the cache. Hits show pages accessed that were not modified (we are excluding dirty pages), this counting also excludes the recent pages inserted for read.'
},
'services.cachestat_misses': {
info: 'When the processor needs to read or write a location in main memory, it checks for a corresponding entry in the page cache. If the entry is not there, a page cache miss has occurred and the cache allocates a new entry and copies in data for the main memory. Misses count page insertions to the memory not related to writing.'
},
// ------------------------------------------------------------------------
// beanstalkd
// system charts
'beanstalk.cpu_usage': {
info: 'Amount of CPU Time for user and system used by beanstalkd.'
},
// This is also a per-tube stat
'beanstalk.jobs_rate': {
info: 'The rate of jobs processed by the beanstalkd served.'
},
'beanstalk.connections_rate': {
info: 'The rate of connections opened to beanstalkd.'
},
'beanstalk.commands_rate': {
info: 'The rate of commands received by beanstalkd.'
},
'beanstalk.current_tubes': {
info: 'Total number of current tubes on the server including the default tube (which always exists).'
},
'beanstalk.current_jobs': {
info: 'Current number of jobs in all tubes grouped by status: urgent, ready, reserved, delayed and buried.'
},
'beanstalk.current_connections': {
info: 'Current number of connections group by connection type: written, producers, workers, waiting.'
},
'beanstalk.binlog': {
info: 'The rate of records written to binlog and migrated as part of compaction.'
},
'beanstalk.uptime': {
info: 'Total time beanstalkd server has been up for.'
},
// tube charts
'beanstalk.jobs': {
info: 'Number of jobs currently in the tube grouped by status: urgent, ready, reserved, delayed and buried.'
},
'beanstalk.connections': {
info: 'The current number of connections to this tube grouped by connection type; using, waiting and watching.'
},
'beanstalk.commands': {
info: 'The rate of delete and pause commands executed by beanstalkd.'
},
'beanstalk.pause': {
info: 'Shows info on how long the tube has been paused for, and how long is left remaining on the pause.'
},
// ------------------------------------------------------------------------
// ceph
'ceph.general_usage': {
info: 'The usage and available space in all ceph cluster.'
},
'ceph.general_objects': {
info: 'Total number of objects storage on ceph cluster.'
},
'ceph.general_bytes': {
info: 'Cluster read and write data per second.'
},
'ceph.general_operations': {
info: 'Number of read and write operations per second.'
},
'ceph.general_latency': {
info: 'Total of apply and commit latency in all OSDs. The apply latency is the total time taken to flush an update to disk. The commit latency is the total time taken to commit an operation to the journal.'
},
'ceph.pool_usage': {
info: 'The usage space in each pool.'
},
'ceph.pool_objects': {
info: 'Number of objects presents in each pool.'
},
'ceph.pool_read_bytes': {
info: 'The rate of read data per second in each pool.'
},
'ceph.pool_write_bytes': {
info: 'The rate of write data per second in each pool.'
},
'ceph.pool_read_objects': {
info: 'Number of read objects per second in each pool.'
},
'ceph.pool_write_objects': {
info: 'Number of write objects per second in each pool.'
},
'ceph.osd_usage': {
info: 'The usage space in each OSD.'
},
'ceph.osd_size': {
info: "Each OSD's size"
},
'ceph.apply_latency': {
info: 'Time taken to flush an update in each OSD.'
},
'ceph.commit_latency': {
info: 'Time taken to commit an operation to the journal in each OSD.'
},
// ------------------------------------------------------------------------
// web_log
'web_log.response_statuses': {
info: 'Web server responses by type. success includes 1xx, 2xx, 304 and 401, error includes 5xx, redirect includes 3xx except 304, bad includes 4xx except 401, other are all the other responses.',
mainheads: [
function (os, id) {
void (os);
return '';
},
function (os, id) {
void (os);
return '';
},
function (os, id) {
void (os);
return '';
},
function (os, id) {
void (os);
return '';
}
]
},
'web_log.response_codes': {
info: 'Web server responses by code family. ' +
'According to the standards 1xx are informational responses, ' +
'2xx are successful responses, ' +
'3xx are redirects (although they include 304 which is used as "not modified"), ' +
'4xx are bad requests, ' +
'5xx are internal server errors, ' +
'other are non-standard responses, ' +
'unmatched counts the lines in the log file that are not matched by the plugin (let us know if you have any unmatched).'
},
'web_log.response_time': {
mainheads: [
function (os, id) {
void (os);
return '';
}
]
},
'web_log.detailed_response_codes': {
info: 'Number of responses for each response code individually.'
},
'web_log.requests_per_ipproto': {
info: 'Web server requests received per IP protocol version.'
},
'web_log.clients': {
info: 'Unique client IPs accessing the web server, within each data collection iteration. If data collection is per second, this chart shows unique client IPs per second.'
},
'web_log.clients_all': {
info: 'Unique client IPs accessing the web server since the last restart of netdata. This plugin keeps in memory all the unique IPs that have accessed the web server. On very busy web servers (several millions of unique IPs) you may want to disable this chart (check /etc/netdata/python.d/web_log.conf).'
},
// ------------------------------------------------------------------------
// web_log for squid
'web_log.squid_response_statuses': {
info: 'Squid responses by type. ' +
'success includes 1xx, 2xx, 000, 304, ' +
'error includes 5xx and 6xx, ' +
'redirect includes 3xx except 304, ' +
'bad includes 4xx, ' +
'other are all the other responses.',
mainheads: [
function (os, id) {
void (os);
return '';
},
function (os, id) {
void (os);
return '';
},
function (os, id) {
void (os);
return '';
},
function (os, id) {
void (os);
return '';
}
]
},
'web_log.squid_response_codes': {
info: 'Web server responses by code family. ' +
'According to HTTP standards 1xx are informational responses, ' +
'2xx are successful responses, ' +
'3xx are redirects (although they include 304 which is used as "not modified"), ' +
'4xx are bad requests, ' +
'5xx are internal server errors. ' +
'Squid also defines 000 mostly for UDP requests, and ' +
'6xx for broken upstream servers sending wrong headers. ' +
'Finally, other are non-standard responses, and ' +
'unmatched counts the lines in the log file that are not matched by the plugin (let us know if you have any unmatched).'
},
'web_log.squid_duration': {
mainheads: [
function (os, id) {
void (os);
return '';
}
]
},
'web_log.squid_detailed_response_codes': {
info: 'Number of responses for each response code individually.'
},
'web_log.squid_clients': {
info: 'Unique client IPs accessing squid, within each data collection iteration. If data collection is per second, this chart shows unique client IPs per second.'
},
'web_log.squid_clients_all': {
info: 'Unique client IPs accessing squid since the last restart of netdata. This plugin keeps in memory all the unique IPs that have accessed the server. On very busy squid servers (several millions of unique IPs) you may want to disable this chart (check /etc/netdata/python.d/web_log.conf).'
},
'web_log.squid_transport_methods': {
info: 'Break down per delivery method: TCP are requests on the HTTP port (usually 3128), ' +
'UDP are requests on the ICP port (usually 3130), or HTCP port (usually 4128). ' +
'If ICP logging was disabled using the log_icp_queries option, no ICP replies will be logged. ' +
'NONE are used to state that squid delivered an unusual response or no response at all. ' +
'Seen with cachemgr requests and errors, usually when the transaction fails before being classified into one of the above outcomes. ' +
'Also seen with responses to CONNECT requests.'
},
'web_log.squid_code': {
info: 'These are combined squid result status codes. A break down per component is given in the following charts. ' +
'Check the squid documentation about them.'
},
'web_log.squid_handling_opts': {
info: 'These tags are optional and describe why the particular handling was performed or where the request came from. ' +
'CLIENT means that the client request placed limits affecting the response. Usually seen with client issued a no-cache, or analogous cache control command along with the request. Thus, the cache has to validate the object.' +
'IMS states that the client sent a revalidation (conditional) request. ' +
'ASYNC, is used when the request was generated internally by Squid. Usually this is background fetches for cache information exchanges, background revalidation from stale-while-revalidate cache controls, or ESI sub-objects being loaded. ' +
'SWAPFAIL is assigned when the object was believed to be in the cache, but could not be accessed. A new copy was requested from the server. ' +
'REFRESH when a revalidation (conditional) request was sent to the server. ' +
'SHARED when this request was combined with an existing transaction by collapsed forwarding. NOTE: the existing request is not marked as SHARED. ' +
'REPLY when particular handling was requested in the HTTP reply from server or peer. Usually seen on DENIED due to http_reply_access ACLs preventing delivery of servers response object to the client.'
},
'web_log.squid_object_types': {
info: 'These tags are optional and describe what type of object was produced. ' +
'NEGATIVE is only seen on HIT responses, indicating the response was a cached error response. e.g. 404 not found. ' +
'STALE means the object was cached and served stale. This is usually caused by stale-while-revalidate or stale-if-error cache controls. ' +
'OFFLINE when the requested object was retrieved from the cache during offline_mode. The offline mode never validates any object. ' +
'INVALID when an invalid request was received. An error response was delivered indicating what the problem was. ' +
'FAIL is only seen on REFRESH to indicate the revalidation request failed. The response object may be the server provided network error or the stale object which was being revalidated depending on stale-if-error cache control. ' +
'MODIFIED is only seen on REFRESH responses to indicate revalidation produced a new modified object. ' +
'UNMODIFIED is only seen on REFRESH responses to indicate revalidation produced a 304 (Not Modified) status, which was relayed to the client. ' +
'REDIRECT when squid generated an HTTP redirect response to this request.'
},
'web_log.squid_cache_events': {
info: 'These tags are optional and describe whether the response was loaded from cache, network, or otherwise. ' +
'HIT when the response object delivered was the local cache object. ' +
'MEM when the response object came from memory cache, avoiding disk accesses. Only seen on HIT responses. ' +
'MISS when the response object delivered was the network response object. ' +
'DENIED when the request was denied by access controls. ' +
'NOFETCH an ICP specific type, indicating service is alive, but not to be used for this request (sent during "-Y" startup, or during frequent failures, a cache in hit only mode will return either UDP_HIT or UDP_MISS_NOFETCH. Neighbours will thus only fetch hits). ' +
'TUNNEL when a binary tunnel was established for this transaction.'
},
'web_log.squid_transport_errors': {
info: 'These tags are optional and describe some error conditions which occurred during response delivery (if any). ' +
'ABORTED when the response was not completed due to the connection being aborted (usually by the client). ' +
'TIMEOUT, when the response was not completed due to a connection timeout.'
},
// ------------------------------------------------------------------------
// go web_log
'web_log.type_requests': {
info: 'Web server responses by type. success includes 1xx, 2xx, 304 and 401, error includes 5xx, redirect includes 3xx except 304, bad includes 4xx except 401, other are all the other responses.',
mainheads: [
function (os, id) {
void (os);
return '';
},
function (os, id) {
void (os);
return '';
},
function (os, id) {
void (os);
return '';
},
function (os, id) {
void (os);
return '';
}
]
},
'web_log.request_processing_time': {
mainheads: [
function (os, id) {
void (os);
return '';
}
]
},
// ------------------------------------------------------------------------
// Fronius Solar Power
'fronius.power': {
info: 'Positive Grid values mean that power is coming from the grid. Negative values are excess power that is going back into the grid, possibly selling it. ' +
'Photovoltaics is the power generated from the solar panels. ' +
'Accumulator is the stored power in the accumulator, if one is present.'
},
'fronius.autonomy': {
commonMin: true,
commonMax: true,
valueRange: "[0, 100]",
info: 'The Autonomy is the percentage of how autonomous the installation is. An autonomy of 100 % means that the installation is producing more energy than it is needed. ' +
'The Self consumption indicates the ratio between the current power generated and the current load. When it reaches 100 %, the Autonomy declines, since the solar panels can not produce enough energy and need support from the grid.'
},
'fronius.energy.today': {
commonMin: true,
commonMax: true,
valueRange: "[0, null]"
},
// ------------------------------------------------------------------------
// Stiebel Eltron Heat pump installation
'stiebeleltron.system.roomtemp': {
commonMin: true,
commonMax: true,
valueRange: "[0, null]"
},
// ------------------------------------------------------------------------
// Port check
'portcheck.latency': {
info: 'The latency describes the time spent connecting to a TCP port. No data is sent or received. ' +
'Currently, the accuracy of the latency is low and should be used as reference only.'
},
'portcheck.status': {
valueRange: "[0, 1]",
info: 'The status chart verifies the availability of the service. ' +
'Each status dimension will have a value of 1 if triggered. Dimension success is 1 only if connection could be established. ' +
'This chart is most useful for alarms and third-party apps.'
},
// ------------------------------------------------------------------------
'chrony.system': {
info: 'In normal operation, chronyd never steps the system clock, because any jump in the timescale can have adverse consequences for certain application programs. Instead, any error in the system clock is corrected by slightly speeding up or slowing down the system clock until the error has been removed, and then returning to the system clock’s normal speed. A consequence of this is that there will be a period when the system clock (as read by other programs using the gettimeofday() system call, or by the date command in the shell) will be different from chronyd\'s estimate of the current true time (which it reports to NTP clients when it is operating in server mode). The value reported on this line is the difference due to this effect.',
colors: NETDATA.colors[3]
},
'chrony.offsets': {
info: 'last offset is the estimated local offset on the last clock update. RMS offset is a long-term average of the offset value.',
height: 0.5
},
'chrony.stratum': {
info: 'The stratum indicates how many hops away from a computer with an attached reference clock we are. Such a computer is a stratum-1 computer.',
decimalDigits: 0,
height: 0.5
},
'chrony.root': {
info: 'Estimated delays against the root time server this system is synchronized with. delay is the total of the network path delays to the stratum-1 computer from which the computer is ultimately synchronised. dispersion is the total dispersion accumulated through all the computers back to the stratum-1 computer from which the computer is ultimately synchronised. Dispersion is due to system clock resolution, statistical measurement variations etc.'
},
'chrony.frequency': {
info: 'The frequency is the rate by which the system\'s clock would be would be wrong if chronyd was not correcting it. It is expressed in ppm (parts per million). For example, a value of 1ppm would mean that when the system\'s clock thinks it has advanced 1 second, it has actually advanced by 1.000001 seconds relative to true time.',
colors: NETDATA.colors[0]
},
'chrony.residualfreq': {
info: 'This shows the residual frequency for the currently selected reference source. ' +
'It reflects any difference between what the measurements from the reference source indicate the ' +
'frequency should be and the frequency currently being used. The reason this is not always zero is ' +
'that a smoothing procedure is applied to the frequency. Each time a measurement from the reference ' +
'source is obtained and a new residual frequency computed, the estimated accuracy of this residual ' +
'is compared with the estimated accuracy (see skew) of the existing frequency value. ' +
'A weighted average is computed for the new frequency, with weights depending on these accuracies. ' +
'If the measurements from the reference source follow a consistent trend, the residual will be ' +
'driven to zero over time.',
height: 0.5,
colors: NETDATA.colors[3]
},
'chrony.skew': {
info: 'The estimated error bound on the frequency.',
height: 0.5,
colors: NETDATA.colors[5]
},
'couchdb.active_tasks': {
info: 'Active tasks running on this CouchDB cluster. Four types of tasks currently exist: indexer (view building), replication, database compaction and view compaction.'
},
'couchdb.replicator_jobs': {
info: 'Detailed breakdown of any replication jobs in progress on this node. For more information, see the replicator documentation.'
},
'couchdb.open_files': {
info: 'Count of all files held open by CouchDB. If this value seems pegged at 1024 or 4096, your server process is probably hitting the open file handle limit and needs to be increased.'
},
'btrfs.disk': {
info: '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.',
colors: [NETDATA.colors[12]]
},
'btrfs.data': {
info: '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.metadata': {
info: '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.system': {
info: '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.'
},
// ------------------------------------------------------------------------
// RabbitMQ
// info: the text above the charts
// heads: the representation of the chart at the top the subsection (second level menu)
// mainheads: the representation of the chart at the top of the section (first level menu)
// colors: the dimension colors of the chart (the default colors are appended)
// height: the ratio of the chart height relative to the default
'rabbitmq.queued_messages': {
info: 'Overall total of ready and unacknowledged queued messages. Messages that are delivered immediately are not counted here.'
},
'rabbitmq.message_rates': {
info: 'Overall messaging rates including acknowledgements, deliveries, redeliveries, and publishes.'
},
'rabbitmq.global_counts': {
info: 'Overall totals for channels, consumers, connections, queues and exchanges.'
},
'rabbitmq.file_descriptors': {
info: 'Total number of used filed descriptors. See Open File Limits for further details.',
colors: NETDATA.colors[3]
},
'rabbitmq.sockets': {
info: 'Total number of used socket descriptors. Each used socket also counts as a used file descriptor. See Open File Limits for further details.',
colors: NETDATA.colors[3]
},
'rabbitmq.processes': {
info: 'Total number of processes running within the Erlang VM. This is not the same as the number of processes running on the host.',
colors: NETDATA.colors[3]
},
'rabbitmq.erlang_run_queue': {
info: 'Number of Erlang processes the Erlang schedulers have queued to run.',
colors: NETDATA.colors[3]
},
'rabbitmq.memory': {
info: 'Total amount of memory used by the RabbitMQ. This is a complex statistic that can be further analyzed in the management UI. See Memory for further details.',
colors: NETDATA.colors[3]
},
'rabbitmq.disk_space': {
info: 'Total amount of disk space consumed by the message store(s). See Disk Space Limits for further details.',
colors: NETDATA.colors[3]
},
'rabbitmq.queue_messages': {
info: 'Total amount of messages and their states in this queue.',
colors: NETDATA.colors[3]
},
'rabbitmq.queue_messages_stats': {
info: 'Overall messaging rates including acknowledgements, deliveries, redeliveries, and publishes.',
colors: NETDATA.colors[3]
},
// ------------------------------------------------------------------------
// ntpd
'ntpd.sys_offset': {
info: 'For hosts without any time critical services an offset of < 100 ms should be acceptable even with high network latencies. For hosts with time critical services an offset of about 0.01 ms or less can be achieved by using peers with low delays and configuring optimal poll exponent values.',
colors: NETDATA.colors[4]
},
'ntpd.sys_jitter': {
info: 'The jitter statistics are exponentially-weighted RMS averages. The system jitter is defined in the NTPv4 specification; the clock jitter statistic is computed by the clock discipline module.'
},
'ntpd.sys_frequency': {
info: 'The frequency offset is shown in ppm (parts per million) relative to the frequency of the system. The frequency correction needed for the clock can vary significantly between boots and also due to external influences like temperature or radiation.',
colors: NETDATA.colors[2],
height: 0.6
},
'ntpd.sys_wander': {
info: 'The wander statistics are exponentially-weighted RMS averages.',
colors: NETDATA.colors[3],
height: 0.6
},
'ntpd.sys_rootdelay': {
info: 'The rootdelay is the round-trip delay to the primary reference clock, similar to the delay shown by the ping command. A lower delay should result in a lower clock offset.',
colors: NETDATA.colors[1]
},
'ntpd.sys_stratum': {
info: 'The distance in "hops" to the primary reference clock',
colors: NETDATA.colors[5],
height: 0.3
},
'ntpd.sys_tc': {
info: 'Time constants and poll intervals are expressed as exponents of 2. The default poll exponent of 6 corresponds to a poll interval of 64 s. For typical Internet paths, the optimum poll interval is about 64 s. For fast LANs with modern computers, a poll exponent of 4 (16 s) is appropriate. The poll process sends NTP packets at intervals determined by the clock discipline algorithm.',
height: 0.5
},
'ntpd.sys_precision': {
colors: NETDATA.colors[6],
height: 0.2
},
'ntpd.peer_offset': {
info: 'The offset of the peer clock relative to the system clock in milliseconds. Smaller values here weight peers more heavily for selection after the initial synchronization of the local clock. For a system providing time service to other systems, these should be as low as possible.'
},
'ntpd.peer_delay': {
info: 'The round-trip time (RTT) for communication with the peer, similar to the delay shown by the ping command. Not as critical as either the offset or jitter, but still factored into the selection algorithm (because as a general rule, lower delay means more accurate time). In most cases, it should be below 100ms.'
},
'ntpd.peer_dispersion': {
info: 'This is a measure of the estimated error between the peer and the local system. Lower values here are better.'
},
'ntpd.peer_jitter': {
info: 'This is essentially a remote estimate of the peer\'s system_jitter value. Lower values here weight highly in favor of peer selection, and this is a good indicator of overall quality of a given time server (good servers will have values not exceeding single digit milliseconds here, with high quality stratum one servers regularly having sub-millisecond jitter).'
},
'ntpd.peer_xleave': {
info: 'This variable is used in interleaved mode (used only in NTP symmetric and broadcast modes). See NTP Interleaved Modes.'
},
'ntpd.peer_rootdelay': {
info: 'For a stratum 1 server, this is the access latency for the reference clock. For lower stratum servers, it is the sum of the peer_delay and peer_rootdelay for the system they are syncing off of. Similarly to peer_delay, lower values here are technically better, but have limited influence in peer selection.'
},
'ntpd.peer_rootdisp': {
info: 'Is the same as peer_rootdelay, but measures accumulated peer_dispersion instead of accumulated peer_delay.'
},
'ntpd.peer_hmode': {
info: 'The peer_hmode and peer_pmode variables give info about what mode the packets being sent to and received from a given peer are. Mode 1 is symmetric active (both the local system and the remote peer have each other declared as peers in /etc/ntp.conf), Mode 2 is symmetric passive (only one side has the other declared as a peer), Mode 3 is client, Mode 4 is server, and Mode 5 is broadcast (also used for multicast and manycast operation).',
height: 0.2
},
'ntpd.peer_pmode': {
height: 0.2
},
'ntpd.peer_hpoll': {
info: 'The peer_hpoll and peer_ppoll variables are log2 representations of the polling interval in seconds.',
height: 0.5
},
'ntpd.peer_ppoll': {
height: 0.5
},
'ntpd.peer_precision': {
height: 0.2
},
'spigotmc.tps': {
info: 'The running 1, 5, and 15 minute average number of server ticks per second. An idealized server will show 20.0 for all values, but in practice this almost never happens. Typical servers should show approximately 19.98-20.0 here. Lower values indicate progressively more server-side lag (and thus that you need better hardware for your server or a lower user limit). For every 0.05 ticks below 20, redstone clocks will lag behind by approximately 0.25%. Values below approximately 19.50 may interfere with complex free-running redstone circuits and will noticeably slow down growth.'
},
'spigotmc.users': {
info: 'The number of currently connected users on the monitored Spigot server.'
},
'boinc.tasks': {
info: 'The total number of tasks and the number of active tasks. Active tasks are those which are either currently being processed, or are partially processed but suspended.'
},
'boinc.states': {
info: 'Counts of tasks in each task state. The normal sequence of states is New, Downloading, Ready to Run, Uploading, Uploaded. Tasks which are marked Ready to Run may be actively running, or may be waiting to be scheduled. Compute Errors are tasks which failed for some reason during execution. Aborted tasks were manually cancelled, and will not be processed. Failed Uploads are otherwise finished tasks which failed to upload to the server, and usually indicate networking issues.'
},
'boinc.sched': {
info: 'Counts of active tasks in each scheduling state. Scheduled tasks are the ones which will run if the system is permitted to process tasks. Preempted tasks are on standby, and will run if a Scheduled task stops running for some reason. Uninitialized tasks should never be present, and indicate tha the scheduler has not tried to schedule them yet.'
},
'boinc.process': {
info: 'Counts of active tasks in each process state. Executing tasks are running right now. Suspended tasks have an associated process, but are not currently running (either because the system isn\'t processing any tasks right now, or because they have been preempted by higher priority tasks). Quit tasks are exiting gracefully. Aborted tasks exceeded some resource limit, and are being shut down. Copy Pending tasks are waiting on a background file transfer to finish. Uninitialized tasks do not have an associated process yet.'
},
'w1sensor.temp': {
info: 'Temperature derived from 1-Wire temperature sensors.'
},
'logind.sessions': {
info: 'Shows the number of active sessions of each type tracked by logind.'
},
'logind.users': {
info: 'Shows the number of active users of each type tracked by logind.'
},
'logind.seats': {
info: 'Shows the number of active seats tracked by logind. Each seat corresponds to a combination of a display device and input device providing a physical presence for the system.'
},
// ------------------------------------------------------------------------
// ProxySQL
'proxysql.pool_status': {
info: 'The status of the backend servers. ' +
'1=ONLINE backend server is fully operational, ' +
'2=SHUNNED backend sever is temporarily taken out of use because of either too many connection errors in a time that was too short, or replication lag exceeded the allowed threshold, ' +
'3=OFFLINE_SOFT when a server is put into OFFLINE_SOFT mode, new incoming connections aren\'t accepted anymore, while the existing connections are kept until they became inactive. In other words, connections are kept in use until the current transaction is completed. This allows to gracefully detach a backend, ' +
'4=OFFLINE_HARD when a server is put into OFFLINE_HARD mode, the existing connections are dropped, while new incoming connections aren\'t accepted either. This is equivalent to deleting the server from a hostgroup, or temporarily taking it out of the hostgroup for maintenance work, ' +
'-1 Unknown status.'
},
'proxysql.pool_net': {
info: 'The amount of data sent to/received from the backend ' +
'(This does not include metadata (packets\' headers, OK/ERR packets, fields\' description, etc).'
},
'proxysql.pool_overall_net': {
info: 'The amount of data sent to/received from the all backends ' +
'(This does not include metadata (packets\' headers, OK/ERR packets, fields\' description, etc).'
},
'proxysql.questions': {
info: 'questions total number of queries sent from frontends, ' +
'slow_queries number of queries that ran for longer than the threshold in milliseconds defined in global variable mysql-long_query_time. '
},
'proxysql.connections': {
info: 'aborted number of frontend connections aborted due to invalid credential or max_connections reached, ' +
'connected number of frontend connections currently connected, ' +
'created number of frontend connections created, ' +
'non_idle number of frontend connections that are not currently idle. '
},
'proxysql.pool_latency': {
info: 'The currently ping time in microseconds, as reported from Monitor.'
},
'proxysql.queries': {
info: 'The number of queries routed towards this particular backend server.'
},
'proxysql.pool_used_connections': {
info: 'The number of connections are currently used by ProxySQL for sending queries to the backend server.'
},
'proxysql.pool_free_connections': {
info: 'The number of connections are currently free. They are kept open in order to minimize the time cost of sending a query to the backend server.'
},
'proxysql.pool_ok_connections': {
info: 'The number of connections were established successfully.'
},
'proxysql.pool_error_connections': {
info: 'The number of connections weren\'t established successfully.'
},
'proxysql.commands_count': {
info: 'The total number of commands of that type executed'
},
'proxysql.commands_duration': {
info: 'The total time spent executing commands of that type, in ms'
},
// ------------------------------------------------------------------------
// Power Supplies
'powersupply.capacity': {
info: 'The current battery charge.'
},
'powersupply.charge': {
info: 'The battery charge in Amp-hours.
'+ 'now - actual charge value. '+ 'full, empty - last remembered value of charge when battery became full/empty. '+ 'It also could mean "value of charge when battery considered full/empty at given conditions (temperature, age)". '+ 'I.e. these attributes represents real thresholds, not design values. ' + 'full_design, empty_design - design charge values, when battery considered full/empty.
' }, 'powersupply.energy': { info: 'The battery charge in Watt-hours.
'+ 'now - actual charge value. '+ 'full, empty - last remembered value of charge when battery became full/empty. '+ 'It also could mean "value of charge when battery considered full/empty at given conditions (temperature, age)". '+ 'I.e. these attributes represents real thresholds, not design values. ' + 'full_design, empty_design - design charge values, when battery considered full/empty.
' }, 'powersupply.voltage': { info: 'The power supply voltage.
'+ 'now - current voltage. '+ 'max, min - voltage values that hardware could only guess (measure and retain) the thresholds '+ 'of a given power supply. '+ 'max_design, min_design - design values for maximal and minimal power supply voltages. '+ 'Maximal/minimal means values of voltages when battery considered "full"/"empty" at normal conditions.
' }, // ------------------------------------------------------------------------ // VMware vSphere // Host specific 'vsphere.host_mem_usage_percentage': { info: 'Percentage of used machine memory:consumed / machine-memory-size.'
},
'vsphere.host_mem_usage': {
info:
'granted is amount of machine memory that is mapped for a host, ' +
'it equals sum of all granted metrics for all powered-on virtual machines, plus machine memory for vSphere services on the host. ' +
'consumed is amount of machine memory used on the host, it includes memory used by the Service Console, the VMkernel, vSphere services, plus the total consumed metrics for all running virtual machines. ' +
'consumed = total host memory - free host memory.' +
'active is sum of all active metrics for all powered-on virtual machines plus vSphere services (such as COS, vpxa) on the host.' +
'shared is sum of all shared metrics for all powered-on virtual machines, plus amount for vSphere services on the host. ' +
'sharedcommon is amount of machine memory that is shared by all powered-on virtual machines and vSphere services on the host. ' +
'shared - sharedcommon = machine memory (host memory) savings (KB). ' +
'For details see Measuring and Differentiating Types of Memory Usage and ' +
'Memory Counters articles.'
},
'vsphere.host_mem_swap_rate': {
info:
'This statistic refers to VMkernel swapping and not to guest OS swapping. ' +
'in is sum of swapinRate values for all powered-on virtual machines on the host.' +
'swapinRate is rate at which VMKernel reads data into machine memory from the swap file. ' +
'out is sum of swapoutRate values for all powered-on virtual machines on the host.' +
'swapoutRate is rate at which VMkernel writes to the virtual machine’s swap file from machine memory.'
},
// VM specific
'vsphere.vm_mem_usage_percentage': {
info: 'Percentage of used virtual machine “physical” memory: active / virtual machine configured size.'
},
'vsphere.vm_mem_usage': {
info:
'granted is amount of guest “physical” memory that is mapped to machine memory, it includes shared memory amount. ' +
'consumed is amount of guest “physical” memory consumed by the virtual machine for guest memory, ' +
'consumed = granted - memory saved due to memory sharing. ' +
'active is amount of memory that is actively used, as estimated by VMkernel based on recently touched memory pages. ' +
'shared is amount of guest “physical” memory shared with other virtual machines (through the VMkernel’s transparent page-sharing mechanism, a RAM de-duplication technique). ' +
'For details see Measuring and Differentiating Types of Memory Usage and ' +
'Memory Counters articles.'
},
'vsphere.vm_mem_swap_rate': {
info:
'This statistic refers to VMkernel swapping and not to guest OS swapping. ' +
'in is rate at which VMKernel reads data into machine memory from the swap file. ' +
'out is rate at which VMkernel writes to the virtual machine’s swap file from machine memory.'
},
'vsphere.vm_mem_swap': {
info:
'This statistic refers to VMkernel swapping and not to guest OS swapping. ' +
'swapped is amount of guest physical memory swapped out to the virtual machine\'s swap file by the VMkernel. ' +
'Swapped memory stays on disk until the virtual machine needs it.'
},
// Common
'vsphere.cpu_usage_total': {
info: 'Summary CPU usage statistics across all CPUs/cores.'
},
'vsphere.net_bandwidth_total': {
info: 'Summary receive/transmit statistics across all network interfaces.'
},
'vsphere.net_packets_total': {
info: 'Summary receive/transmit statistics across all network interfaces.'
},
'vsphere.net_errors_total': {
info: 'Summary receive/transmit statistics across all network interfaces.'
},
'vsphere.net_drops_total': {
info: 'Summary receive/transmit statistics across all network interfaces.'
},
'vsphere.disk_usage_total': {
info: 'Summary read/write statistics across all disks.'
},
'vsphere.disk_max_latency': {
info: 'latency is highest latency value across all disks.'
},
'vsphere.overall_status': {
info: '0 is unknown, 1 is OK, 2 is might have a problem, 3 is definitely has a problem.'
},
// ------------------------------------------------------------------------
// VCSA
'vcsa.system_health': {
info:
'-1: unknown; ' +
'0: all components are healthy; ' +
'1: one or more components might become overloaded soon; ' +
'2: one or more components in the appliance might be degraded; ' +
'3: one or more components might be in an unusable status and the appliance might become unresponsive soon; ' +
'4: no health data is available.'
},
'vcsa.components_health': {
info:
'-1: unknown; ' +
'0: healthy; ' +
'1: healthy, but may have some problems; ' +
'2: degraded, and may have serious problems; ' +
'3: unavailable, or will stop functioning soon; ' +
'4: no health data is available.'
},
'vcsa.software_updates_health': {
info:
'softwarepackages represents information on available software updates available in the remote vSphere Update Manager repository.-1: unknown; ' +
'0: no updates available; ' +
'2: non-security updates are available; ' +
'3: security updates are available; ' +
'4: an error retrieving information on software updates.'
},
// ------------------------------------------------------------------------
// Zookeeper
'zookeeper.server_state': {
info:
'0: unknown, ' +
'1: leader, ' +
'2: follower, ' +
'3: observer, ' +
'4: standalone.'
},
// ------------------------------------------------------------------------
// Squidlog
'squidlog.requests': {
info: 'Total number of requests (log lines read). It includes unmatched.'
},
'squidlog.excluded_requests': {
info: 'unmatched counts the lines in the log file that are not matched by the plugin parser (let us know if you have any unmatched).'
},
'squidlog.type_requests': {
info: 'Requests by response type:success includes 1xx, 2xx, 0, 304, 401.error includes 5xx and 6xx.redirect includes 3xx except 304.bad includes 4xx except 401.1xx is informational responses.2xx is successful responses.3xx is redirects.4xx is bad requests.5xx is internal server errors.0 for a result code being unavailable, and 6xx to signal an invalid header, a proxy error.'
},
'squidlog.http_status_code_responses': {
info: 'Number of responses for each http response status code individually.'
},
'squidlog.uniq_clients': {
info: 'Unique clients (requesting instances), within each data collection iteration. If data collection is per second, this chart shows unique clients per second.'
},
'squidlog.bandwidth': {
info: 'The size is the amount of data delivered to the clients. Mind that this does not constitute the net object size, as headers are also counted. ' +
'Also, failed requests may deliver an error page, the size of which is also logged here.'
},
'squidlog.response_time': {
info: 'The elapsed time considers how many milliseconds the transaction busied the cache. It differs in interpretation between TCP and UDP:' +
'TCP this is basically the time from having received the request to when Squid finishes sending the last byte of the response.UDP this is the time between scheduling a reply and actually sending it.TCP requests on the HTTP port (usually 3128).UDP requests on the ICP port (usually 3130) or HTCP port (usually 4128).NONE Squid delivered an unusual response or no response at all. Seen with cachemgr requests and errors, usually when the transaction fails before being classified into one of the above outcomes. Also seen with responses to CONNECT requests.CF at least one request in this transaction was collapsed. See collapsed_forwarding for more details about request collapsing.CLIENT usually seen with client issued a "no-cache", or analogous cache control command along with the request. Thus, the cache has to validate the object.IMS the client sent a revalidation (conditional) request.ASYNC the request was generated internally by Squid. Usually this is background fetches for cache information exchanges, background revalidation from stale-while-revalidate cache controls, or ESI sub-objects being loaded.SWAPFAIL the object was believed to be in the cache, but could not be accessed. A new copy was requested from the server.REFRESH a revalidation (conditional) request was sent to the server.SHARED this request was combined with an existing transaction by collapsed forwarding.REPLY the HTTP reply from server or peer. Usually seen on DENIED due to http_reply_access ACLs preventing delivery of servers response object to the client.NEGATIVE only seen on HIT responses, indicating the response was a cached error response. e.g. 404 not found.STALE the object was cached and served stale. This is usually caused by stale-while-revalidate or stale-if-error cache controls.OFFLINE the requested object was retrieved from the cache during offline_mode. The offline mode never validates any object.INVALID an invalid request was received. An error response was delivered indicating what the problem was.FAILED only seen on REFRESH to indicate the revalidation request failed. The response object may be the server provided network error or the stale object which was being revalidated depending on stale-if-error cache control.MODIFIED only seen on REFRESH responses to indicate revalidation produced a new modified object.UNMODIFIED only seen on REFRESH responses to indicate revalidation produced a 304 (Not Modified) status. The client gets either a full 200 (OK), a 304 (Not Modified), or (in theory) another response, depending on the client request and other details.REDIRECT Squid generated an HTTP redirect response to this request.HIT the response object delivered was the local cache object.MEM the response object came from memory cache, avoiding disk accesses. Only seen on HIT responses.MISS the response object delivered was the network response object.DENIED the request was denied by access controls.NOFETCH an ICP specific type, indicating service is alive, but not to be used for this request.TUNNEL a binary tunnel was established for this transaction.ABORTED the response was not completed due to the connection being aborted (usually by the client).TIMEOUT the response was not completed due to a connection timeout.IGNORED while refreshing a previously cached response A, Squid got a response B that was older than A (as determined by the Date header field). Squid ignored response B (and attempted to use A instead).TIMEOUT_, if the timeout occurs waiting for all ICP replies to return from the neighbours. The timeout is either dynamic, if the icp_query_timeout was not set, or the time configured there has run up. ' +
'Refer to Hierarchy Codes for details on hierarchy codes.'
},
'squidlog.server_address_forwarded_requests': {
info: 'The IP address or hostname where the request (if a miss) was forwarded. For requests sent to origin servers, this is the origin server\'s IP address. ' +
'For requests sent to a neighbor cache, this is the neighbor\'s hostname. NOTE: older versions of Squid would put the origin server hostname here.'
},
'squidlog.mime_type_requests': {
info: 'The content type of the object as seen in the HTTP reply header. Please note that ICP exchanges usually don\'t have any content type.'
},
// ------------------------------------------------------------------------
// CockroachDB
'cockroachdb.process_cpu_time_combined_percentage': {
info: 'Current combined cpu utilization, calculated as (user+system)/num of logical cpus.'
},
'cockroachdb.host_disk_bandwidth': {
info: 'Summary disk bandwidth statistics across all system host disks.'
},
'cockroachdb.host_disk_operations': {
info: 'Summary disk operations statistics across all system host disks.'
},
'cockroachdb.host_disk_iops_in_progress': {
info: 'Summary disk iops in progress statistics across all system host disks.'
},
'cockroachdb.host_network_bandwidth': {
info: 'Summary network bandwidth statistics across all system host network interfaces.'
},
'cockroachdb.host_network_packets': {
info: 'Summary network packets statistics across all system host network interfaces.'
},
'cockroachdb.live_nodes': {
info: 'Will be 0 if this node is not itself live.'
},
'cockroachdb.total_storage_capacity': {
info: 'Entire disk capacity. It includes non-CR data, CR data, and empty space.'
},
'cockroachdb.storage_capacity_usability': {
info: 'usable is sum of empty space and CR data, unusable is space used by non-CR data.'
},
'cockroachdb.storage_usable_capacity': {
info: 'Breakdown of usable space.'
},
'cockroachdb.storage_used_capacity_percentage': {
info: 'total is % of total space used, usable is % of usable space used.'
},
'cockroachdb.sql_bandwidth': {
info: 'The total amount of SQL client network traffic.'
},
'cockroachdb.sql_errors': {
info: 'statement is statements resulting in a planning or runtime error, ' +
'transaction is SQL transactions abort errors.'
},
'cockroachdb.sql_started_ddl_statements': {
info: 'The amount of started DDL (Data Definition Language) statements. ' +
'This type means database schema changes. ' +
'It includes CREATE, ALTER, DROP, RENAME, TRUNCATE and COMMENT statements.'
},
'cockroachdb.sql_executed_ddl_statements': {
info: 'The amount of executed DDL (Data Definition Language) statements. ' +
'This type means database schema changes. ' +
'It includes CREATE, ALTER, DROP, RENAME, TRUNCATE and COMMENT statements.'
},
'cockroachdb.sql_started_dml_statements': {
info: 'The amount of started DML (Data Manipulation Language) statements.'
},
'cockroachdb.sql_executed_dml_statements': {
info: 'The amount of executed DML (Data Manipulation Language) statements.'
},
'cockroachdb.sql_started_tcl_statements': {
info: 'The amount of started TCL (Transaction Control Language) statements.'
},
'cockroachdb.sql_executed_tcl_statements': {
info: 'The amount of executed TCL (Transaction Control Language) statements.'
},
'cockroachdb.live_bytes': {
info: 'The amount of live data used by both applications and the CockroachDB system.'
},
'cockroachdb.kv_transactions': {
info: 'KV transactions breakdown:committed committed KV transactions (including 1PC).fast-path_committed KV transaction on-phase commit attempts.aborted aborted KV transactions.write too old restarts due to a concurrent writer committing first.write too old (multiple) restarts due to multiple concurrent writers committing first.forwarded timestamp (iso=serializable) restarts due to a forwarded commit timestamp and isolation=SERIALIZABLE".possible replay restarts due to possible replays of command batches at the storage layer.async consensus failure restarts due to async consensus writes that failed to leave intents.read within uncertainty interval restarts due to reading a new value within the uncertainty interval.aborted restarts due to an abort by a concurrent transaction (usually due to deadlock).push failure restarts due to a transaction push failure.unknown restarts due to a unknown reasons.unavailable ranges with fewer live replicas than needed for quorum.under replicated ranges with fewer live replicas than the replication target.over replicated ranges with more live replicas than the replication target.leader for write requests, not leaseholders is the number of Raft leaders whose range lease is held by another store.'
},
'cockroachdb.replicas_leaseholders': {
info: 'For each range, one of the replicas holds the "range lease". This replica, referred to as the leaseholder, is the one that receives and coordinates all read and write requests for the range.'
},
'cockroachdb.queue_processing_failures': {
info: 'Failed replicas breakdown by queue:gc replicas which failed processing in the GC queue.replica gc replicas which failed processing in the replica GC queue.replication replicas which failed processing in the replicate queue.split replicas which failed processing in the split queue.consistency replicas which failed processing in the consistency checker queue.raft log replicas which failed processing in the Raft log queue.raft snapshot replicas which failed processing in the Raft repair queue.time series maintenance replicas which failed processing in the time series maintenance queue.vfs_unlink. '
},
'filesystem.vfs_io': {
title : 'VFS IO',
info: 'Successful or failed calls to functions vfs_read and vfs_write. This chart may not show all file system events if it uses other functions to store data on disk.'
},
'filesystem.vfs_io_bytes': {
title : 'VFS bytes written',
info: 'Total of bytes read or written with success using the functions vfs_read and vfs_write.'
},
'filesystem.vfs_io_error': {
title : 'VFS IO error',
info: 'Failed calls to functions vfs_read and vfs_write.'
},
'filesystem.vfs_fsync': {
info: 'Successful or failed calls to functions vfs_fsync.'
},
'filesystem.vfs_fsync_error': {
info: 'Failed calls to functions vfs_fsync.'
},
'filesystem.vfs_open': {
info: 'Successful or failed calls to functions vfs_open.'
},
'filesystem.vfs_open_error': {
info: 'Failed calls to functions vfs_open.'
},
'filesystem.vfs_create': {
info: 'Successful or failed calls to functions vfs_create.'
},
'filesystem.vfs_create_error': {
info: 'Failed calls to functions vfs_create.'
},
'filesystem.ext4_read_latency': {
info: 'Netdata is attaching kprobes for the function ext4_file_read_iter.'
},
'filesystem.ext4_write_latency': {
info: 'Netdata is attaching kprobes for the function ext4_file_write_iter.'
},
'filesystem.ext4_open_latency': {
info: 'Netdata is attaching kprobes for the function ext4_file_open.'
},
'filesystem.ext4_sync_latency': {
info: 'Netdata is attaching kprobes for the function ext4_sync_file.'
},
'filesystem.xfs_read_latency': {
info: 'Netdata is attaching kprobes for the function xfs_file_read_iter.'
},
'filesystem.xfs_write_latency': {
info: 'Netdata is attaching kprobes for the function xfs_file_write_iter.'
},
'filesystem.xfs_open_latency': {
info: 'Netdata is attaching kprobes for the function xfs_file_open.'
},
'filesystem.xfs_sync_latency': {
info: 'Netdata is attaching kprobes for the function xfs_file_sync.'
},
'filesystem.nfs_read_latency': {
info: 'Netdata is attaching kprobes for the function nfs_file_read.'
},
'filesystem.nfs_write_latency': {
info: 'Netdata is attaching kprobes for the function nfs_file_write.'
},
'filesystem.nfs_open_latency': {
info: 'Netdata is attaching kprobes for functions nfs_file_open and nfs4_file_open'
},
'filesystem.nfs_attribute_latency': {
info: 'Netdata is attaching kprobes for the function nfs_getattr.'
},
'filesystem.zfs_read_latency': {
info: 'Netdata is attaching kprobes for when the function zpl_iter_read.'
},
'filesystem.zfs_write_latency': {
info: 'Netdata is attaching kprobes for when the function zpl_iter_write.'
},
'filesystem.zfs_open_latency': {
info: 'Netdata is attaching kprobes for when the function zpl_open.'
},
'filesystem.zfs_sync_latency': {
info: 'Netdata is attaching kprobes for when the function zpl_fsync.'
},
'filesystem.btrfs_read_latency': {
info: 'Netdata is attaching kprobes for when the function btrfs_file_read_iter (kernel newer than 5.9.16) or the function generic_file_read_iter (old kernels).'
},
'filesystem.btrfs_write_latency': {
info: 'Netdata is attaching kprobes for when the function btrfs_file_write_iter.'
},
'filesystem.btrfs_open_latency': {
info: 'Netdata is attaching kprobes for when the function btrfs_file_open.'
},
'filesystem.btrfs_sync_latency': {
info: 'Netdata is attaching kprobes for when the function btrfs_sync_file.'
},
'mount_points.call': {
info: 'Monitor calls to syscalls mount(2) and umount(2) that are responsible for attaching or removing filesystems.'
},
'mount_points.error': {
info: 'Monitor errors in calls to syscalls mount(2) and umount(2).'
},
'filesystem.file_descriptor': {
info: 'Calls for internal functions on Linux kernel. The open dimension is attached to the kernel internal function do_sys_open ( For kernels newer than 5.5.19 we add a kprobe to do_sys_openat2. ), which is the common function called from'+
' open(2) ' +
' and openat(2). ' +
' The close dimension is attached to the function __close_fd or close_fd according to your kernel version, which is called from system call' +
' close(2). '
},
'filesystem.file_error': {
info: 'Failed calls to the kernel internal function do_sys_open ( For kernels newer than 5.5.19 we add a kprobe to do_sys_openat2. ), which is the common function called from'+
' open(2) ' +
' and openat(2). ' +
' The close dimension is attached to the function __close_fd or close_fd according to your kernel version, which is called from system call' +
' close(2). '
},
// ------------------------------------------------------------------------
// eBPF
'apps.swap_read_call': {
info: 'The function swap_readpage is called when the kernel reads a page from swap memory. Netdata also gives a summary for these charts in System overview.'
},
'apps.swap_write_call': {
info: 'The function swap_writepage is called when the kernel writes a page to swap memory.'
},
'apps.shmget_call': {
info: 'Number of times the syscall shmget is called. Netdata also gives a summary for these charts in System overview.'
},
'apps.shmat_call': {
info: 'Number of times the syscall shmat is called.'
},
'apps.shmdt_call': {
info: 'Number of times the syscall shmdt is called.'
},
'apps.shmctl_call': {
info: 'Number of times the syscall shmctl is called.'
},
// ------------------------------------------------------------------------
// ACLK Internal Stats
'netdata.aclk_status': {
valueRange: "[0, 1]",
info: 'This chart shows if ACLK was online during entirety of the sample duration.'
},
'netdata.aclk_query_per_second': {
info: 'This chart shows how many queries were added for ACLK_query thread to process and how many it was actually able to process.'
},
'netdata.aclk_latency_mqtt': {
info: 'Measures latency between MQTT publish of the message and it\'s PUB_ACK being received'
},
// ------------------------------------------------------------------------
// VerneMQ
'vernemq.sockets': {
mainheads: [
function (os, id) {
void (os);
return '';
}
]
},
'vernemq.queue_processes': {
mainheads: [
function (os, id) {
void (os);
return '';
}
]
},
'vernemq.queue_messages': {
mainheads: [
function (os, id) {
void (os);
return '';
},
function (os, id) {
void (os);
return '';
},
]
},
'vernemq.average_scheduler_utilization': {
mainheads: [
function (os, id) {
void (os);
return '';
}
]
},
// ------------------------------------------------------------------------
// Apache Pulsar
'pulsar.messages_rate': {
mainheads: [
function (os, id) {
void (os);
return '';
},
function (os, id) {
void (os);
return '';
},
]
},
'pulsar.subscription_msg_rate_redeliver': {
mainheads: [
function (os, id) {
void (os);
return '';
}
]
},
'pulsar.subscription_blocked_on_unacked_messages': {
mainheads: [
function (os, id) {
void (os);
return '';
}
]
},
'pulsar.msg_backlog': {
mainheads: [
function (os, id) {
void (os);
return '';
}
]
},
'pulsar.namespace_messages_rate': {
heads: [
function (os, id) {
void (os);
return '';
},
function (os, id) {
void (os);
return '';
},
]
},
'pulsar.namespace_subscription_msg_rate_redeliver': {
heads: [
function (os, id) {
void (os);
return '';
}
]
},
'pulsar.namespace_subscription_blocked_on_unacked_messages': {
heads: [
function (os, id) {
void (os);
return '';
}
]
},
'pulsar.namespace_msg_backlog': {
heads: [
function (os, id) {
void (os);
return '';
},
],
},
// ------------------------------------------------------------------------
// Nvidia-smi
'nvidia_smi.fan_speed': {
heads: [
function (os, id) {
void (os);
return '';
}
]
},
'nvidia_smi.temperature': {
heads: [
function (os, id) {
void (os);
return '';
}
]
},
'nvidia_smi.memory_allocated': {
heads: [
function (os, id) {
void (os);
return '';
}
]
},
'nvidia_smi.power': {
heads: [
function (os, id) {
void (os);
return '';
}
]
},
// ------------------------------------------------------------------------
// Supervisor
'supervisord.process_state_code': {
info: 'Process states map: ' +
'0 - stopped, 10 - starting, 20 - running, 30 - backoff,' +
'40 - stopping, 100 - exited, 200 - fatal, 1000 - unknown.'
},
// ------------------------------------------------------------------------
// Systemd units
'systemd.service_units_state': {
info: 'Service units start and control daemons and the processes they consist of. ' +
'For details, see systemd.service(5)'
},
'systemd.socket_unit_state': {
info: 'Socket units encapsulate local IPC or network sockets in the system, useful for socket-based activation. ' +
'For details about socket units, see systemd.socket(5), ' +
'for details on socket-based activation and other forms of activation, see daemon(7).'
},
'systemd.target_unit_state': {
info: 'Target units are useful to group units, or provide well-known synchronization points during boot-up, ' +
'see systemd.target(5).'
},
'systemd.path_unit_state': {
info: 'Path units may be used to activate other services when file system objects change or are modified. ' +
'See systemd.path(5).'
},
'systemd.device_unit_state': {
info: 'Device units expose kernel devices in systemd and may be used to implement device-based activation. ' +
'For details, see systemd.device(5).'
},
'systemd.mount_unit_state': {
info: 'Mount units control mount points in the file system. ' +
'For details, see systemd.mount(5).'
},
'systemd.automount_unit_state': {
info: 'Automount units provide automount capabilities, for on-demand mounting of file systems as well as parallelized boot-up. ' +
'See systemd.automount(5).'
},
'systemd.swap_unit_state': {
info: 'Swap units are very similar to mount units and encapsulate memory swap partitions or files of the operating system. ' +
'They are described in systemd.swap(5).'
},
'systemd.timer_unit_state': {
info: 'Timer units are useful for triggering activation of other units based on timers. ' +
'You may find details in systemd.timer(5).'
},
'systemd.scope_unit_state': {
info: 'Slice units may be used to group units which manage system processes (such as service and scope units) ' +
'in a hierarchical tree for resource management purposes. ' +
'See systemd.scope(5).'
},
'systemd.slice_unit_state': {
info: 'Scope units are similar to service units, but manage foreign processes instead of starting them as well. ' +
'See systemd.slice(5).'
},
'anomaly_detection.dimensions': {
info: 'Total count of dimensions considered anomalous or normal. '
},
'anomaly_detection.anomaly_rate': {
info: 'Percentage of anomalous dimensions. '
},
'anomaly_detection.detector_window': {
info: 'The length of the active window used by the detector. '
},
'anomaly_detection.detector_events': {
info: 'Flags (0 or 1) to show when an anomaly event has been triggered by the detector. '
},
'anomaly_detection.prediction_stats': {
info: 'Diagnostic metrics relating to prediction time of anomaly detection. '
},
'anomaly_detection.training_stats': {
info: 'Diagnostic metrics relating to training time of anomaly detection. '
},
// ------------------------------------------------------------------------
// Supervisor
'fail2ban.failed_attempts': {
info: 'The number of failed attempts.
'+ 'This chart reflects the number of \'Found\' lines. '+ 'Found means a line in the service’s log file matches the failregex in its filter.
' }, 'fail2ban.bans': { info: 'The number of bans.
'+ 'This chart reflects the number of \'Ban\' and \'Restore Ban\' lines. '+ 'Ban action happens when the number of failed attempts (maxretry) occurred in the last configured interval (findtime).
' }, 'fail2ban.banned_ips': { info: 'The number of banned IP addresses.
' }, };