X-Git-Url: https://arthur.barton.de/gitweb/?p=netdata.git;a=blobdiff_plain;f=web%2Fdashboard_info.js;h=03b2a4cedbe4372d2e7035a5e1470e38c0726d6f;hp=173e95bb921f016be6be9999bf084aa188beffd1;hb=204e0d099d9e5f679bd72f581209a485c83d6189;hpb=290cb6b06ecbd8c8d7d284494b468be11c5e9934
diff --git a/web/dashboard_info.js b/web/dashboard_info.js
index 173e95bb..03b2a4ce 100644
--- a/web/dashboard_info.js
+++ b/web/dashboard_info.js
@@ -1,7 +1,9 @@
var netdataDashboard = window.netdataDashboard || {};
-// menu
+// ----------------------------------------------------------------------------
+// menus
+
// information about the main menus
netdataDashboard.menu = {
@@ -217,6 +219,12 @@ netdataDashboard.menu = {
info: undefined
},
+ '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.'
+ },
+
'named': {
title: 'named',
icon: '',
@@ -254,9 +262,31 @@ netdataDashboard.menu = {
}
};
-// submenu
+
+
+// ----------------------------------------------------------------------------
+// submenus
+
+// information to be shown, just below each submenu
+
// 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.'
+ },
+
+ '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).'
+ },
+
+ 'web_log.clients': {
+ info: 'Charts showing the number of unique client IPs, accessing the web server.'
+ },
+
+ 'web_log.timings': {
+ info: 'Web server response timings - the time the web server needed to prepare and respond to requests. This requires 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.'
+ },
+
'mem.ksm': {
title: 'Memory Deduper',
info: 'Kernel Same-page Merging (KSM) performance monitoring, read from several files in /sys/kernel/mm/ksm/. KSM is a memory-saving de-duplication feature in the Linux kernel (since version 2.6.32). The KSM daemon ksmd periodically scans those areas of user memory which have been registered with it, looking for pages of identical content which can be replaced by a single write-protected page (which is automatically copied if a process later wants to update its content). KSM was originally developed for use with KVM (where it was known as Kernel Shared Memory), to fit more virtual machines into physical memory, by sharing the data common between them. But it can be useful to any application which generates many instances of the same data.'
@@ -306,7 +336,11 @@ netdataDashboard.submenu = {
}
};
+
+
+// ----------------------------------------------------------------------------
// chart
+
// information works on the context of a chart
// Its purpose is to set:
//
@@ -811,6 +845,96 @@ netdataDashboard.context = {
'fping.packets': {
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).',
+
+ 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.detailed_response_codes': {
+ info: 'Number of responses for each response code.'
+ },
+
+ 'web_log.requests_per_ipproto': {
+ info: 'Web server requests received per IP protocol version.'
+ },
+
+ 'web_log.clients': {
+ info: 'Unique client IPs accessing the web server, within each data collection iteration. So, if data collection is per second, this chart shows unique client IPs per second.'
+ },
+
+ 'web_log.clients_all': {
+ info: 'Unique client IPs accessing the web server since the last restart of netdata. This plugin keeps in memory all the unique IPs that have accessed the web server. On very busy web servers (several millions of unique IPs) you may want to disable this chart (check /etc/netdata/python.d/web_log.conf).'
}
};