diff options
Diffstat (limited to '')
| -rw-r--r-- | web/gui/dashboard_info.js (renamed from web/dashboard_info.js) | 639 |
1 files changed, 445 insertions, 194 deletions
diff --git a/web/dashboard_info.js b/web/gui/dashboard_info.js index 55d454e03..139ac9340 100644 --- a/web/dashboard_info.js +++ b/web/gui/dashboard_info.js @@ -1,3 +1,4 @@ +// SPDX-License-Identifier: GPL-3.0-or-later var netdataDashboard = window.netdataDashboard || {}; @@ -16,7 +17,8 @@ netdataDashboard.menu = { 'services': { title: 'systemd Services', icon: '<i class="fas fa-cogs"></i>', - info: 'Resources utilization of systemd services. netdata monitors all systemd services via cgroups (the resources accounting used by containers). ' + info: 'Resources utilization of systemd services. netdata monitors all systemd services via CGROUPS ' + + '(the resources accounting used by containers). ' }, 'ap': { @@ -28,7 +30,15 @@ netdataDashboard.menu = { 'tc': { title: 'Quality of Service', icon: '<i class="fas fa-globe"></i>', - info: 'Netdata collects and visualizes <code>tc</code> class utilization using its <a href="https://github.com/firehol/netdata/blob/master/plugins.d/tc-qos-helper.sh" target="_blank">tc-helper plugin</a>. If you also use <a href="http://firehol.org/#fireqos" target="_blank">FireQOS</a> 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).' + info: 'Netdata collects and visualizes <code>tc</code> class utilization using its ' + + '<a href="https://github.com/netdata/netdata/blob/master/plugins.d/tc-qos-helper.sh" target="_blank">tc-helper plugin</a>. ' + + 'If you also use <a href="http://firehol.org/#fireqos" target="_blank">FireQOS</a> 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': { @@ -37,10 +47,27 @@ netdataDashboard.menu = { info: 'Performance metrics for network interfaces.' }, + 'ip': { + title: 'Networking Stack', + icon: '<i class="fas fa-cloud"></i>', + info: function (os) { + if(os === "linux") + return 'Metrics for the networking stack of the system. These metrics are collected from <code>/proc/net/netstat</code>, 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: '<i class="fas fa-cloud"></i>', - info: 'Metrics for the IPv4 stack of the system. <a href="https://en.wikipedia.org/wiki/IPv4" target="_blank">Internet Protocol version 4 (IPv4)</a> 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).' + info: 'Metrics for the IPv4 stack of the system. ' + + '<a href="https://en.wikipedia.org/wiki/IPv4" target="_blank">Internet Protocol version 4 (IPv4)</a> 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': { @@ -49,6 +76,12 @@ netdataDashboard.menu = { info: 'Metrics for the IPv6 stack of the system. <a href="https://en.wikipedia.org/wiki/IPv6" target="_blank">Internet Protocol version 6 (IPv6)</a> 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: '<i class="fas fa-cloud"></i>', + info: '<a href="https://en.wikipedia.org/wiki/Stream_Control_Transmission_Protocol" target="_blank">Stream Control Transmission Protocol (SCTP)</a> 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.' + }, + 'ipvs': { title: 'IP Virtual Server', icon: '<i class="fas fa-eye"></i>', @@ -130,7 +163,7 @@ netdataDashboard.menu = { 'apps': { title: 'Applications', icon: '<i class="fas fa-heartbeat"></i>', - info: 'Per application statistics are collected using netdata\'s <code>apps.plugin</code>. This plugin walks through all processes and aggregates statistics for applications of interest, defined in <code>/etc/netdata/apps_groups.conf</code> (the default is <a href="https://github.com/firehol/netdata/blob/master/conf.d/apps_groups.conf" target="_blank">here</a>). The plugin internally builds a process tree (much like <code>ps fax</code> does), and groups processes together (evaluating both child and parent processes) so that the result is always a chart with a predefined set of dimensions (of course, only application groups found running are reported). The reported values are compatible with <code>top</code>, although the netdata plugin counts also the resources of exited children (unlike <code>top</code> which shows only the resources of the currently running processes). So for processes like shell scripts, the reported values include the resources used by the commands these scripts run within each timeframe.', + info: 'Per application statistics are collected using netdata\'s <code>apps.plugin</code>. This plugin walks through all processes and aggregates statistics for applications of interest, defined in <code>/etc/netdata/apps_groups.conf</code> (the default is <a href="https://github.com/netdata/netdata/blob/master/conf.d/apps_groups.conf" target="_blank">here</a>). The plugin internally builds a process tree (much like <code>ps fax</code> does), and groups processes together (evaluating both child and parent processes) so that the result is always a chart with a predefined set of dimensions (of course, only application groups found running are reported). The reported values are compatible with <code>top</code>, although the netdata plugin counts also the resources of exited children (unlike <code>top</code> which shows only the resources of the currently running processes). So for processes like shell scripts, the reported values include the resources used by the commands these scripts run within each timeframe.', height: 1.5 }, @@ -189,6 +222,12 @@ netdataDashboard.menu = { info: 'Performance metrics for <b>memcached</b>. 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: '<i class="fas fa-database"></i>', + info: 'Statuses of checks in <b>monit</b>. 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: '<i class="fas fa-database"></i>', @@ -207,6 +246,12 @@ netdataDashboard.menu = { info: 'Performance metrics for <b>redis</b>. 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: '<i class="fas fa-database"></i>', + info: 'Performance metrics for <b>rethinkdb</b>. RethinkDB is the first open-source scalable database built for realtime applications' + }, + 'retroshare': { title: 'RetroShare', icon: '<i class="fas fa-share-alt"></i>', @@ -270,7 +315,7 @@ netdataDashboard.menu = { 'web_log': { title: undefined, icon: '<i class="fas fa-file-alt"></i>', - info: 'Information extracted from a server log file. <code>web_log</code> 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 <code>nginx</code> and <code>apache</code>) offering timing information and bandwidth for both requests and responses. <code>web_log</code> plugin may also be configured to provide a break down of requests per URL pattern (check <a href="https://github.com/firehol/netdata/blob/master/conf.d/python.d/web_log.conf" target="_blank"><code>/etc/netdata/python.d/web_log.conf</code></a>).' + info: 'Information extracted from a server log file. <code>web_log</code> 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 <code>nginx</code> and <code>apache</code>) offering timing information and bandwidth for both requests and responses. <code>web_log</code> plugin may also be configured to provide a break down of requests per URL pattern (check <a href="https://github.com/netdata/netdata/blob/master/conf.d/python.d/web_log.conf" target="_blank"><code>/etc/netdata/python.d/web_log.conf</code></a>).' }, 'named': { @@ -359,11 +404,46 @@ netdataDashboard.menu = { title: 'ntpd', icon: '<i class="fas fa-clock"></i>', info: 'Provides statistics for the internal variables of the Network Time Protocol daemon <b><a href="http://www.ntp.org/">ntpd</a></b> and optional including the configured peers (if enabled in the module configuration). The module presents the performance metrics as shown by <b><a href="http://doc.ntp.org/current-stable/ntpq.html">ntpq</a></b> (the standard NTP query program) using NTP mode 6 UDP packets to communicate with the NTP server.' + }, + + 'spigotmc': { + title: 'Spigot MC', + icon: '<i class="fas fa-eye"></i>', + info: 'Provides basic performance statistics for the <b><a href="https://www.spigotmc.org/">Spigot Minecraft</a></b> server.' + }, + + 'unbound': { + title: 'Unbound', + icon: '<i class="fas fa-tag"></i>', + info: undefined + }, + + 'boinc': { + title: 'BOINC', + icon: '<i class="fas fa-microchip"></i>', + info: 'Provides task counts for <b><a href="http://boinc.berkeley.edu/">BOINC</a></b> distributed computing clients.' + }, + + 'w1sensor': { + title: '1-Wire Sensors', + icon: '<i class="fas fa-thermometer-half"></i>', + info: 'Data derived from <a href="https://en.wikipedia.org/wiki/1-Wire">1-Wire</a> sensors. Currently temperature sensors are automatically detected.' + }, + + 'logind': { + title: 'Logind', + icon: '<i class="fas fa-user"></i>', + info: undefined + }, + + 'linux_power_supply': { + title: 'Power Supply', + icon: '<i class="fas fa-battery-half"></i>', + info: 'Statistics for the various system power supplies.' } }; - // ---------------------------------------------------------------------------- // submenus @@ -414,7 +494,7 @@ netdataDashboard.submenu = { }, 'web_log.urls': { - info: 'Number of requests for each <code>URL pattern</code> defined in <a href="https://github.com/firehol/netdata/blob/master/conf.d/python.d/web_log.conf" target="_blank"><code>/etc/netdata/python.d/web_log.conf</code></a>. This chart counts all requests matching the URL patterns defined, independently of the web server response codes (i.e. both successful and unsuccessful).' + info: 'Number of requests for each <code>URL pattern</code> defined in <a href="https://github.com/netdata/netdata/blob/master/conf.d/python.d/web_log.conf" target="_blank"><code>/etc/netdata/python.d/web_log.conf</code></a>. 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': { @@ -438,7 +518,7 @@ netdataDashboard.submenu = { info: 'Non-Uniform Memory Access (NUMA) is a hierarchical memory design the memory access time is dependent on locality. Under NUMA, a processor can access its own local memory faster than non-local memory (memory local to another processor or memory shared between processors). The individual metrics are described in the <a href="https://www.kernel.org/doc/Documentation/numastat.txt" target="_blank">Linux kernel documentation</a>.' }, - 'ipv4.ecn': { + 'ip.ecn': { info: '<a href="https://en.wikipedia.org/wiki/Explicit_Congestion_Notification" target="_blank">Explicit Congestion Notification (ECN)</a> is a TCP extension 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.' }, @@ -464,9 +544,9 @@ netdataDashboard.submenu = { '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 <a href="#menu_cpu_submenu_softnet_stat">CPU / softnet statistics</a>. <b>processed</b> states the number of packets processed, <b>dropped</b> is the number packets dropped because the network device backlog was full (to fix them on Linux use <code>sysctl</code> to increase <code>net.core.netdev_max_backlog</code>), <b>squeezed</b> is the number of packets dropped because the network device budget ran out (to fix them on Linux use <code>sysctl</code> to increase <code>net.core.netdev_budget</code>). More information about identifying and troubleshooting network driver related issues can be found at <a href="https://access.redhat.com/sites/default/files/attachments/20150325_network_performance_tuning.pdf" target="_blank">Red Hat Enterprise Linux Network Performance Tuning Guide</a>.'; + 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 <a href="#menu_cpu_submenu_softnet_stat">CPU / softnet statistics</a>. <b>processed</b> states the number of packets processed, <b>dropped</b> is the number packets dropped because the network device backlog was full (to fix them on Linux use <code>sysctl</code> to increase <code>net.core.netdev_max_backlog</code>), <b>squeezed</b> is the number of packets dropped because the network device budget ran out (to fix them on Linux use <code>sysctl</code> to increase <code>net.core.netdev_budget</code> and/or <code>net.core.netdev_budget_usecs</code>). More information about identifying and troubleshooting network driver related issues can be found at <a href="https://access.redhat.com/sites/default/files/attachments/20150325_network_performance_tuning.pdf" target="_blank">Red Hat Enterprise Linux Network Performance Tuning Guide</a>.'; else return 'Statistics for CPUs SoftIRQs related to network receive work.'; } @@ -474,9 +554,9 @@ netdataDashboard.submenu = { 'cpu.softnet_stat': { title: 'softnet', - info: function(os) { - if(os === 'linux') - return 'Statistics for per CPUs core SoftIRQs related to network receive work. Total for all CPU cores can be found at <a href="#menu_system_submenu_softnet_stat">System / softnet statistics</a>. <b>processed</b> states the number of packets processed, <b>dropped</b> is the number packets dropped because the network device backlog was full (to fix them on Linux use <code>sysctl</code> to increase <code>net.core.netdev_max_backlog</code>), <b>squeezed</b> is the number of packets dropped because the network device budget ran out (to fix them on Linux use <code>sysctl</code> to increase <code>net.core.netdev_budget</code>). More information about identifying and troubleshooting network driver related issues can be found at <a href="https://access.redhat.com/sites/default/files/attachments/20150325_network_performance_tuning.pdf" target="_blank">Red Hat Enterprise Linux Network Performance Tuning Guide</a>.'; + info: function (os) { + if (os === 'linux') + return 'Statistics for per CPUs core SoftIRQs related to network receive work. Total for all CPU cores can be found at <a href="#menu_system_submenu_softnet_stat">System / softnet statistics</a>. <b>processed</b> states the number of packets processed, <b>dropped</b> is the number packets dropped because the network device backlog was full (to fix them on Linux use <code>sysctl</code> to increase <code>net.core.netdev_max_backlog</code>), <b>squeezed</b> is the number of packets dropped because the network device budget ran out (to fix them on Linux use <code>sysctl</code> to increase <code>net.core.netdev_budget</code> and/or <code>net.core.netdev_budget_usecs</code>). More information about identifying and troubleshooting network driver related issues can be found at <a href="https://access.redhat.com/sites/default/files/attachments/20150325_network_performance_tuning.pdf" target="_blank">Red Hat Enterprise Linux Network Performance Tuning Guide</a>.'; else return 'Statistics for per CPUs core SoftIRQs related to network receive work. Total for all CPU cores can be found at <a href="#menu_system_submenu_softnet_stat">System / softnet statistics</a>.'; } @@ -523,7 +603,6 @@ netdataDashboard.submenu = { }; - // ---------------------------------------------------------------------------- // chart @@ -538,7 +617,7 @@ netdataDashboard.submenu = { // netdataDashboard.context = { 'system.cpu': { - info: function(os) { + 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 <a href="#menu_cpu">CPUs</a> section and per application usage at the <a href="#menu_apps">Applications Monitoring</a> section.' + netdataDashboard.sparkline('<br/>Keep an eye on <b>iowait</b> ', 'system.cpu', 'iowait', '%', '. If it is constantly high, your disks are a bottleneck and they slow your system down.') @@ -553,10 +632,10 @@ netdataDashboard.context = { }, 'system.io': { - info: function(os) { + info: function (os) { var s = 'Total Disk I/O, for all physical disks. You can get detailed information about each disk at the <a href="#menu_disk">Disks</a> section and per application Disk usage at the <a href="#menu_apps">Applications Monitoring</a> section.'; - if(os === 'linux') + if (os === 'linux') return s + ' Physical are all the disks that are listed in <code>/sys/block</code>, but do not exist in <code>/sys/devices/virtual/block</code>.'; else return s; @@ -615,16 +694,20 @@ netdataDashboard.context = { }, 'system.net': { - info: function(os) { + info: function (os) { var s = 'Total bandwidth of all physical network interfaces. This does not include <code>lo</code>, VPNs, network bridges, IFB devices, bond interfaces, etc. Only the bandwidth of physical network interfaces is aggregated.'; - if(os === 'linux') + if (os === 'linux') return s + ' Physical are all the network interfaces that are listed in <code>/proc/net/dev</code>, but do not exist in <code>/sys/devices/virtual/net</code>.'; else return s; } }, + 'system.ip': { + info: 'Total IP traffic in the system.' + }, + 'system.ipv4': { info: 'Total IPv4 Traffic.' }, @@ -676,9 +759,9 @@ netdataDashboard.context = { 'mem.ksm_ratios': { heads: [ - function(os, id) { + function (os, id) { void(os); - return '<div data-netdata="' + id + '"' + return '<div data-netdata="' + id + '"' + ' data-gauge-max-value="100"' + ' data-chart-library="gauge"' + ' data-title="Savings"' @@ -694,7 +777,7 @@ netdataDashboard.context = { }, 'mem.pgfaults': { - info: 'A <a href="https://en.wikipedia.org/wiki/Page_fault" target="_blank">page fault</a> 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. If 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, then it is called a <b>minor</b> or soft page fault. A <b>major</b> page fault is generated when the system needs to load the memory page from disk or swap memory.' + info: 'A <a href="https://en.wikipedia.org/wiki/Page_fault" target="_blank">page fault</a> 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. If 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, then it is called a <b>minor</b> or soft page fault. A <b>major</b> page fault is generated when the system needs to load the memory page from disk or swap memory.' }, 'mem.committed': { @@ -734,16 +817,47 @@ netdataDashboard.context = { }, // ------------------------------------------------------------------------ - // IPv4 + // IP + + 'ip.inerrors': { + info: 'Errors encountered during the reception of IP packets. ' + + '<code>noroutes</code> (<code>InNoRoutes</code>) counts packets that were dropped because there was no route to send them. ' + + '<code>truncated</code> (<code>InTruncatedPkts</code>) counts packets which is being discarded because the datagram frame didn\'t carry enough data. ' + + '<code>checksum</code> (<code>InCsumErrors</code>) counts packets that were dropped because they had wrong checksum. ' + }, - 'ipv4.tcpmemorypressures': { + 'ip.tcpmemorypressures': { info: 'Number of times a socket was put in <b>memory pressure</b> due to a non fatal memory allocation failure (the kernel attempts to work around this situation by reducing the send buffers, etc).' }, - 'ipv4.tcpconnaborts': { + 'ip.tcpconnaborts': { info: 'TCP connection aborts. <b>baddata</b> (<code>TCPAbortOnData</code>) happens while the connection is on <code>FIN_WAIT1</code> and the kernel receives a packet with a sequence number beyond the last one for this connection - the kernel responds with <code>RST</code> (closes the connection). <b>userclosed</b> (<code>TCPAbortOnClose</code>) happens when the kernel receives data on an already closed connection and responds with <code>RST</code>. <b>nomemory</b> (<code>TCPAbortOnMemory</code> 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 <code>RST</code>, sometimes it won\'t. <b>timeout</b> (<code>TCPAbortOnTimeout</code>) happens when a connection times out. <b>linger</b> (<code>TCPAbortOnLinger</code>) happens when the kernel killed a socket that was already closed by the application and lingered around for long enough. <b>failed</b> (<code>TCPAbortFailed</code>) happens when the kernel attempted to send an <code>RST</code> but failed because there was no memory available.' }, + 'ip.tcp_syn_queue': { + info: 'The <b>SYN queue</b> 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 ' + + '(i.e. someone sends lots of SYN packets and never completes the handshakes). ' + + '<b>drops</b> (or <code>TcpExtTCPReqQFullDrop</code>) is the number of connections dropped because the ' + + 'SYN queue was full and SYN cookies were disabled. ' + + '<b>cookies</b> (or <code>TcpExtTCPReqQFullDoCookies</code>) is the number of SYN cookies sent because the ' + + 'SYN queue was full.' + }, + + 'ip.tcp_accept_queue': { + info: 'The <b>accept queue</b> of the kernel holds the fully established TCP connections, waiting to be handled ' + + 'by the listening application. <b>overflows</b> (or <code>ListenOverflows</code>) is the number of ' + + 'established connections that could not be handled because the receive queue of the listening application ' + + 'was full. <b>drops</b> (or <code>ListenDrops</code>) is the 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.tcpsock': { info: 'The number of established TCP connections (known as <code>CurrEstab</code>). 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).' }, @@ -766,11 +880,6 @@ netdataDashboard.context = { + ' <code>TCPSynRetrans</code> shows retries for new outbound TCP connections, which can indicate general connectivity issues or backlog on the remote host.' }, - 'ipv4.tcplistenissues': { - info: '<b>overflows</b> (or <code>ListenOverflows</code>) is the number of incoming connections that could not be handled because the receive queue of the application was full (for both IPv4 and IPv6).' - + ' <b>drops</b> (or <code>ListenDrops</code>) is the 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 (for both IPv4 and IPv6).' - }, - // ------------------------------------------------------------------------ // APPS @@ -783,7 +892,7 @@ netdataDashboard.context = { }, 'apps.vmem': { - info: 'Virtual memory allocated by applications. Please check <a href="https://github.com/firehol/netdata/wiki/netdata-virtual-memory-size" target="_blank">this article</a> for more information.' + info: 'Virtual memory allocated by applications. Please check <a href="https://github.com/netdata/netdata/wiki/netdata-virtual-memory-size" target="_blank">this article</a> for more information.' }, 'apps.preads': { @@ -806,7 +915,7 @@ netdataDashboard.context = { }, 'users.vmem': { - info: 'Virtual memory allocated per user. Please check <a href="https://github.com/firehol/netdata/wiki/netdata-virtual-memory-size" target="_blank">this article</a> for more information.' + info: 'Virtual memory allocated per user. Please check <a href="https://github.com/netdata/netdata/wiki/netdata-virtual-memory-size" target="_blank">this article</a> for more information.' }, 'users.preads': { @@ -829,7 +938,7 @@ netdataDashboard.context = { }, 'groups.vmem': { - info: 'Virtual memory allocated per user group. Please check <a href="https://github.com/firehol/netdata/wiki/netdata-virtual-memory-size" target="_blank">this article</a> for more information.' + info: 'Virtual memory allocated per user group. Please check <a href="https://github.com/netdata/netdata/wiki/netdata-virtual-memory-size" target="_blank">this article</a> for more information.' }, 'groups.preads': { @@ -845,10 +954,10 @@ netdataDashboard.context = { 'tc.qos': { heads: [ - function(os, id) { + function (os, id) { void(os); - if(id.match(/.*-ifb$/)) + if (id.match(/.*-ifb$/)) return netdataDashboard.gaugeChart('Inbound', '12%', '', '#5555AA'); else return netdataDashboard.gaugeChart('Outbound', '12%', '', '#AA9900'); @@ -861,9 +970,9 @@ netdataDashboard.context = { 'net.net': { mainheads: [ - function(os, id) { + function (os, id) { void(os); - if(id.match(/^cgroup_.*/)) { + if (id.match(/^cgroup_.*/)) { var iface; try { iface = ' ' + id.substring(id.lastIndexOf('.net_') + 5, id.length); @@ -876,9 +985,9 @@ netdataDashboard.context = { else return ''; }, - function(os, id) { + function (os, id) { void(os); - if(id.match(/^cgroup_.*/)) { + if (id.match(/^cgroup_.*/)) { var iface; try { iface = ' ' + id.substring(id.lastIndexOf('.net_') + 5, id.length); @@ -893,16 +1002,16 @@ netdataDashboard.context = { } ], heads: [ - function(os, id) { + function (os, id) { void(os); - if(!id.match(/^cgroup_.*/)) + if (!id.match(/^cgroup_.*/)) return netdataDashboard.gaugeChart('Received', '12%', 'received'); else return ''; }, - function(os, id) { + function (os, id) { void(os); - if(!id.match(/^cgroup_.*/)) + if (!id.match(/^cgroup_.*/)) return netdataDashboard.gaugeChart('Sent', '12%', 'sent'); else return ''; @@ -995,38 +1104,38 @@ netdataDashboard.context = { 'mysql.queries': { info: 'The number of statements executed by the server.<ul>' + - '<li><strong>queries</strong> counts the statements executed within stored SQL programs.</li>' + - '<li><strong>questions</strong> counts the statements sent to the mysql server by mysql clients.</li>' + - '<li><strong>slow queries</strong> counts the number of statements that took more than <a href="http://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_long_query_time" target="_blank">long_query_time</a> seconds to be executed.' + - ' For more information about slow queries check the mysql <a href="http://dev.mysql.com/doc/refman/5.7/en/slow-query-log.html" target="_blank">slow query log</a>.</li>' + - '</ul>' + '<li><strong>queries</strong> counts the statements executed within stored SQL programs.</li>' + + '<li><strong>questions</strong> counts the statements sent to the mysql server by mysql clients.</li>' + + '<li><strong>slow queries</strong> counts the number of statements that took more than <a href="http://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_long_query_time" target="_blank">long_query_time</a> seconds to be executed.' + + ' For more information about slow queries check the mysql <a href="http://dev.mysql.com/doc/refman/5.7/en/slow-query-log.html" target="_blank">slow query log</a>.</li>' + + '</ul>' }, 'mysql.handlers': { info: 'Usage of the internal handlers of mysql. This chart provides very good insights of what the mysql server is actually doing.' + - ' (if the chart is not showing all these dimensions it is because they are zero - set <strong>Which dimensions to show?</strong> to <strong>All</strong> from the dashboard settings, to render even the zero values)<ul>' + - '<li><strong>commit</strong>, the number of internal <a href="http://dev.mysql.com/doc/refman/5.7/en/commit.html" target="_blank">COMMIT</a> statements.</li>' + - '<li><strong>delete</strong>, the number of times that rows have been deleted from tables.</li>' + - '<li><strong>prepare</strong>, a counter for the prepare phase of two-phase commit operations.</li>' + - '<li><strong>read first</strong>, the number of times the first entry in an index was read. A high value suggests that the server is doing a lot of full index scans; e.g. <strong>SELECT col1 FROM foo</strong>, with col1 indexed.</li>' + - '<li><strong>read key</strong>, the number of requests to read a row based on a key. If this value is high, it is a good indication that your tables are properly indexed for your queries.</li>' + - '<li><strong>read next</strong>, the number of requests to read the next row in key order. This value is incremented if you are querying an index column with a range constraint or if you are doing an index scan.</li>' + - '<li><strong>read prev</strong>, the number of requests to read the previous row in key order. This read method is mainly used to optimize <strong>ORDER BY ... DESC</strong>.</li>' + - '<li><strong>read rnd</strong>, the number of requests to read a row based on a fixed position. A high value indicates you are doing a lot of queries that require sorting of the result. You probably have a lot of queries that require MySQL to scan entire tables or you have joins that do not use keys properly.</li>' + - '<li><strong>read rnd next</strong>, the number of requests to read the next row in the data file. This value is high if you are doing a lot of table scans. Generally this suggests that your tables are not properly indexed or that your queries are not written to take advantage of the indexes you have.</li>' + - '<li><strong>rollback</strong>, the number of requests for a storage engine to perform a rollback operation.</li>' + - '<li><strong>savepoint</strong>, the number of requests for a storage engine to place a savepoint.</li>' + - '<li><strong>savepoint rollback</strong>, the number of requests for a storage engine to roll back to a savepoint.</li>' + - '<li><strong>update</strong>, the number of requests to update a row in a table.</li>' + - '<li><strong>write</strong>, the number of requests to insert a row in a table.</li>' + - '</ul>' + ' (if the chart is not showing all these dimensions it is because they are zero - set <strong>Which dimensions to show?</strong> to <strong>All</strong> from the dashboard settings, to render even the zero values)<ul>' + + '<li><strong>commit</strong>, the number of internal <a href="http://dev.mysql.com/doc/refman/5.7/en/commit.html" target="_blank">COMMIT</a> statements.</li>' + + '<li><strong>delete</strong>, the number of times that rows have been deleted from tables.</li>' + + '<li><strong>prepare</strong>, a counter for the prepare phase of two-phase commit operations.</li>' + + '<li><strong>read first</strong>, the number of times the first entry in an index was read. A high value suggests that the server is doing a lot of full index scans; e.g. <strong>SELECT col1 FROM foo</strong>, with col1 indexed.</li>' + + '<li><strong>read key</strong>, the number of requests to read a row based on a key. If this value is high, it is a good indication that your tables are properly indexed for your queries.</li>' + + '<li><strong>read next</strong>, the number of requests to read the next row in key order. This value is incremented if you are querying an index column with a range constraint or if you are doing an index scan.</li>' + + '<li><strong>read prev</strong>, the number of requests to read the previous row in key order. This read method is mainly used to optimize <strong>ORDER BY ... DESC</strong>.</li>' + + '<li><strong>read rnd</strong>, the number of requests to read a row based on a fixed position. A high value indicates you are doing a lot of queries that require sorting of the result. You probably have a lot of queries that require MySQL to scan entire tables or you have joins that do not use keys properly.</li>' + + '<li><strong>read rnd next</strong>, the number of requests to read the next row in the data file. This value is high if you are doing a lot of table scans. Generally this suggests that your tables are not properly indexed or that your queries are not written to take advantage of the indexes you have.</li>' + + '<li><strong>rollback</strong>, the number of requests for a storage engine to perform a rollback operation.</li>' + + '<li><strong>savepoint</strong>, the number of requests for a storage engine to place a savepoint.</li>' + + '<li><strong>savepoint rollback</strong>, the number of requests for a storage engine to roll back to a savepoint.</li>' + + '<li><strong>update</strong>, the number of requests to update a row in a table.</li>' + + '<li><strong>write</strong>, the number of requests to insert a row in a table.</li>' + + '</ul>' }, 'mysql.table_locks': { info: 'MySQL table locks counters: <ul>' + - '<li><strong>immediate</strong>, the number of times that a request for a table lock could be granted immediately.</li>' + - '<li><strong>waited</strong>, the number of times that a request for a table lock could not be granted immediately and a wait was needed. If this is high and you have performance problems, you should first optimize your queries, and then either split your table or tables or use replication.</li>' + - '</ul>' + '<li><strong>immediate</strong>, the number of times that a request for a table lock could be granted immediately.</li>' + + '<li><strong>waited</strong>, the number of times that a request for a table lock could not be granted immediately and a wait was needed. If this is high and you have performance problems, you should first optimize your queries, and then either split your table or tables or use replication.</li>' + + '</ul>' }, // ------------------------------------------------------------------------ @@ -1035,57 +1144,57 @@ netdataDashboard.context = { 'postgres.db_stat_blks': { info: 'Blocks reads from disk or cache.<ul>' + - '<li><strong>blks_read:</strong> number of disk blocks read in this database.</li>' + - '<li><strong>blks_hit:</strong> number of times disk blocks were found already in the buffer cache, so that a read was not necessary (this only includes hits in the PostgreSQL buffer cache, not the operating system's file system cache)</li>' + - '</ul>' + '<li><strong>blks_read:</strong> number of disk blocks read in this database.</li>' + + '<li><strong>blks_hit:</strong> number of times disk blocks were found already in the buffer cache, so that a read was not necessary (this only includes hits in the PostgreSQL buffer cache, not the operating system's file system cache)</li>' + + '</ul>' }, 'postgres.db_stat_tuple_write': { info: '<ul><li>Number of rows inserted/updated/deleted.</li>' + - '<li><strong>conflicts:</strong> number of queries canceled due to conflicts with recovery in this database. (Conflicts occur only on standby servers; see <a href="https://www.postgresql.org/docs/10/static/monitoring-stats.html#PG-STAT-DATABASE-CONFLICTS-VIEW" target="_blank">pg_stat_database_conflicts</a> for details.)</li>' + - '</ul>' + '<li><strong>conflicts:</strong> number of queries canceled due to conflicts with recovery in this database. (Conflicts occur only on standby servers; see <a href="https://www.postgresql.org/docs/10/static/monitoring-stats.html#PG-STAT-DATABASE-CONFLICTS-VIEW" target="_blank">pg_stat_database_conflicts</a> for details.)</li>' + + '</ul>' }, 'postgres.db_stat_temp_bytes': { info: 'Temporary files can be created on disk for sorts, hashes, and temporary query results.' }, 'postgres.db_stat_temp_files': { info: '<ul>' + - '<li><strong>files:</strong> number of temporary files created by queries. All temporary files are counted, regardless of why the temporary file was created (e.g., sorting or hashing).</li>' + - '</ul>' + '<li><strong>files:</strong> number of temporary files created by queries. All temporary files are counted, regardless of why the temporary file was created (e.g., sorting or hashing).</li>' + + '</ul>' }, 'postgres.archive_wal': { - info: 'WAL archiving.<ul>' + - '<li><strong>total:</strong> total files.</li>' + - '<li><strong>ready:</strong> WAL waiting to be archived.</li>' + - '<li><strong>done:</strong> WAL successfully archived' + - 'Ready WAL can indicate archive_command is in error, see <a href="https://www.postgresql.org/docs/current/static/continuous-archiving.html" target="_blank">Continuous Archiving and Point-in-Time Recovery</a>.</li>' + - '</ul>' + info: 'WAL archiving.<ul>' + + '<li><strong>total:</strong> total files.</li>' + + '<li><strong>ready:</strong> WAL waiting to be archived.</li>' + + '<li><strong>done:</strong> WAL successfully archived. ' + + 'Ready WAL can indicate archive_command is in error, see <a href="https://www.postgresql.org/docs/current/static/continuous-archiving.html" target="_blank">Continuous Archiving and Point-in-Time Recovery</a>.</li>' + + '</ul>' }, 'postgres.checkpointer': { info: 'Number of checkpoints.<ul>' + - '<li><strong>scheduled:</strong> when checkpoint_timeout is reached.</li>' + - '<li><strong>requested:</strong> when max_wal_size is reached.</li>' + - '</ul>' + - 'For more information see <a href="https://www.postgresql.org/docs/current/static/wal-configuration.html" target="_blank">WAL Configuration</a>.' + '<li><strong>scheduled:</strong> when checkpoint_timeout is reached.</li>' + + '<li><strong>requested:</strong> when max_wal_size is reached.</li>' + + '</ul>' + + 'For more information see <a href="https://www.postgresql.org/docs/current/static/wal-configuration.html" target="_blank">WAL Configuration</a>.' }, 'postgres.autovacuum': { - info: 'PostgreSQL databases require periodic maintenance known as vacuuming. For many installations, it is sufficient to let vacuuming be performed by the autovacuum daemon.' + - 'For more information see <a href="https://www.postgresql.org/docs/current/static/routine-vacuuming.html#AUTOVACUUM" target="_blank">The Autovacuum Daemon</a>.' + info: 'PostgreSQL databases require periodic maintenance known as vacuuming. For many installations, it is sufficient to let vacuuming be performed by the autovacuum daemon. ' + + 'For more information see <a href="https://www.postgresql.org/docs/current/static/routine-vacuuming.html#AUTOVACUUM" target="_blank">The Autovacuum Daemon</a>.' }, 'postgres.standby_delta': { info: 'Streaming replication delta.<ul>' + - '<li><strong>sent_delta:</strong> replication delta sent to standby.</li>' + - '<li><strong>write_delta:</strong> replication delta written to disk by this standby.</li>' + - '<li><strong>flush_delta:</strong> replication delta flushed to disk by this standby server.</li>' + - '<li><strong>replay_delta:</strong> replication delta replayed into the database on this standby server.</li>' + - '</ul>' + - 'For more information see <a href="https://www.postgresql.org/docs/current/static/warm-standby.html#SYNCHRONOUS-REPLICATION" target="_blank">Synchronous Replication</a>.' + '<li><strong>sent_delta:</strong> replication delta sent to standby.</li>' + + '<li><strong>write_delta:</strong> replication delta written to disk by this standby.</li>' + + '<li><strong>flush_delta:</strong> replication delta flushed to disk by this standby server.</li>' + + '<li><strong>replay_delta:</strong> replication delta replayed into the database on this standby server.</li>' + + '</ul>' + + 'For more information see <a href="https://www.postgresql.org/docs/current/static/warm-standby.html#SYNCHRONOUS-REPLICATION" target="_blank">Synchronous Replication</a>.' }, 'postgres.replication_slot': { info: 'Replication slot files.<ul>' + - '<li><strong>wal_keeped:</strong> WAL files retained by each replication slots.</li>' + - '<li><strong>pg_replslot_files:</strong> files present in pg_replslot.</li>' + - '</ul>' + - 'For more information see <a href="https://www.postgresql.org/docs/current/static/warm-standby.html#STREAMING-REPLICATION-SLOTS" target="_blank">Replication Slots</a>.' + '<li><strong>wal_keeped:</strong> WAL files retained by each replication slots.</li>' + + '<li><strong>pg_replslot_files:</strong> files present in pg_replslot.</li>' + + '</ul>' + + 'For more information see <a href="https://www.postgresql.org/docs/current/static/warm-standby.html#STREAMING-REPLICATION-SLOTS" target="_blank">Replication Slots</a>.' }, @@ -1115,9 +1224,9 @@ netdataDashboard.context = { 'apache.workers': { mainheads: [ - function(os, id) { + function (os, id) { void(os); - return '<div data-netdata="' + id + '"' + return '<div data-netdata="' + id + '"' + ' data-dimensions="busy"' + ' data-append-options="percentage"' + ' data-gauge-max-value="100"' @@ -1176,9 +1285,9 @@ netdataDashboard.context = { 'lighttpd.workers': { mainheads: [ - function(os, id) { + function (os, id) { void(os); - return '<div data-netdata="' + id + '"' + return '<div data-netdata="' + id + '"' + ' data-dimensions="busy"' + ' data-append-options="percentage"' + ' data-gauge-max-value="100"' @@ -1232,7 +1341,7 @@ netdataDashboard.context = { 'httpcheck.responsetime': { info: 'The <code>response time</code> describes the time passed between request and response. ' + - 'Currently, the accuracy of the response time is low and should be used as reference only.' + 'Currently, the accuracy of the response time is low and should be used as reference only.' }, 'httpcheck.responselength': { @@ -1242,8 +1351,8 @@ netdataDashboard.context = { 'httpcheck.status': { valueRange: "[0, 1]", info: 'This chart verifies the response of the webserver. Each status dimension will have a value of <code>1</code> if triggered. ' + - 'Dimension <code>success</code> is <code>1</code> only if all constraints are satisfied.' + - 'This chart is most useful for alarms or third-party apps.' + 'Dimension <code>success</code> is <code>1</code> only if all constraints are satisfied. ' + + 'This chart is most useful for alarms or third-party apps.' }, // ------------------------------------------------------------------------ @@ -1267,9 +1376,9 @@ netdataDashboard.context = { 'retroshare.peers': { info: 'Number of (connected) RetroShare friends.', mainheads: [ - function(os, id) { + function (os, id) { void(os); - return '<div data-netdata="' + id + '"' + return '<div data-netdata="' + id + '"' + ' data-dimensions="peers_connected"' + ' data-append-options="friends"' + ' data-chart-library="easypiechart"' @@ -1306,9 +1415,9 @@ netdataDashboard.context = { 'cgroup.cpu': { mainheads: [ - function(os, id) { + function (os, id) { void(os); - return '<div data-netdata="' + id + '"' + return '<div data-netdata="' + id + '"' + ' data-chart-library="gauge"' + ' data-title="CPU"' + ' data-units="%"' @@ -1325,9 +1434,9 @@ netdataDashboard.context = { 'cgroup.mem_usage': { mainheads: [ - function(os, id) { + function (os, id) { void(os); - return '<div data-netdata="' + id + '"' + return '<div data-netdata="' + id + '"' + ' data-chart-library="gauge"' + ' data-title="Memory"' + ' data-units="MB"' @@ -1344,9 +1453,9 @@ netdataDashboard.context = { 'cgroup.throttle_io': { mainheads: [ - function(os, id) { + function (os, id) { void(os); - return '<div data-netdata="' + id + '"' + return '<div data-netdata="' + id + '"' + ' data-dimensions="read"' + ' data-chart-library="gauge"' + ' data-title="Read Disk I/O"' @@ -1359,9 +1468,9 @@ netdataDashboard.context = { + ' data-colors="' + NETDATA.colors[2] + '"' + ' role="application"></div>'; }, - function(os, id) { + function (os, id) { void(os); - return '<div data-netdata="' + id + '"' + return '<div data-netdata="' + id + '"' + ' data-dimensions="write"' + ' data-chart-library="gauge"' + ' data-title="Write Disk I/O"' @@ -1499,9 +1608,9 @@ netdataDashboard.context = { 'web_log.response_statuses': { info: 'Web server responses by type. <code>success</code> includes <b>1xx</b>, <b>2xx</b> and <b>304</b>, <code>error</code> includes <b>5xx</b>, <code>redirect</code> includes <b>3xx</b> except <b>304</b>, <code>bad</code> includes <b>4xx</b>, <code>other</code> are all the other responses.', mainheads: [ - function(os, id) { + function (os, id) { void(os); - return '<div data-netdata="' + id + '"' + return '<div data-netdata="' + id + '"' + ' data-dimensions="success"' + ' data-chart-library="gauge"' + ' data-title="Successful"' @@ -1517,9 +1626,9 @@ netdataDashboard.context = { + ' role="application"></div>'; }, - function(os, id) { + function (os, id) { void(os); - return '<div data-netdata="' + id + '"' + return '<div data-netdata="' + id + '"' + ' data-dimensions="redirect"' + ' data-chart-library="gauge"' + ' data-title="Redirects"' @@ -1535,9 +1644,9 @@ netdataDashboard.context = { + ' role="application"></div>'; }, - function(os, id) { + function (os, id) { void(os); - return '<div data-netdata="' + id + '"' + return '<div data-netdata="' + id + '"' + ' data-dimensions="bad"' + ' data-chart-library="gauge"' + ' data-title="Bad Requests"' @@ -1553,9 +1662,9 @@ netdataDashboard.context = { + ' role="application"></div>'; }, - function(os, id) { + function (os, id) { void(os); - return '<div data-netdata="' + id + '"' + return '<div data-netdata="' + id + '"' + ' data-dimensions="error"' + ' data-chart-library="gauge"' + ' data-title="Server Errors"' @@ -1575,20 +1684,20 @@ netdataDashboard.context = { 'web_log.response_codes': { info: 'Web server responses by code family. ' + - 'According to the standards <code>1xx</code> are informational responses, ' + - '<code>2xx</code> are successful responses, ' + - '<code>3xx</code> are redirects (although they include <b>304</b> which is used as "<b>not modified</b>"), ' + - '<code>4xx</code> are bad requests, ' + - '<code>5xx</code> are internal server errors, ' + - '<code>other</code> are non-standard responses, ' + - '<code>unmatched</code> counts the lines in the log file that are not matched by the plugin (<a href="https://github.com/firehol/netdata/issues/new?title=web_log%20reports%20unmatched%20lines&body=web_log%20plugin%20reports%20unmatched%20lines.%0A%0AThis%20is%20my%20log:%0A%0A%60%60%60txt%0A%0Aplease%20paste%20your%20web%20server%20log%20here%0A%0A%60%60%60" target="_blank">let us know</a> if you have any unmatched).' + 'According to the standards <code>1xx</code> are informational responses, ' + + '<code>2xx</code> are successful responses, ' + + '<code>3xx</code> are redirects (although they include <b>304</b> which is used as "<b>not modified</b>"), ' + + '<code>4xx</code> are bad requests, ' + + '<code>5xx</code> are internal server errors, ' + + '<code>other</code> are non-standard responses, ' + + '<code>unmatched</code> counts the lines in the log file that are not matched by the plugin (<a href="https://github.com/netdata/netdata/issues/new?title=web_log%20reports%20unmatched%20lines&body=web_log%20plugin%20reports%20unmatched%20lines.%0A%0AThis%20is%20my%20log:%0A%0A%60%60%60txt%0A%0Aplease%20paste%20your%20web%20server%20log%20here%0A%0A%60%60%60" target="_blank">let us know</a> if you have any unmatched).' }, 'web_log.response_time': { mainheads: [ - function(os, id) { + function (os, id) { void(os); - return '<div data-netdata="' + id + '"' + return '<div data-netdata="' + id + '"' + ' data-dimensions="avg"' + ' data-chart-library="gauge"' + ' data-title="Average Response Time"' @@ -1618,7 +1727,7 @@ netdataDashboard.context = { }, '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 <a href="https://github.com/firehol/netdata/blob/master/conf.d/python.d/web_log.conf" target="_blank"><code>/etc/netdata/python.d/web_log.conf</code></a>).' + 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 <a href="https://github.com/netdata/netdata/blob/master/conf.d/python.d/web_log.conf" target="_blank"><code>/etc/netdata/python.d/web_log.conf</code></a>).' }, // ------------------------------------------------------------------------ @@ -1626,15 +1735,15 @@ netdataDashboard.context = { 'web_log.squid_response_statuses': { info: 'Squid responses by type. ' + - '<code>success</code> includes <b>1xx</b>, <b>2xx</b>, <b>000</b>, <b>304</b>, ' + - '<code>error</code> includes <b>5xx</b> and <b>6xx</b>, ' + - '<code>redirect</code> includes <b>3xx</b> except <b>304</b>, ' + - '<code>bad</code> includes <b>4xx</b>, ' + - '<code>other</code> are all the other responses.', + '<code>success</code> includes <b>1xx</b>, <b>2xx</b>, <b>000</b>, <b>304</b>, ' + + '<code>error</code> includes <b>5xx</b> and <b>6xx</b>, ' + + '<code>redirect</code> includes <b>3xx</b> except <b>304</b>, ' + + '<code>bad</code> includes <b>4xx</b>, ' + + '<code>other</code> are all the other responses.', mainheads: [ - function(os, id) { + function (os, id) { void(os); - return '<div data-netdata="' + id + '"' + return '<div data-netdata="' + id + '"' + ' data-dimensions="success"' + ' data-chart-library="gauge"' + ' data-title="Successful"' @@ -1650,9 +1759,9 @@ netdataDashboard.context = { + ' role="application"></div>'; }, - function(os, id) { + function (os, id) { void(os); - return '<div data-netdata="' + id + '"' + return '<div data-netdata="' + id + '"' + ' data-dimensions="redirect"' + ' data-chart-library="gauge"' + ' data-title="Redirects"' @@ -1668,9 +1777,9 @@ netdataDashboard.context = { + ' role="application"></div>'; }, - function(os, id) { + function (os, id) { void(os); - return '<div data-netdata="' + id + '"' + return '<div data-netdata="' + id + '"' + ' data-dimensions="bad"' + ' data-chart-library="gauge"' + ' data-title="Bad Requests"' @@ -1686,9 +1795,9 @@ netdataDashboard.context = { + ' role="application"></div>'; }, - function(os, id) { + function (os, id) { void(os); - return '<div data-netdata="' + id + '"' + return '<div data-netdata="' + id + '"' + ' data-dimensions="error"' + ' data-chart-library="gauge"' + ' data-title="Server Errors"' @@ -1708,22 +1817,22 @@ netdataDashboard.context = { 'web_log.squid_response_codes': { info: 'Web server responses by code family. ' + - 'According to HTTP standards <code>1xx</code> are informational responses, ' + - '<code>2xx</code> are successful responses, ' + - '<code>3xx</code> are redirects (although they include <b>304</b> which is used as "<b>not modified</b>"), ' + - '<code>4xx</code> are bad requests, ' + - '<code>5xx</code> are internal server errors. ' + - 'Squid also defines <code>000</code> mostly for UDP requests, and ' + - '<code>6xx</code> for broken upstream servers sending wrong headers. ' + - 'Finally, <code>other</code> are non-standard responses, and ' + - '<code>unmatched</code> counts the lines in the log file that are not matched by the plugin (<a href="https://github.com/firehol/netdata/issues/new?title=web_log%20reports%20unmatched%20lines&body=web_log%20plugin%20reports%20unmatched%20lines.%0A%0AThis%20is%20my%20log:%0A%0A%60%60%60txt%0A%0Aplease%20paste%20your%20web%20server%20log%20here%0A%0A%60%60%60" target="_blank">let us know</a> if you have any unmatched).' + 'According to HTTP standards <code>1xx</code> are informational responses, ' + + '<code>2xx</code> are successful responses, ' + + '<code>3xx</code> are redirects (although they include <b>304</b> which is used as "<b>not modified</b>"), ' + + '<code>4xx</code> are bad requests, ' + + '<code>5xx</code> are internal server errors. ' + + 'Squid also defines <code>000</code> mostly for UDP requests, and ' + + '<code>6xx</code> for broken upstream servers sending wrong headers. ' + + 'Finally, <code>other</code> are non-standard responses, and ' + + '<code>unmatched</code> counts the lines in the log file that are not matched by the plugin (<a href="https://github.com/netdata/netdata/issues/new?title=web_log%20reports%20unmatched%20lines&body=web_log%20plugin%20reports%20unmatched%20lines.%0A%0AThis%20is%20my%20log:%0A%0A%60%60%60txt%0A%0Aplease%20paste%20your%20web%20server%20log%20here%0A%0A%60%60%60" target="_blank">let us know</a> if you have any unmatched).' }, 'web_log.squid_duration': { mainheads: [ - function(os, id) { + function (os, id) { void(os); - return '<div data-netdata="' + id + '"' + return '<div data-netdata="' + id + '"' + ' data-dimensions="avg"' + ' data-chart-library="gauge"' + ' data-title="Average Response Time"' @@ -1749,60 +1858,60 @@ netdataDashboard.context = { }, '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 <a href="https://github.com/firehol/netdata/blob/master/conf.d/python.d/web_log.conf" target="_blank"><code>/etc/netdata/python.d/web_log.conf</code></a>).' + 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 <a href="https://github.com/netdata/netdata/blob/master/conf.d/python.d/web_log.conf" target="_blank"><code>/etc/netdata/python.d/web_log.conf</code></a>).' }, 'web_log.squid_transport_methods': { info: 'Break down per delivery method: <code>TCP</code> are requests on the HTTP port (usually 3128), ' + - '<code>UDP</code> 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. ' + - '<code>NONE</code> 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 <code>CONNECT</code> requests.' + '<code>UDP</code> 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. ' + + '<code>NONE</code> 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 <code>CONNECT</code> 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 <a href="http://wiki.squid-cache.org/SquidFaq/SquidLogs">squid documentation about them</a>.' + 'Check the <a href="http://wiki.squid-cache.org/SquidFaq/SquidLogs">squid documentation about them</a>.' }, 'web_log.squid_handling_opts': { info: 'These tags are optional and describe why the particular handling was performed or where the request came from. ' + - '<code>CLIENT</code> means that the client request placed limits affecting the response. Usually seen with client issued a <b>no-cache</b>, or analogous cache control command along with the request. Thus, the cache has to validate the object.' + - '<code>IMS</code> states that the client sent a revalidation (conditional) request. ' + - '<code>ASYNC</code>, 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. ' + - '<code>SWAPFAIL</code> 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. ' + - '<code>REFRESH</code> when a revalidation (conditional) request was sent to the server. ' + - '<code>SHARED</code> when this request was combined with an existing transaction by collapsed forwarding. NOTE: the existing request is not marked as SHARED. ' + - '<code>REPLY</code> 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.' + '<code>CLIENT</code> means that the client request placed limits affecting the response. Usually seen with client issued a <b>no-cache</b>, or analogous cache control command along with the request. Thus, the cache has to validate the object.' + + '<code>IMS</code> states that the client sent a revalidation (conditional) request. ' + + '<code>ASYNC</code>, 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. ' + + '<code>SWAPFAIL</code> 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. ' + + '<code>REFRESH</code> when a revalidation (conditional) request was sent to the server. ' + + '<code>SHARED</code> when this request was combined with an existing transaction by collapsed forwarding. NOTE: the existing request is not marked as SHARED. ' + + '<code>REPLY</code> 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. ' + - '<code>NEGATIVE</code> is only seen on HIT responses, indicating the response was a cached error response. e.g. <b>404 not found</b>. ' + - '<code>STALE</code> means the object was cached and served stale. This is usually caused by stale-while-revalidate or stale-if-error cache controls. ' + - '<code>OFFLINE</code> when the requested object was retrieved from the cache during offline_mode. The offline mode never validates any object. ' + - '<code>INVALID</code> when an invalid request was received. An error response was delivered indicating what the problem was. ' + - '<code>FAIL</code> is only seen on <code>REFRESH</code> 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. ' + - '<code>MODIFIED</code> is only seen on <code>REFRESH</code> responses to indicate revalidation produced a new modified object. ' + - '<code>UNMODIFIED</code> is only seen on <code>REFRESH</code> responses to indicate revalidation produced a <b>304</b> (Not Modified) status, which was relayed to the client. ' + - '<code>REDIRECT</code> when squid generated an HTTP redirect response to this request.' + '<code>NEGATIVE</code> is only seen on HIT responses, indicating the response was a cached error response. e.g. <b>404 not found</b>. ' + + '<code>STALE</code> means the object was cached and served stale. This is usually caused by stale-while-revalidate or stale-if-error cache controls. ' + + '<code>OFFLINE</code> when the requested object was retrieved from the cache during offline_mode. The offline mode never validates any object. ' + + '<code>INVALID</code> when an invalid request was received. An error response was delivered indicating what the problem was. ' + + '<code>FAIL</code> is only seen on <code>REFRESH</code> 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. ' + + '<code>MODIFIED</code> is only seen on <code>REFRESH</code> responses to indicate revalidation produced a new modified object. ' + + '<code>UNMODIFIED</code> is only seen on <code>REFRESH</code> responses to indicate revalidation produced a <b>304</b> (Not Modified) status, which was relayed to the client. ' + + '<code>REDIRECT</code> 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. ' + - '<code>HIT</code> when the response object delivered was the local cache object. ' + - '<code>MEM</code> when the response object came from memory cache, avoiding disk accesses. Only seen on HIT responses. ' + - '<code>MISS</code> when the response object delivered was the network response object. ' + - '<code>DENIED</code> when the request was denied by access controls. ' + - '<code>NOFETCH</code> 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). ' + - '<code>TUNNEL</code> when a binary tunnel was established for this transaction.' + '<code>HIT</code> when the response object delivered was the local cache object. ' + + '<code>MEM</code> when the response object came from memory cache, avoiding disk accesses. Only seen on HIT responses. ' + + '<code>MISS</code> when the response object delivered was the network response object. ' + + '<code>DENIED</code> when the request was denied by access controls. ' + + '<code>NOFETCH</code> 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). ' + + '<code>TUNNEL</code> 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 occured during response delivery (if any). ' + - '<code>ABORTED</code> when the response was not completed due to the connection being aborted (usually by the client). ' + - '<code>TIMEOUT</code>, when the response was not completed due to a connection timeout.' + '<code>ABORTED</code> when the response was not completed due to the connection being aborted (usually by the client). ' + + '<code>TIMEOUT</code>, when the response was not completed due to a connection timeout.' }, // ------------------------------------------------------------------------ @@ -1819,7 +1928,7 @@ netdataDashboard.context = { commonMax: true, valueRange: "[0, 100]", info: 'The <code>Autonomy</code> 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 <code>Self consumption</code> indicates the ratio between the current power generated and the current load. When it reaches 100 %, the <code>Autonomy</code> declines, since the solar panels can not produce enough energy and need support from the grid.' + 'The <code>Self consumption</code> indicates the ratio between the current power generated and the current load. When it reaches 100 %, the <code>Autonomy</code> declines, since the solar panels can not produce enough energy and need support from the grid.' }, 'fronius.energy.today': { @@ -1842,14 +1951,14 @@ netdataDashboard.context = { 'portcheck.latency': { info: 'The <code>latency</code> 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.' + 'Currently, the accuracy of the latency is low and should be used as reference only.' }, 'portcheck.status': { valueRange: "[0, 1]", info: 'The <code>status</code> chart verifies the availability of the service. ' + - 'Each status dimension will have a value of <code>1</code> if triggered. Dimension <code>success</code> is <code>1</code> only if connection could be established.' + - 'This chart is most useful for alarms and third-party apps.' + 'Each status dimension will have a value of <code>1</code> if triggered. Dimension <code>success</code> is <code>1</code> only if connection could be established. ' + + 'This chart is most useful for alarms and third-party apps.' }, // ------------------------------------------------------------------------ @@ -1880,8 +1989,15 @@ netdataDashboard.context = { }, 'chrony.residualfreq': { - info: 'This shows the <code>residual frequency</code> 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 <code>skew</code>) 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.', + info: 'This shows the <code>residual frequency</code> 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 <code>skew</code>) 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] }, @@ -1905,7 +2021,8 @@ netdataDashboard.context = { }, '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. <b>before any RAID levels</b>). 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. <code>unallocated</code> is the physical disk space that is not allocated yet and is available to become data, metdata or system on demand. When <code>unallocated</code> 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 <code>unallocated</code>. You can keep your volume healthy by running the <code>btrfs balance</code> command on it regularly (check <code>man btrfs-balance</code> for more info).' + info: 'Physical disk usage of BTRFS. The disk space reported here is the raw physical disk space assigned to the BTRFS volume (i.e. <b>before any RAID levels</b>). 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. <code>unallocated</code> is the physical disk space that is not allocated yet and is available to become data, metdata or system on demand. When <code>unallocated</code> 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 <code>unallocated</code>. You can keep your volume healthy by running the <code>btrfs balance</code> command on it regularly (check <code>man btrfs-balance</code> for more info). Note that some of the spac elisted as <code>unallocated</code> may not actually be usable if the volume uses devices of different sizes.', + colors: [NETDATA.colors[12]] }, 'btrfs.data': { @@ -1917,7 +2034,7 @@ netdataDashboard.context = { }, 'btrfs.system': { - info: 'Logical disk usage for BTRFS system. System chunks store information aobut 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.' + 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.' }, // ------------------------------------------------------------------------ @@ -2064,6 +2181,140 @@ netdataDashboard.context = { '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 connect users on the monitored Spigot server.' + }, + + 'unbound.queries': { + info: 'Shows the number of queries being processed of each type. Note that <code>Recursive</code> queries are also accounted as cache misses.' + }, + + 'unbound.reqlist': { + info: 'Shows various stats about Unbound\'s internal request list.' + }, + + 'unbound.recursion': { + info: 'Average and median time to complete recursive name resolution.' + }, + + 'unbound.cache': { + info: 'The number of items in each of the various caches.' + }, + + 'unbound.threads.queries': { + height: 0.2 + }, + + 'unbound.threads.reqlist': { + height: 0.2 + }, + + 'unbound.threads.recursion': { + height: 0.2 + }, + + '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 partialy processed but suspended.' + }, + + 'boinc.states': { + info: 'Counts of tasks in each task state. The normal sequence of states is <code>New</code>, <code>Downloading</code>, <code>Ready to Run</code>, <code>Uploading</code>, <code>Uploaded</code>. Tasks which are marked <code>Ready to Run</code> may be actively running, or may be waiting to be scheduled. <code>Compute Errors</code> are tasks which failed for some reason during execution. <code>Aborted</code> tasks were manually cancelled, and will not be processed. <code>Failed Uploads</code> 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. <code>Scheduled</code> tasks are the ones which will run if the system is permitted to process tasks. <code>Preempted</code> tasks are on standby, and will run if a <code>Scheduled</code> task stops running for some reason. <code>Uninitialized</code> 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. <code>Executing</code> tasks are running right now. <code>Suspended</code> 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). <code>Quit</code> tasks are exiting gracefully. <code>Aborted</code> tasks exceeded some resource limit, and are being shut down. <code>Copy Pending</code> tasks are waiting on a background file transfer to finish. <code>Uninitialized</code> 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. ' + + '<code>1=ONLINE</code> backend server is fully operational, ' + + '<code>2=SHUNNED</code> 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, ' + + '<code>3=OFFLINE_SOFT</code> 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, ' + + '<code>4=OFFLINE_HARD</code> 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, ' + + '<code>-1</code> 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: '<code>questions</code> total number of queries sent from frontends, ' + + '<code>slow_queries</code> number of queries that ran for longer than the threshold in milliseconds defined in global variable <code>mysql-long_query_time</code>. ' + }, + + 'proxysql.connections': { + info: '<code>aborted</code> number of frontend connections aborted due to invalid credential or max_connections reached, ' + + '<code>connected</code> number of frontend connections currently connected, ' + + '<code>created</code> number of frontend connections created, ' + + '<code>non_idle</code> 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' } // ------------------------------------------------------------------------ |