X-Git-Url: https://arthur.barton.de/gitweb/?a=blobdiff_plain;f=web%2Fdashboard_info.js;h=a9278cbb6a73ce5d61399c511b04d10cd712a52a;hb=aa6b96fc2d421517a59a1aaaf91be5f201d34287;hp=7da621ef10eae5b0ee80008faec771d4c4773eea;hpb=6f44ad6ea02e5e5bd316af09756cda740c3c6f56;p=netdata.git
diff --git a/web/dashboard_info.js b/web/dashboard_info.js
index 7da621ef..a9278cbb 100644
--- a/web/dashboard_info.js
+++ b/web/dashboard_info.js
@@ -28,7 +28,7 @@ netdataDashboard.menu = {
'tc': {
title: 'Quality of Service',
icon: '',
- info: 'Netdata collects and visualizes 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).'
+ info: 'Netdata collects and visualizes 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': {
@@ -85,6 +85,12 @@ netdataDashboard.menu = {
info: 'Readings of the configured system sensors.'
},
+ 'ipmi': {
+ title: 'IPMI',
+ icon: '',
+ info: 'The Intelligent Platform Management Interface (IPMI) is a set of computer interface specifications for an autonomous computer subsystem that provides management and monitoring capabilities independently of the host system\'s CPU, firmware (BIOS or UEFI) and operating system.'
+ },
+
'nfsd': {
title: 'NFS Server',
icon: '',
@@ -97,6 +103,12 @@ netdataDashboard.menu = {
info: 'Performance metrics of the NFS operations of this system, acting as an NFS client.'
},
+ 'zfs': {
+ title: 'ZFS filesystem',
+ icon: '',
+ info: 'Performance metrics of the ZFS filesystem. The following charts visualize all metrics reported by arcstat.py and arc_summary.py.'
+ },
+
'apps': {
title: 'Applications',
icon: '',
@@ -222,7 +234,7 @@ netdataDashboard.menu = {
'web_log': {
title: undefined,
icon: '',
- info: 'Information extracted from the web server log file. netdata python.d/web_log plugin incrementally parses web server log files to provide a real-time break down of key web server performance metrics. A special log file format is also supported (for nginx and apache) that allows netdata to extract timing information for the web server responses and bandwidth for both requests and responses. The web_log plugin can also be configured to provide a break down of requests per URL pattern (check /etc/netdata/python.d/web_log.conf). netdata provides also several alarms based on the information on these charts, such as too many bad requests, too many redirects, too many internal errros, unreasonably slow responses, too many requests and too few requests.'
+ info: 'Information extracted from a web server log file. web_log plugin incrementally parses the web server log file to provide, in real-time, a break down of key web server performance metrics. 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': {
@@ -272,11 +284,11 @@ netdataDashboard.menu = {
// information about the submenus
netdataDashboard.submenu = {
'web_log.bandwidth': {
- info: 'Bandwidth of requests (received) and responses (sent). received requires a special file format (without it, the web server log does not have this information). This chart may present unusual spikes, since the whole bandwidth will be 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.'
+ 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 category (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).'
+ 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': {
@@ -284,7 +296,7 @@ netdataDashboard.submenu = {
},
'web_log.timings': {
- info: 'Web server response timings - the time the web server needed to prepare and respond to requests. This requires a special 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.'
+ 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': {
@@ -847,17 +859,16 @@ netdataDashboard.context = {
height: 0.5
},
- 'web_log.response_codes': {
- info: 'Break down of web server responses by response code type. 1xx are informational responses, 2xx are successful responses, 3xx are redirects, 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 (please open a github issue to help us fix it, if you have any unmatched lines).',
-
+ 'web_log.response_statuses': {
+ info: 'Web server responses by type. success includes 1xx, 2xx and 304, error includes 5xx, 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.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) {
@@ -928,7 +947,7 @@ netdataDashboard.context = {
return '';
}
]
},
'web_log.detailed_response_codes': {
- info: 'Number of responses for each response code.'
+ info: 'Number of responses for each response code individually.'
},
'web_log.requests_per_ipproto': {
@@ -950,7 +970,7 @@ netdataDashboard.context = {
},
'web_log.clients': {
- info: 'Unique client IPs accessing the web server, within each data collection iteration. So, if data collection is per second, this chart shows unique client IPs per second.'
+ 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': {