From: Costa Tsaousis (ktsaou) Date: Mon, 13 Feb 2017 18:20:25 +0000 (+0200) Subject: fixed typos and shortened the descriptions of web_log charts at the dashboard X-Git-Tag: ab-debian_0.20170221.01-0ab1~1^2~15^2 X-Git-Url: https://arthur.barton.de/cgi-bin/gitweb.cgi?p=netdata.git;a=commitdiff_plain;h=79a565b5c8e169ca037f0531082242ea061c5a4e fixed typos and shortened the descriptions of web_log charts at the dashboard --- diff --git a/web/dashboard_info.js b/web/dashboard_info.js index d34b5c17..7b8728c3 100644 --- a/web/dashboard_info.js +++ b/web/dashboard_info.js @@ -222,7 +222,7 @@ netdataDashboard.menu = { 'web_log': { title: undefined, icon: '', - info: 'Information extracted from a web server log file. python.d/web_log plugin incrementally parses the web server log file to provide, in real-time, a break down of key web server performance metrics. A special log file format may optionally be used (for nginx and apache) allowing the plugin to extract timing information for the web server responses 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). netdata attaches several alarms on these charts, such as too many bad requests, too many redirects, too many internal errors, unreasonably slow responses, unreasonably many requests (i.e. web attack) and unreasonably few requests (i.e. something is wrong).' + 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 +272,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 +284,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': { @@ -848,7 +848,7 @@ netdataDashboard.context = { }, 'web_log.response_statuses': { - info: 'Break down of web server responses by response type. success included all 1xx, 2xx and 304 (not modified) responses, error are all 5xxresponses, redirect are all 3xx responses, except 304, bad are all 4xx responses, other are all the other responses.', + 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); @@ -925,7 +925,7 @@ netdataDashboard.context = { }, 'web_log.response_codes': { - info: 'Break down of web server responses by response code family. 1xx are informational responses, 2xx are successful responses, 3xx are redirects (although they include 304 which means "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 (please open a github issue to help us fix it, if you have any unmatched lines).' + 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': { @@ -950,7 +950,7 @@ netdataDashboard.context = { }, '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': { diff --git a/web/index.html b/web/index.html index 545dd6ca..7e1a517a 100644 --- a/web/index.html +++ b/web/index.html @@ -2828,7 +2828,7 @@ }); NETDATA.requiredJs.push({ - url: NETDATA.serverDefault + 'dashboard_info.js?v20170213-1', + url: NETDATA.serverDefault + 'dashboard_info.js?v20170213-2', async: false, isAlreadyLoaded: function() { return false; } });