@cryptotaxi247 / netdata-1 / commits / 89059a7d8

charts can now have syncronized y-range; fixes #593

Costa Tsaousis (ktsaou) committed Oct 30, 2016 at 17:46 UTC 89059a7d848801a20154ab764c86b04c68d03ffd
10 files changed +1007 -779
web/dashboard.html
+1 -1
@@ -652,4 +652,4 @@ So, to avoid flashing the charts, we destroy and re-create the charts on each up
652 <!-- <script> netdataServer = "http://box:19999"; </script> -->
653
654 <!-- load the dashboard manager - it will do the rest -->
655 -<script type="text/javascript" src="dashboard.js?v20161030-10"></script>
655 +<script type="text/javascript" src="dashboard.js?v20161030-30"></script>
web/dashboard.js
+161 -12
@@ -660,6 +660,119 @@
660 NETDATA.errorLast.datetime = 0;
661 };
662
663 + // ----------------------------------------------------------------------------------------------------------------
664 + // commonMin & commonMax
665 +
666 + NETDATA.commonMin = {
667 + keys: {},
668 + latest: {},
669 +
670 + get: function(state) {
671 + if(typeof state.__commonMin === 'undefined') {
672 + // get the commonMin setting
673 + var self = $(state.element);
674 + state.__commonMin = self.data('common-min') || null;
675 + }
676 +
677 + var min = state.data.min;
678 + var name = state.__commonMin;
679 +
680 + if(name === null) {
681 + // we don't need commonMin
682 + //state.log('no need for commonMin');
683 + return min;
684 + }
685 +
686 + var t = this.keys[name];
687 + if(typeof t === 'undefined') {
688 + // add our commonMin
689 + this.keys[name] = {};
690 + t = this.keys[name];
691 + }
692 +
693 + var uuid = state.uuid;
694 + if(typeof t[uuid] !== 'undefined') {
695 + if(t[uuid] === min) {
696 + //state.log('commonMin ' + state.__commonMin + ' not changed: ' + this.latest[name]);
697 + return this.latest[name];
698 + }
699 + else if(min < this.latest[name]) {
700 + //state.log('commonMin ' + state.__commonMin + ' increased: ' + min);
701 + t[uuid] = min;
702 + this.latest[name] = min;
703 + return min;
704 + }
705 + }
706 +
707 + // add our min
708 + t[uuid] = min;
709 +
710 + // find the common min
711 + var m = min;
712 + for(var i in t)
713 + if(t[i] < m) m = t[i];
714 +
715 + //state.log('commonMin ' + state.__commonMin + ' updated: ' + m);
716 + this.latest[name] = m;
717 + return m;
718 + }
719 + };
720 +
721 + NETDATA.commonMax = {
722 + keys: {},
723 + latest: {},
724 +
725 + get: function(state) {
726 + if(typeof state.__commonMax === 'undefined') {
727 + // get the commonMax setting
728 + var self = $(state.element);
729 + state.__commonMax = self.data('common-max') || null;
730 + }
731 +
732 + var max = state.data.max;
733 + var name = state.__commonMax;
734 +
735 + if(name === null) {
736 + // we don't need commonMax
737 + //state.log('no need for commonMax');
738 + return max;
739 + }
740 +
741 + var t = this.keys[name];
742 + if(typeof t === 'undefined') {
743 + // add our commonMax
744 + this.keys[name] = {};
745 + t = this.keys[name];
746 + }
747 +
748 + var uuid = state.uuid;
749 + if(typeof t[uuid] !== 'undefined') {
750 + if(t[uuid] === max) {
751 + //state.log('commonMax ' + state.__commonMax + ' not changed: ' + this.latest[name]);
752 + return this.latest[name];
753 + }
754 + else if(max > this.latest[name]) {
755 + //state.log('commonMax ' + state.__commonMax + ' increased: ' + max);
756 + t[uuid] = max;
757 + this.latest[name] = max;
758 + return max;
759 + }
760 + }
761 +
762 + // add our max
763 + t[uuid] = max;
764 +
765 + // find the common max
766 + var m = max;
767 + for(var i in t)
768 + if(t[i] > m) m = t[i];
769 +
770 + //state.log('commonMax ' + state.__commonMax + ' updated: ' + m);
771 + this.latest[name] = m;
772 + return m;
773 + }
774 + };
775 +
776 // ----------------------------------------------------------------------------------------------------------------
777 // Chart Registry
778
@@ -3903,25 +4016,33 @@
4016 state.log('dygraphChartUpdate() forced zoom update');
4017
4018 options.dateWindow = (state.requested_padding !== null)?[ state.view_after, state.view_before ]:null;
3906 - options.valueRange = state.dygraph_options.valueRange;
4019 options.isZoomedIgnoreProgrammaticZoom = true;
4020 state.dygraph_force_zoom = false;
4021 }
4022 else if(state.current.name !== 'auto') {
4023 if(NETDATA.options.debug.dygraph === true || state.debug === true)
4024 state.log('dygraphChartUpdate() loose update');
3913 -
3914 - options.valueRange = state.dygraph_options.valueRange;
4025 }
4026 else {
4027 if(NETDATA.options.debug.dygraph === true || state.debug === true)
4028 state.log('dygraphChartUpdate() strict update');
4029
4030 options.dateWindow = (state.requested_padding !== null)?[ state.view_after, state.view_before ]:null;
3921 - options.valueRange = state.dygraph_options.valueRange;
4031 options.isZoomedIgnoreProgrammaticZoom = true;
4032 }
4033
4034 + options.valueRange = state.dygraph_options.valueRange;
4035 +
4036 + var oldMax = null, oldMin = null;
4037 + if(state.__commonMin !== null) {
4038 + state.data.min = state.dygraph_instance.axes_[0].extremeRange[0];
4039 + oldMin = options.valueRange[0] = NETDATA.commonMin.get(state);
4040 + }
4041 + if(state.__commonMax !== null) {
4042 + state.data.max = state.dygraph_instance.axes_[0].extremeRange[1];
4043 + oldMax = options.valueRange[1] = NETDATA.commonMax.get(state);
4044 + }
4045 +
4046 if(state.dygraph_smooth_eligible === true) {
4047 if((NETDATA.options.current.smooth_plot === true && state.dygraph_options.plotter !== smoothPlotter)
4048 || (NETDATA.options.current.smooth_plot === false && state.dygraph_options.plotter === smoothPlotter)) {
@@ -3932,6 +4053,23 @@
4053
4054 dygraph.updateOptions(options);
4055
4056 + var redraw = false;
4057 + if(oldMin !== null && oldMin > state.dygraph_instance.axes_[0].extremeRange[0]) {
4058 + state.data.min = state.dygraph_instance.axes_[0].extremeRange[0];
4059 + options.valueRange[0] = NETDATA.commonMin.get(state);
4060 + redraw = true;
4061 + }
4062 + if(oldMax !== null && oldMax < state.dygraph_instance.axes_[0].extremeRange[1]) {
4063 + state.data.max = state.dygraph_instance.axes_[0].extremeRange[1];
4064 + options.valueRange[1] = NETDATA.commonMax.get(state);
4065 + redraw = true;
4066 + }
4067 +
4068 + if(redraw === true) {
4069 + // state.log('forcing redraw to adapt to common- min/max');
4070 + dygraph.updateOptions(options);
4071 + }
4072 +
4073 state.dygraph_last_rendered = new Date().getTime();
4074 return true;
4075 };
@@ -3966,7 +4104,7 @@
4104 title: self.data('dygraph-title') || state.title,
4105 titleHeight: self.data('dygraph-titleheight') || 19,
4106
3969 - legend: self.data('dygraph-legend') || 'always', // 'onmouseover',
4107 + legend: self.data('dygraph-legend') || 'always', // we need this to get selection events
4108 labels: data.result.labels,
4109 labelsDiv: self.data('dygraph-labelsdiv') || state.element_legend_childs.hidden,
4110 labelsDivStyles: self.data('dygraph-labelsdivstyles') || { 'fontSize':'1px' },
@@ -3982,7 +4120,7 @@
4120 xRangePad: self.data('dygraph-xrangepad') || 0,
4121 yRangePad: self.data('dygraph-yrangepad') || 1,
4122
3985 - valueRange: self.data('dygraph-valuerange') || null,
4123 + valueRange: self.data('dygraph-valuerange') || [ null, null ],
4124
4125 ylabel: state.units,
4126 yLabelWidth: self.data('dygraph-ylabelwidth') || 12,
@@ -4422,6 +4560,17 @@
4560 state.dygraph_force_zoom = false;
4561 state.dygraph_user_action = false;
4562 state.dygraph_last_rendered = new Date().getTime();
4563 +
4564 + if(typeof state.dygraph_instance.axes_[0].extremeRange !== 'undefined') {
4565 + state.__commonMin = self.data('common-min') || null;
4566 + state.__commonMax = self.data('common-max') || null;
4567 + }
4568 + else {
4569 + state.log('incompatible version of dygraphs detected');
4570 + state.__commonMin = null;
4571 + state.__commonMax = null;
4572 + }
4573 +
4574 return true;
4575 };
4576
@@ -4922,7 +5071,7 @@
5071 }
5072
5073 var value = state.data.result[state.data.result.length - 1 - slot];
4925 - var max = (state.easyPieChartMax === null)?state.data.max:state.easyPieChartMax;
5074 + var max = (state.easyPieChartMax === null)?NETDATA.commonMax.get(state):state.easyPieChartMax;
5075 var pcent = NETDATA.percentFromValueMax(value, max);
5076
5077 state.easyPieChartEvent.value = value;
@@ -4951,7 +5100,7 @@
5100 }
5101 else {
5102 value = data.result[0];
4954 - max = (state.easyPieChartMax === null)?data.max:state.easyPieChartMax;
5103 + max = (state.easyPieChartMax === null)?NETDATA.commonMax.get(state):state.easyPieChartMax;
5104 pcent = NETDATA.percentFromValueMax(value, max);
5105 }
5106
@@ -4969,7 +5118,7 @@
5118 var adjust = self.data('easypiechart-adjust') || null;
5119
5120 if(max === null) {
4972 - max = data.max;
5121 + max = NETDATA.commonMax.get(state);
5122 state.easyPieChartMax = null;
5123 }
5124 else
@@ -5191,7 +5340,7 @@
5340 }
5341
5342 var value = state.data.result[state.data.result.length - 1 - slot];
5194 - var max = (state.gaugeMax === null)?state.data.max:state.gaugeMax;
5343 + var max = (state.gaugeMax === null)?NETDATA.commonMax.get(state):state.gaugeMax;
5344 var min = 0;
5345
5346 state.gaugeEvent.value = value;
@@ -5223,7 +5372,7 @@
5372 else {
5373 value = data.result[0];
5374 min = 0;
5226 - max = (state.gaugeMax === null)?data.max:state.gaugeMax;
5375 + max = (state.gaugeMax === null)?NETDATA.commonMax.get(state):state.gaugeMax;
5376 if(value > max) max = value;
5377 NETDATA.gaugeSetLabels(state, value, min, max);
5378 }
@@ -5246,7 +5395,7 @@
5395 var generateGradient = self.data('gauge-generate-gradient') || false;
5396
5397 if(max === null) {
5249 - max = data.max;
5398 + max = NETDATA.commonMax.get(state);
5399 state.gaugeMax = null;
5400 }
5401 else
web/dashboard_info.js
+757 -756
@@ -1,756 +1,757 @@
1 -
2 -var netdataDashboard = window.netdataDashboard || {};
3 -
4 -// menu
5 -// information about the main menus
6 -
7 -netdataDashboard.menu = {
8 - 'system': {
9 - title: 'System Overview',
10 - icon: '<i class="fa fa-bookmark" aria-hidden="true"></i>',
11 - info: 'Overview of the key system metrics.'
12 - },
13 -
14 - 'ap': {
15 - title: 'Access Points',
16 - icon: '<i class="fa fa-wifi" aria-hidden="true"></i>',
17 - info: undefined
18 - },
19 -
20 - 'tc': {
21 - title: 'Quality of Service',
22 - icon: '<i class="fa fa-globe" aria-hidden="true"></i>',
23 - info: 'Netdata collects and visualizes tc 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). Also, data collection may have a slight time difference compared to the interface (QoS data collection is implemented with a BASH script, so a shift in data collection of a few milliseconds should be justified).'
24 - },
25 -
26 - 'net': {
27 - title: 'Network Interfaces',
28 - icon: '<i class="fa fa-share-alt" aria-hidden="true"></i>',
29 - info: 'Per network interface statistics collected from <code>/proc/net/dev</code>.'
30 - },
31 -
32 - 'ipv4': {
33 - title: 'IPv4 Networking',
34 - icon: '<i class="fa fa-cloud" aria-hidden="true"></i>',
35 - info: undefined
36 - },
37 -
38 - 'ipv6': {
39 - title: 'IPv6 Networking',
40 - icon: '<i class="fa fa-cloud" aria-hidden="true"></i>',
41 - info: undefined
42 - },
43 -
44 - 'ipvs': {
45 - title: 'IP Virtual Server',
46 - icon: '<i class="fa fa-eye" aria-hidden="true"></i>',
47 - info: undefined
48 - },
49 -
50 - 'netfilter': {
51 - title: 'Firewall (netfilter)',
52 - icon: '<i class="fa fa-shield" aria-hidden="true"></i>',
53 - info: undefined
54 - },
55 -
56 - 'cpu': {
57 - title: 'CPUs',
58 - icon: '<i class="fa fa-bolt" aria-hidden="true"></i>',
59 - info: undefined
60 - },
61 -
62 - 'mem': {
63 - title: 'Memory',
64 - icon: '<i class="fa fa-bolt" aria-hidden="true"></i>',
65 - info: undefined
66 - },
67 -
68 - 'disk': {
69 - title: 'Disks',
70 - icon: '<i class="fa fa-folder" aria-hidden="true"></i>',
71 - info: 'Charts with performance information for all the system disks. Special care has been given to present disk performance metrics in a way compatible with <code>iostat -x</code>. netdata by default prevents rendering performance charts for individual partitions and unmounted virtual disks. Disabled charts can still be enabled by altering the relative settings in the netdata configuration file.'
72 - },
73 -
74 - 'sensors': {
75 - title: 'Sensors',
76 - icon: '<i class="fa fa-leaf" aria-hidden="true"></i>',
77 - info: undefined
78 - },
79 -
80 - 'nfsd': {
81 - title: 'NFS Server',
82 - icon: '<i class="fa fa-folder-open" aria-hidden="true"></i>',
83 - info: undefined
84 - },
85 -
86 - 'nfs': {
87 - title: 'NFS Client',
88 - icon: '<i class="fa fa-folder-open" aria-hidden="true"></i>',
89 - info: undefined
90 - },
91 -
92 - 'apps': {
93 - title: 'Applications',
94 - icon: '<i class="fa fa-heartbeat" aria-hidden="true"></i>',
95 - info: 'Per application statistics are collected using netdata\'s <code>apps.plugin</code>. This plugin walks through the entire <code>/proc</code> filesystem 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.',
96 - height: 1.5
97 - },
98 -
99 - 'users': {
100 - title: 'Users',
101 - icon: '<i class="fa fa-user" aria-hidden="true"></i>',
102 - info: 'Per user statistics are collected using netdata\'s <code>apps.plugin</code>. This plugin walks through the entire <code>/proc</code> filesystem and aggregates statistics per user. 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.',
103 - height: 1.5
104 - },
105 -
106 - 'groups': {
107 - title: 'User Groups',
108 - icon: '<i class="fa fa-users" aria-hidden="true"></i>',
109 - info: 'Per user group statistics are collected using netdata\'s <code>apps.plugin</code>. This plugin walks through the entire <code>/proc</code> filesystem and aggregates statistics per user group. 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.',
110 - height: 1.5
111 - },
112 -
113 - 'netdata': {
114 - title: 'Netdata Monitoring',
115 - icon: '<i class="fa fa-bar-chart" aria-hidden="true"></i>',
116 - info: undefined
117 - },
118 -
119 - 'example': {
120 - title: 'Example Charts',
121 - info: undefined
122 - },
123 -
124 - 'cgroup': {
125 - title: '',
126 - icon: '<i class="fa fa-th" aria-hidden="true"></i>',
127 - info: undefined
128 - },
129 -
130 - 'cgqemu': {
131 - title: '',
132 - icon: '<i class="fa fa-th-large" aria-hidden="true"></i>',
133 - info: undefined
134 - },
135 -
136 - 'fping': {
137 - title: 'fping',
138 - icon: '<i class="fa fa-exchange" aria-hidden="true"></i>',
139 - info: undefined
140 - },
141 -
142 - 'memcached': {
143 - title: 'memcached',
144 - icon: '<i class="fa fa-database" aria-hidden="true"></i>',
145 - info: undefined
146 - },
147 -
148 - 'mysql': {
149 - title: 'MySQL',
150 - icon: '<i class="fa fa-database" aria-hidden="true"></i>',
151 - info: undefined
152 - },
153 -
154 - 'postgres': {
155 - title: 'Postgres',
156 - icon: '<i class="fa fa-database" aria-hidden="true"></i>',
157 - info: undefined
158 - },
159 -
160 - 'redis': {
161 - title: 'Redis',
162 - icon: '<i class="fa fa-database" aria-hidden="true"></i>',
163 - info: undefined
164 - },
165 -
166 - 'retroshare': {
167 - title: 'RetroShare',
168 - icon: '<i class="fa fa-share-alt" aria-hidden="true"></i>',
169 - info: undefined
170 - },
171 -
172 - 'ipfs': {
173 - title: 'IPFS',
174 - icon: '<i class="fa fa-folder-open" aria-hidden="true"></i>',
175 - info: undefined
176 - },
177 -
178 - 'phpfpm': {
179 - title: 'PHP-FPM',
180 - icon: '<i class="fa fa-eye" aria-hidden="true"></i>',
181 - info: undefined,
182 - },
183 -
184 - 'postfix': {
185 - title: 'postfix',
186 - icon: '<i class="fa fa-envelope" aria-hidden="true"></i>',
187 - info: undefined,
188 - },
189 -
190 - 'nginx': {
191 - title: 'nginx',
192 - icon: '<i class="fa fa-eye" aria-hidden="true"></i>',
193 - info: undefined,
194 - },
195 -
196 - 'apache': {
197 - title: 'Apache',
198 - icon: '<i class="fa fa-eye" aria-hidden="true"></i>',
199 - info: undefined,
200 - },
201 -
202 - 'named': {
203 - title: 'named',
204 - icon: '<i class="fa fa-tag" aria-hidden="true"></i>',
205 - info: undefined
206 - },
207 -
208 - 'squid': {
209 - title: 'squid',
210 - icon: '<i class="fa fa-exchange" aria-hidden="true"></i>',
211 - info: undefined
212 - },
213 -
214 - 'nut': {
215 - title: 'UPS',
216 - icon: '<i class="fa fa-battery-half" aria-hidden="true"></i>',
217 - info: undefined
218 - },
219 -
220 - 'apcupsd': {
221 - title: 'UPS',
222 - icon: '<i class="fa fa-battery-half" aria-hidden="true"></i>',
223 - info: undefined
224 - },
225 -
226 - 'smawebbox': {
227 - title: 'Solar Power',
228 - icon: '<i class="fa fa-sun-o" aria-hidden="true"></i>',
229 - info: undefined
230 - },
231 -
232 - 'snmp': {
233 - title: 'SNMP',
234 - icon: '<i class="fa fa-random" aria-hidden="true"></i>',
235 - info: undefined
236 - }
237 -};
238 -
239 -// submenu
240 -// information about the submenus
241 -netdataDashboard.submenu = {
242 - 'mem.ksm': {
243 - title: 'Memory Deduper',
244 - info: 'Kernel Same-page Merging (KSM) performance monitoring, read from several files in <code>/sys/kernel/mm/ksm/</code>. 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.'
245 - },
246 -
247 - 'ipv4.ecn': {
248 - 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.'
249 - },
250 -
251 - 'netfilter.conntrack': {
252 - title: 'Connection Tracker',
253 - info: 'Netfilter Connection Tracker performance monitoring, read from <code>/proc/net/stat/nf_conntrack</code>. The connection tracker keeps track of all connections of the machine, inbound and outbound. It works by keeping a database with all open connections, tracking network and address translation and connection expectations.'
254 - },
255 -
256 - 'netfilter.nfacct': {
257 - title: 'Bandwidth Accounting',
258 - info: 'The following information is read using the <code>nfacct.plugin</code>.'
259 - },
260 -
261 - 'netfilter.synproxy': {
262 - title: 'DDoS Protection',
263 - info: 'DDoS Protection performance monitoring read from <code>/proc/net/stat/synproxy</code>. <a href="https://github.com/firehol/firehol/wiki/Working-with-SYNPROXY" target="_blank">SYNPROXY</a> is a TCP SYN packets proxy. It is used to protect any TCP server (like a web server) from SYN floods and similar DDoS attacks. It is a netfilter module, in the Linux kernel (since version 3.12). It is optimized to handle millions of packets per second utilizing all CPUs available without any concurrency locking between the connections. It can be used for any kind of TCP traffic (even encrypted), since it does not interfere with the content itself.'
264 - },
265 -
266 - 'system.softnet_stat': {
267 - title: 'softnet',
268 - info: 'Statistics for CPUs SoftIRQs related to network receive work, read from <code>/proc/net/softnet_stat</code>. Break down per CPU core can be found at <a href="#cpu_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 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 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>.'
269 - },
270 -
271 - 'cpu.softnet_stat': {
272 - title: 'softnet',
273 - info: 'Statistics for per CPUs core SoftIRQs related to network receive work, read from <code>/proc/net/softnet_stat</code>. Total for all CPU cores can be found at <a href="#system_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 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 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>.'
274 - }
275 -};
276 -
277 -// chart
278 -// information works on the context of a chart
279 -// Its purpose is to set:
280 -//
281 -// info: the text above the charts
282 -// heads: the representation of the chart at the top the subsection (second level menu)
283 -// mainheads: the representation of the chart at the top of the section (first level menu)
284 -// colors: the dimension colors of the chart (the default colors are appended)
285 -// height: the ratio of the chart height relative to the default
286 -//
287 -netdataDashboard.context = {
288 - 'system.cpu': {
289 - info: '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="#cpu">CPUs</a> section and per application usage at the <a href="#apps">Applications Monitoring</a> section.<br/>Keep an eye on <b>iowait</b> ' + sparkline('system.cpu', 'iowait', '%') + '. If it is constantly high, your disks are a bottleneck and they slow your system down.<br/>Another important metric worth monitoring, is <b>softirq</b> ' + sparkline('system.cpu', 'softirq', '%') + '. A constantly high percentage of softirq may indicate network drivers issues.'
290 - },
291 -
292 - 'system.load': {
293 - info: 'Current system load, i.e. the number of processes using CPU or waiting for system resources (usually CPU and disk). The 3 metrics refer to 1, 5 and 15 minute averages. Linux calculates this once every 5 seconds. Netdata reads them from <code>/proc/loadavg</code>. For more information check <a href="https://en.wikipedia.org/wiki/Load_(computing)" target="_blank">this wikipedia article</a>',
294 - height: 0.7
295 - },
296 -
297 - 'system.io': {
298 - info: 'Total Disk I/O, for all disks, read from <code>/proc/vmstat</code>. You can get detailed information about each disk at the <a href="#disk">Disks</a> section and per application Disk usage at the <a href="#apps">Applications Monitoring</a> section.'
299 - },
300 -
301 - 'system.swapio': {
302 - info: 'Total Swap I/O, read from <code>/proc/vmstat</code>. (netdata measures both <code>in</code> and <code>out</code>. If either of them is not shown in the chart, it is because it is zero - you can change the page settings to always render all the available dimensions on all charts).'
303 - },
304 -
305 - 'system.pgfaults': {
306 - info: 'Total page faults, read from <code>/proc/vmstat</code>. <b>Major page faults</b> indicates that the system is using its swap. You can find which applications use the swap at the <a href="#apps">Applications Monitoring</a> section.'
307 - },
308 -
309 - 'system.entropy': {
310 - colors: '#CC22AA',
311 - info: '<a href="https://en.wikipedia.org/wiki/Entropy_(computing)" target="_blank">Entropy</a>, read from <code>/proc/sys/kernel/random/entropy_avail</code>, is like a pool of random numbers (<a href="https://en.wikipedia.org/wiki//dev/random" target="_blank">/dev/random</a>) that are mainly used in cryptography. It is advised that the pool remains always <a href="https://blog.cloudflare.com/ensuring-randomness-with-linuxs-random-number-generator/" target="_blank">above 200</a>. If the pool of entropy gets empty, you risk your security to be predictable and you should install a user-space random numbers generating daemon, like <a href="http://www.issihosts.com/haveged/" target="_blank">haveged</a> or <code>rng-tools</code> (i.e. <b>rngd</b>), to keep the pool in healthy levels.'
312 - },
313 -
314 - 'system.forks': {
315 - colors: '#5555DD',
316 - info: 'The number of new processes created per second, read from <code>/proc/stat</code>.'
317 - },
318 -
319 - 'system.intr': {
320 - colors: '#DD5555',
321 - info: 'Total number of CPU interrupts, read from <code>/proc/stat</code>. Check <code>system.interrupts</code> that gives more detail about each interrupt and also the <a href="#cpu">CPUs</a> section where interrupts are analyzed per CPU core.'
322 - },
323 -
324 - 'system.interrupts': {
325 - info: 'CPU interrupts in detail, read from <code>/proc/interrupts</code>. At the <a href="#cpu">CPUs</a> section, interrupts are analyzed per CPU core.'
326 - },
327 -
328 - 'system.softirqs': {
329 - info: 'CPU softirqs in detail, read from <code>/proc/softirqs</code>. At the <a href="#cpu">CPUs</a> section, softirqs are analyzed per CPU core.'
330 - },
331 -
332 - 'system.processes': {
333 - info: 'System processes, read from <code>/proc/stat</code>. <b>Running</b> are the processes in the CPU. <b>Blocked</b> are processes that are willing to enter the CPU, but they cannot, e.g. because they wait for disk activity.'
334 - },
335 -
336 - 'system.active_processes': {
337 - info: 'All system processes, read from <code>/proc/loadavg</code>.'
338 - },
339 -
340 - 'system.ctxt': {
341 - info: '<a href="https://en.wikipedia.org/wiki/Context_switch" target="_blank">Context Switches</a>, read from <code>/proc/stat</code>, is the switching of the CPU from one process, task or thread to another. If there are many processes or threads willing to execute and very few CPU cores available to handle them, the system is making more context switching to balance the CPU resources among them. The whole process is computationally intensive. The more the context switches, the slower the system gets.'
342 - },
343 -
344 - 'system.idlejitter': {
345 - colors: '#5555AA',
346 - info: 'Idle jitter is calculated by netdata. A thread is spawned that requests to sleep for a few microseconds. When the system wakes it up, it measures how many microseconds have passed. The difference between the requested and the actual duration of the sleep, is the <b>idle jitter</b>. This number is useful in real-time environments, where CPU jitter can affect the quality of the service (like VoIP media gateways).'
347 - },
348 -
349 - 'system.ipv4': {
350 - info: 'Total IPv4 Traffic, read from <code>/proc/net/netstat</code>.'
351 - },
352 -
353 - 'system.ipv6': {
354 - info: 'Total IPv6 Traffic, read from <code>/proc/net/snmp6</code>.'
355 - },
356 -
357 - 'system.ram': {
358 - info: 'System memory, read from <code>/proc/meminfo</code>.'
359 - },
360 -
361 - 'system.swap': {
362 - info: 'System swap memory, read from <code>/proc/meminfo</code>.'
363 - },
364 -
365 - // ------------------------------------------------------------------------
366 - // MEMORY
367 -
368 - 'mem.ksm_savings': {
369 - heads: [
370 - netdataDashboard.gaugeChart('Saved', '12%', 'savings', '#0099CC')
371 - ]
372 - },
373 -
374 - 'mem.ksm_ratios': {
375 - heads: [
376 - function(id) {
377 - return '<div data-netdata="' + id + '"'
378 - + ' data-gauge-max-value="100"'
379 - + ' data-chart-library="gauge"'
380 - + ' data-title="Savings"'
381 - + ' data-units="percentage %"'
382 - + ' data-gauge-adjust="width"'
383 - + ' data-width="12%"'
384 - + ' data-before="0"'
385 - + ' data-after="-CHART_DURATION"'
386 - + ' data-points="CHART_DURATION"'
387 - + ' role="application"></div>';
388 - }
389 - ]
390 - },
391 -
392 - 'mem.committed': {
393 - colors: NETDATA.colors[3]
394 - },
395 -
396 - // ------------------------------------------------------------------------
397 - // network interfaces
398 -
399 - 'net.drops': {
400 - info: 'Packets that have been dropped at the network interface level. These are the same counters reported by <code>ifconfig</code> as <code>RX dropped</code> (inbound) and <code>TX dropped</code> (outbound). <b>inbound</b> packets can be dropped at the network interface level due to <a href="#system_softnet_stat">softnet backlog</a> overflow, bad / unintented VLAN tags, unknown or unregistered protocols, IPv6 frames when the server is not configured for IPv6. Check <a href="https://www.novell.com/support/kb/doc.php?id=7007165" target="_blank">this document</a> for more information.'
401 - },
402 -
403 - // ------------------------------------------------------------------------
404 - // IPv4
405 -
406 - 'ipv4.tcpmemorypressures': {
407 - 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).'
408 - },
409 -
410 - 'ipv4.tcpconnaborts': {
411 - 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.'
412 - },
413 -
414 - // ------------------------------------------------------------------------
415 - // APPS
416 -
417 - 'apps.cpu': {
418 - height: 2.0
419 - },
420 -
421 - 'apps.mem': {
422 - info: 'Real memory (RAM) used by applications. This does not include shared memory.'
423 - },
424 -
425 - 'apps.vmem': {
426 - 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.'
427 - },
428 -
429 - 'apps.preads': {
430 - height: 2.0
431 - },
432 -
433 - 'apps.pwrites': {
434 - height: 2.0
435 - },
436 -
437 - // ------------------------------------------------------------------------
438 - // USERS
439 -
440 - 'users.cpu': {
441 - height: 2.0
442 - },
443 -
444 - 'users.mem': {
445 - info: 'Real memory (RAM) used per user. This does not include shared memory.'
446 - },
447 -
448 - 'users.vmem': {
449 - 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.'
450 - },
451 -
452 - 'users.preads': {
453 - height: 2.0
454 - },
455 -
456 - 'users.pwrites': {
457 - height: 2.0
458 - },
459 -
460 - // ------------------------------------------------------------------------
461 - // GROUPS
462 -
463 - 'groups.cpu': {
464 - height: 2.0
465 - },
466 -
467 - 'groups.mem': {
468 - info: 'Real memory (RAM) used per user group. This does not include shared memory.'
469 - },
470 -
471 - 'groups.vmem': {
472 - 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.'
473 - },
474 -
475 - 'groups.preads': {
476 - height: 2.0
477 - },
478 -
479 - 'groups.pwrites': {
480 - height: 2.0
481 - },
482 -
483 - // ------------------------------------------------------------------------
484 - // NETWORK QoS
485 -
486 - 'tc.qos': {
487 - heads: [
488 - function(id) {
489 - if(id.match(/.*-ifb$/))
490 - return netdataDashboard.gaugeChart('Inbound', '12%', '', '#5555AA');
491 - else
492 - return netdataDashboard.gaugeChart('Outbound', '12%', '', '#AA9900');
493 - }
494 - ]
495 - },
496 -
497 - // ------------------------------------------------------------------------
498 - // NETWORK INTERFACES
499 -
500 - 'net.net': {
501 - heads: [
502 - netdataDashboard.gaugeChart('Received', '12%', 'received'),
503 - netdataDashboard.gaugeChart('Sent', '12%', 'sent')
504 - ]
505 - },
506 -
507 - // ------------------------------------------------------------------------
508 - // NETFILTER
509 -
510 - 'netfilter.sockets': {
511 - colors: '#88AA00',
512 - heads: [
513 - netdataDashboard.gaugeChart('Active Connections', '12%', '', '#88AA00')
514 - ]
515 - },
516 -
517 - 'netfilter.new': {
518 - heads: [
519 - netdataDashboard.gaugeChart('New Connections', '12%', 'new', '#5555AA')
520 - ]
521 - },
522 -
523 - // ------------------------------------------------------------------------
524 - // DISKS
525 -
526 - 'disk.util': {
527 - colors: '#FF5588',
528 - heads: [
529 - netdataDashboard.gaugeChart('Utilization', '12%', '', '#FF5588')
530 - ],
531 - info: 'Disk Utilization measures the amount of time the disk was busy with something. This is not related to its performance. 100% means that the Linux kernel always had an outstanding operation on the disk. Keep in mind that depending on the underlying technology of the disk, 100% here may or may not be an indication of congestion.'
532 - },
533 -
534 - 'disk.backlog': {
535 - colors: '#0099CC',
536 - info: 'Backlog is an indication of the duration of pending disk operations. On every I/O event the Linux kernel is multiplying the time spent doing I/O since the last update of this field with the number of pending operations. While not accurate, this metric can provide an indication of the expected completion time of the operations in progress.'
537 - },
538 -
539 - 'disk.io': {
540 - heads: [
541 - netdataDashboard.gaugeChart('Read', '12%', 'reads'),
542 - netdataDashboard.gaugeChart('Write', '12%', 'writes')
543 - ],
544 - info: 'Amount of data transferred to and from disk.'
545 - },
546 -
547 - 'disk.ops': {
548 - info: 'Completed disk I/O operations. Keep in mind the number of operations requested might be higher, since the Linux kernel is able to merge adjacent to each other (see merged operations chart).'
549 - },
550 -
551 - 'disk.qops': {
552 - info: 'I/O operations currently in progress. This metric is a snapshot - it is not an average over the last interval.'
553 - },
554 -
555 - 'disk.iotime': {
556 - height: 0.5,
557 - info: 'The sum of the duration of all completed I/O operations. This number can exceed the interval if the disk is able to execute I/O operations in parallel.'
558 - },
559 - 'disk.mops': {
560 - height: 0.5,
561 - info: 'The number of merged disk operations. The Linux kernel is able to merge adjacent I/O operations, for example two 4KB reads can become one 8KB read before given to disk.'
562 - },
563 - 'disk.svctm': {
564 - height: 0.5,
565 - info: 'The average service time for completed I/O operations. This metric is calculated using the total busy time of the disk and the number of completed operations. If the disk is able to execute multiple parallel operations the reporting average service time will be misleading.'
566 - },
567 - 'disk.avgsz': {
568 - height: 0.5,
569 - info: 'The average I/O operation size.'
570 - },
571 - 'disk.await': {
572 - height: 0.5,
573 - info: 'The average time for I/O requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them.'
574 - },
575 -
576 - 'disk.space': {
577 - info: 'Disk space utilization. reserved for root is automatically reserved by the system to prevent the root user from getting out of space.'
578 - },
579 - 'disk.inodes': {
580 - info: 'inodes (or index nodes) are filesystem objects (e.g. files and directories). On many types of file system implementations, the maximum number of inodes is fixed at filesystem creation, limiting the maximum number of files the filesystem can hold. It is possible for a device to run out of inodes. When this happens, new files cannot be created on the device, even though there may be free space available.'
581 - },
582 -
583 - 'mysql.net': {
584 - info: 'The amount of data sent to mysql clients (<strong>out</strong>) and received from mysql clients (<strong>in</strong>).'
585 - },
586 -
587 - // ------------------------------------------------------------------------
588 - // MYSQL
589 -
590 - 'mysql.queries': {
591 - info: 'The number of statements executed by the server.<ul>' +
592 - '<li><strong>queries</strong> counts the statements executed within stored SQL programs.</li>' +
593 - '<li><strong>questions</strong> counts the statements sent to the mysql server by mysql clients.</li>' +
594 - '<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.' +
595 - ' 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>' +
596 - '</ul>'
597 - },
598 -
599 - 'mysql.handlers': {
600 - info: 'Usage of the internal handlers of mysql. This chart provides very good insights of what the mysql server is actually doing.' +
601 - ' (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>' +
602 - '<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>' +
603 - '<li><strong>delete</strong>, the number of times that rows have been deleted from tables.</li>' +
604 - '<li><strong>prepare</strong>, a counter for the prepare phase of two-phase commit operations.</li>' +
605 - '<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>' +
606 - '<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>' +
607 - '<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>' +
608 - '<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>' +
609 - '<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>' +
610 - '<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>' +
611 - '<li><strong>rollback</strong>, the number of requests for a storage engine to perform a rollback operation.</li>' +
612 - '<li><strong>savepoint</strong>, the number of requests for a storage engine to place a savepoint.</li>' +
613 - '<li><strong>savepoint rollback</strong>, the number of requests for a storage engine to roll back to a savepoint.</li>' +
614 - '<li><strong>update</strong>, the number of requests to update a row in a table.</li>' +
615 - '<li><strong>write</strong>, the number of requests to insert a row in a table.</li>' +
616 - '</ul>'
617 - },
618 -
619 - 'mysql.table_locks': {
620 - info: 'MySQL table locks counters: <ul>' +
621 - '<li><strong>immediate</strong>, the number of times that a request for a table lock could be granted immediately.</li>' +
622 - '<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>' +
623 - '</ul>'
624 - },
625 -
626 - // ------------------------------------------------------------------------
627 - // APACHE
628 -
629 - 'apache.connections': {
630 - colors: NETDATA.colors[4],
631 - mainheads: [
632 - netdataDashboard.gaugeChart('Connections', '12%', '', NETDATA.colors[4])
633 - ]
634 - },
635 -
636 - 'apache.requests': {
637 - colors: NETDATA.colors[0],
638 - mainheads: [
639 - netdataDashboard.gaugeChart('Requests', '12%', '', NETDATA.colors[0])
640 - ]
641 - },
642 -
643 - 'apache.net': {
644 - colors: NETDATA.colors[3],
645 - mainheads: [
646 - netdataDashboard.gaugeChart('Bandwidth', '12%', '', NETDATA.colors[3])
647 - ]
648 - },
649 -
650 - 'apache.workers': {
651 - mainheads: [
652 - function(id) {
653 - return '<div data-netdata="' + id + '"'
654 - + ' data-dimensions="busy"'
655 - + ' data-append-options="percentage"'
656 - + ' data-gauge-max-value="100"'
657 - + ' data-chart-library="gauge"'
658 - + ' data-title="Workers Utilization"'
659 - + ' data-units="percentage %"'
660 - + ' data-gauge-adjust="width"'
661 - + ' data-width="12%"'
662 - + ' data-before="0"'
663 - + ' data-after="-CHART_DURATION"'
664 - + ' data-points="CHART_DURATION"'
665 - + ' role="application"></div>';
666 - }
667 - ]
668 - },
669 -
670 - 'apache.bytesperreq': {
671 - colors: NETDATA.colors[3],
672 - height: 0.5
673 - },
674 -
675 - 'apache.reqpersec': {
676 - colors: NETDATA.colors[4],
677 - height: 0.5
678 - },
679 -
680 - 'apache.bytespersec': {
681 - colors: NETDATA.colors[6],
682 - height: 0.5
683 - },
684 -
685 -
686 - // ------------------------------------------------------------------------
687 - // NGINX
688 -
689 - 'nginx.connections': {
690 - colors: NETDATA.colors[4],
691 - mainheads: [
692 - netdataDashboard.gaugeChart('Connections', '12%', '', NETDATA.colors[4])
693 - ]
694 - },
695 -
696 - 'nginx.requests': {
697 - colors: NETDATA.colors[0],
698 - mainheads: [
699 - netdataDashboard.gaugeChart('Requests', '12%', '', NETDATA.colors[0])
700 - ]
701 - },
702 -
703 - // ------------------------------------------------------------------------
704 - // NETDATA
705 -
706 - 'netdata.response_time': {
707 - info: 'The netdata API response time measures the time netdata needed to serve requests. This time includes everything, from the reception of the first byte of a request, to the dispatch of the last byte of its reply, therefore it includes all network latencies involved (i.e. a client over a slow network will influence these metrics).'
708 - },
709 -
710 - // ------------------------------------------------------------------------
711 - // RETROSHARE
712 -
713 - 'retroshare.bandwidth': {
714 - info: 'RetroShare inbound and outbound traffic.',
715 - mainheads: [
716 - netdataDashboard.gaugeChart('Received', '12%', 'bandwidth_down_kb'),
717 - netdataDashboard.gaugeChart('Sent', '12%', 'bandwidth_up_kb')
718 - ]
719 - },
720 -
721 - 'retroshare.peers': {
722 - info: 'Number of (connected) RetroShare friends.',
723 - mainheads: [
724 - function(id) {
725 - return '<div data-netdata="' + id + '"'
726 - + ' data-dimensions="peers_connected"'
727 - + ' data-append-options="friends"'
728 - + ' data-chart-library="easypiechart"'
729 - + ' data-title="connected friends"'
730 - + ' data-units=""'
731 - + ' data-width="8%"'
732 - + ' data-before="0"'
733 - + ' data-after="-CHART_DURATION"'
734 - + ' data-points="CHART_DURATION"'
735 - + ' role="application"></div>';
736 - }
737 - ]
738 - },
739 -
740 - 'retroshare.dht': {
741 - info: 'Statistics about RetroShare\'s DHT. These values are estimated!'
742 - },
743 -
744 - // ------------------------------------------------------------------------
745 - // fping
746 -
747 - 'fping.loss': {
748 - colors: NETDATA.colors[1],
749 - height: 0.5
750 - },
751 -
752 - 'fping.packets': {
753 - height: 0.5
754 - }
755 -
756 -};
1 +
2 +var netdataDashboard = window.netdataDashboard || {};
3 +
4 +// menu
5 +// information about the main menus
6 +
7 +netdataDashboard.menu = {
8 + 'system': {
9 + title: 'System Overview',
10 + icon: '<i class="fa fa-bookmark" aria-hidden="true"></i>',
11 + info: 'Overview of the key system metrics.'
12 + },
13 +
14 + 'ap': {
15 + title: 'Access Points',
16 + icon: '<i class="fa fa-wifi" aria-hidden="true"></i>',
17 + info: undefined
18 + },
19 +
20 + 'tc': {
21 + title: 'Quality of Service',
22 + icon: '<i class="fa fa-globe" aria-hidden="true"></i>',
23 + info: 'Netdata collects and visualizes tc 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). Also, data collection may have a slight time difference compared to the interface (QoS data collection is implemented with a BASH script, so a shift in data collection of a few milliseconds should be justified).'
24 + },
25 +
26 + 'net': {
27 + title: 'Network Interfaces',
28 + icon: '<i class="fa fa-share-alt" aria-hidden="true"></i>',
29 + info: 'Per network interface statistics collected from <code>/proc/net/dev</code>.'
30 + },
31 +
32 + 'ipv4': {
33 + title: 'IPv4 Networking',
34 + icon: '<i class="fa fa-cloud" aria-hidden="true"></i>',
35 + info: undefined
36 + },
37 +
38 + 'ipv6': {
39 + title: 'IPv6 Networking',
40 + icon: '<i class="fa fa-cloud" aria-hidden="true"></i>',
41 + info: undefined
42 + },
43 +
44 + 'ipvs': {
45 + title: 'IP Virtual Server',
46 + icon: '<i class="fa fa-eye" aria-hidden="true"></i>',
47 + info: undefined
48 + },
49 +
50 + 'netfilter': {
51 + title: 'Firewall (netfilter)',
52 + icon: '<i class="fa fa-shield" aria-hidden="true"></i>',
53 + info: undefined
54 + },
55 +
56 + 'cpu': {
57 + title: 'CPUs',
58 + icon: '<i class="fa fa-bolt" aria-hidden="true"></i>',
59 + info: undefined
60 + },
61 +
62 + 'mem': {
63 + title: 'Memory',
64 + icon: '<i class="fa fa-bolt" aria-hidden="true"></i>',
65 + info: undefined
66 + },
67 +
68 + 'disk': {
69 + title: 'Disks',
70 + icon: '<i class="fa fa-folder" aria-hidden="true"></i>',
71 + info: 'Charts with performance information for all the system disks. Special care has been given to present disk performance metrics in a way compatible with <code>iostat -x</code>. netdata by default prevents rendering performance charts for individual partitions and unmounted virtual disks. Disabled charts can still be enabled by altering the relative settings in the netdata configuration file.'
72 + },
73 +
74 + 'sensors': {
75 + title: 'Sensors',
76 + icon: '<i class="fa fa-leaf" aria-hidden="true"></i>',
77 + info: undefined
78 + },
79 +
80 + 'nfsd': {
81 + title: 'NFS Server',
82 + icon: '<i class="fa fa-folder-open" aria-hidden="true"></i>',
83 + info: undefined
84 + },
85 +
86 + 'nfs': {
87 + title: 'NFS Client',
88 + icon: '<i class="fa fa-folder-open" aria-hidden="true"></i>',
89 + info: undefined
90 + },
91 +
92 + 'apps': {
93 + title: 'Applications',
94 + icon: '<i class="fa fa-heartbeat" aria-hidden="true"></i>',
95 + info: 'Per application statistics are collected using netdata\'s <code>apps.plugin</code>. This plugin walks through the entire <code>/proc</code> filesystem 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.',
96 + height: 1.5
97 + },
98 +
99 + 'users': {
100 + title: 'Users',
101 + icon: '<i class="fa fa-user" aria-hidden="true"></i>',
102 + info: 'Per user statistics are collected using netdata\'s <code>apps.plugin</code>. This plugin walks through the entire <code>/proc</code> filesystem and aggregates statistics per user. 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.',
103 + height: 1.5
104 + },
105 +
106 + 'groups': {
107 + title: 'User Groups',
108 + icon: '<i class="fa fa-users" aria-hidden="true"></i>',
109 + info: 'Per user group statistics are collected using netdata\'s <code>apps.plugin</code>. This plugin walks through the entire <code>/proc</code> filesystem and aggregates statistics per user group. 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.',
110 + height: 1.5
111 + },
112 +
113 + 'netdata': {
114 + title: 'Netdata Monitoring',
115 + icon: '<i class="fa fa-bar-chart" aria-hidden="true"></i>',
116 + info: undefined
117 + },
118 +
119 + 'example': {
120 + title: 'Example Charts',
121 + info: undefined
122 + },
123 +
124 + 'cgroup': {
125 + title: '',
126 + icon: '<i class="fa fa-th" aria-hidden="true"></i>',
127 + info: undefined
128 + },
129 +
130 + 'cgqemu': {
131 + title: '',
132 + icon: '<i class="fa fa-th-large" aria-hidden="true"></i>',
133 + info: undefined
134 + },
135 +
136 + 'fping': {
137 + title: 'fping',
138 + icon: '<i class="fa fa-exchange" aria-hidden="true"></i>',
139 + info: undefined
140 + },
141 +
142 + 'memcached': {
143 + title: 'memcached',
144 + icon: '<i class="fa fa-database" aria-hidden="true"></i>',
145 + info: undefined
146 + },
147 +
148 + 'mysql': {
149 + title: 'MySQL',
150 + icon: '<i class="fa fa-database" aria-hidden="true"></i>',
151 + info: undefined
152 + },
153 +
154 + 'postgres': {
155 + title: 'Postgres',
156 + icon: '<i class="fa fa-database" aria-hidden="true"></i>',
157 + info: undefined
158 + },
159 +
160 + 'redis': {
161 + title: 'Redis',
162 + icon: '<i class="fa fa-database" aria-hidden="true"></i>',
163 + info: undefined
164 + },
165 +
166 + 'retroshare': {
167 + title: 'RetroShare',
168 + icon: '<i class="fa fa-share-alt" aria-hidden="true"></i>',
169 + info: undefined
170 + },
171 +
172 + 'ipfs': {
173 + title: 'IPFS',
174 + icon: '<i class="fa fa-folder-open" aria-hidden="true"></i>',
175 + info: undefined
176 + },
177 +
178 + 'phpfpm': {
179 + title: 'PHP-FPM',
180 + icon: '<i class="fa fa-eye" aria-hidden="true"></i>',
181 + info: undefined,
182 + },
183 +
184 + 'postfix': {
185 + title: 'postfix',
186 + icon: '<i class="fa fa-envelope" aria-hidden="true"></i>',
187 + info: undefined,
188 + },
189 +
190 + 'nginx': {
191 + title: 'nginx',
192 + icon: '<i class="fa fa-eye" aria-hidden="true"></i>',
193 + info: undefined,
194 + },
195 +
196 + 'apache': {
197 + title: 'Apache',
198 + icon: '<i class="fa fa-eye" aria-hidden="true"></i>',
199 + info: undefined,
200 + },
201 +
202 + 'named': {
203 + title: 'named',
204 + icon: '<i class="fa fa-tag" aria-hidden="true"></i>',
205 + info: undefined
206 + },
207 +
208 + 'squid': {
209 + title: 'squid',
210 + icon: '<i class="fa fa-exchange" aria-hidden="true"></i>',
211 + info: undefined
212 + },
213 +
214 + 'nut': {
215 + title: 'UPS',
216 + icon: '<i class="fa fa-battery-half" aria-hidden="true"></i>',
217 + info: undefined
218 + },
219 +
220 + 'apcupsd': {
221 + title: 'UPS',
222 + icon: '<i class="fa fa-battery-half" aria-hidden="true"></i>',
223 + info: undefined
224 + },
225 +
226 + 'smawebbox': {
227 + title: 'Solar Power',
228 + icon: '<i class="fa fa-sun-o" aria-hidden="true"></i>',
229 + info: undefined
230 + },
231 +
232 + 'snmp': {
233 + title: 'SNMP',
234 + icon: '<i class="fa fa-random" aria-hidden="true"></i>',
235 + info: undefined
236 + }
237 +};
238 +
239 +// submenu
240 +// information about the submenus
241 +netdataDashboard.submenu = {
242 + 'mem.ksm': {
243 + title: 'Memory Deduper',
244 + info: 'Kernel Same-page Merging (KSM) performance monitoring, read from several files in <code>/sys/kernel/mm/ksm/</code>. 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.'
245 + },
246 +
247 + 'ipv4.ecn': {
248 + 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.'
249 + },
250 +
251 + 'netfilter.conntrack': {
252 + title: 'Connection Tracker',
253 + info: 'Netfilter Connection Tracker performance monitoring, read from <code>/proc/net/stat/nf_conntrack</code>. The connection tracker keeps track of all connections of the machine, inbound and outbound. It works by keeping a database with all open connections, tracking network and address translation and connection expectations.'
254 + },
255 +
256 + 'netfilter.nfacct': {
257 + title: 'Bandwidth Accounting',
258 + info: 'The following information is read using the <code>nfacct.plugin</code>.'
259 + },
260 +
261 + 'netfilter.synproxy': {
262 + title: 'DDoS Protection',
263 + info: 'DDoS Protection performance monitoring read from <code>/proc/net/stat/synproxy</code>. <a href="https://github.com/firehol/firehol/wiki/Working-with-SYNPROXY" target="_blank">SYNPROXY</a> is a TCP SYN packets proxy. It is used to protect any TCP server (like a web server) from SYN floods and similar DDoS attacks. It is a netfilter module, in the Linux kernel (since version 3.12). It is optimized to handle millions of packets per second utilizing all CPUs available without any concurrency locking between the connections. It can be used for any kind of TCP traffic (even encrypted), since it does not interfere with the content itself.'
264 + },
265 +
266 + 'system.softnet_stat': {
267 + title: 'softnet',
268 + info: 'Statistics for CPUs SoftIRQs related to network receive work, read from <code>/proc/net/softnet_stat</code>. Break down per CPU core can be found at <a href="#cpu_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 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 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>.'
269 + },
270 +
271 + 'cpu.softnet_stat': {
272 + title: 'softnet',
273 + info: 'Statistics for per CPUs core SoftIRQs related to network receive work, read from <code>/proc/net/softnet_stat</code>. Total for all CPU cores can be found at <a href="#system_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 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 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>.'
274 + }
275 +};
276 +
277 +// chart
278 +// information works on the context of a chart
279 +// Its purpose is to set:
280 +//
281 +// info: the text above the charts
282 +// heads: the representation of the chart at the top the subsection (second level menu)
283 +// mainheads: the representation of the chart at the top of the section (first level menu)
284 +// colors: the dimension colors of the chart (the default colors are appended)
285 +// height: the ratio of the chart height relative to the default
286 +//
287 +netdataDashboard.context = {
288 + 'system.cpu': {
289 + info: '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="#cpu">CPUs</a> section and per application usage at the <a href="#apps">Applications Monitoring</a> section.<br/>Keep an eye on <b>iowait</b> ' + sparkline('system.cpu', 'iowait', '%') + '. If it is constantly high, your disks are a bottleneck and they slow your system down.<br/>Another important metric worth monitoring, is <b>softirq</b> ' + sparkline('system.cpu', 'softirq', '%') + '. A constantly high percentage of softirq may indicate network drivers issues.',
290 + valueRange: "[0, 100]"
291 + },
292 +
293 + 'system.load': {
294 + info: 'Current system load, i.e. the number of processes using CPU or waiting for system resources (usually CPU and disk). The 3 metrics refer to 1, 5 and 15 minute averages. Linux calculates this once every 5 seconds. Netdata reads them from <code>/proc/loadavg</code>. For more information check <a href="https://en.wikipedia.org/wiki/Load_(computing)" target="_blank">this wikipedia article</a>',
295 + height: 0.7
296 + },
297 +
298 + 'system.io': {
299 + info: 'Total Disk I/O, for all disks, read from <code>/proc/vmstat</code>. You can get detailed information about each disk at the <a href="#disk">Disks</a> section and per application Disk usage at the <a href="#apps">Applications Monitoring</a> section.'
300 + },
301 +
302 + 'system.swapio': {
303 + info: 'Total Swap I/O, read from <code>/proc/vmstat</code>. (netdata measures both <code>in</code> and <code>out</code>. If either of them is not shown in the chart, it is because it is zero - you can change the page settings to always render all the available dimensions on all charts).'
304 + },
305 +
306 + 'system.pgfaults': {
307 + info: 'Total page faults, read from <code>/proc/vmstat</code>. <b>Major page faults</b> indicates that the system is using its swap. You can find which applications use the swap at the <a href="#apps">Applications Monitoring</a> section.'
308 + },
309 +
310 + 'system.entropy': {
311 + colors: '#CC22AA',
312 + info: '<a href="https://en.wikipedia.org/wiki/Entropy_(computing)" target="_blank">Entropy</a>, read from <code>/proc/sys/kernel/random/entropy_avail</code>, is like a pool of random numbers (<a href="https://en.wikipedia.org/wiki//dev/random" target="_blank">/dev/random</a>) that are mainly used in cryptography. It is advised that the pool remains always <a href="https://blog.cloudflare.com/ensuring-randomness-with-linuxs-random-number-generator/" target="_blank">above 200</a>. If the pool of entropy gets empty, you risk your security to be predictable and you should install a user-space random numbers generating daemon, like <a href="http://www.issihosts.com/haveged/" target="_blank">haveged</a> or <code>rng-tools</code> (i.e. <b>rngd</b>), to keep the pool in healthy levels.'
313 + },
314 +
315 + 'system.forks': {
316 + colors: '#5555DD',
317 + info: 'The number of new processes created per second, read from <code>/proc/stat</code>.'
318 + },
319 +
320 + 'system.intr': {
321 + colors: '#DD5555',
322 + info: 'Total number of CPU interrupts, read from <code>/proc/stat</code>. Check <code>system.interrupts</code> that gives more detail about each interrupt and also the <a href="#cpu">CPUs</a> section where interrupts are analyzed per CPU core.'
323 + },
324 +
325 + 'system.interrupts': {
326 + info: 'CPU interrupts in detail, read from <code>/proc/interrupts</code>. At the <a href="#cpu">CPUs</a> section, interrupts are analyzed per CPU core.'
327 + },
328 +
329 + 'system.softirqs': {
330 + info: 'CPU softirqs in detail, read from <code>/proc/softirqs</code>. At the <a href="#cpu">CPUs</a> section, softirqs are analyzed per CPU core.'
331 + },
332 +
333 + 'system.processes': {
334 + info: 'System processes, read from <code>/proc/stat</code>. <b>Running</b> are the processes in the CPU. <b>Blocked</b> are processes that are willing to enter the CPU, but they cannot, e.g. because they wait for disk activity.'
335 + },
336 +
337 + 'system.active_processes': {
338 + info: 'All system processes, read from <code>/proc/loadavg</code>.'
339 + },
340 +
341 + 'system.ctxt': {
342 + info: '<a href="https://en.wikipedia.org/wiki/Context_switch" target="_blank">Context Switches</a>, read from <code>/proc/stat</code>, is the switching of the CPU from one process, task or thread to another. If there are many processes or threads willing to execute and very few CPU cores available to handle them, the system is making more context switching to balance the CPU resources among them. The whole process is computationally intensive. The more the context switches, the slower the system gets.'
343 + },
344 +
345 + 'system.idlejitter': {
346 + colors: '#5555AA',
347 + info: 'Idle jitter is calculated by netdata. A thread is spawned that requests to sleep for a few microseconds. When the system wakes it up, it measures how many microseconds have passed. The difference between the requested and the actual duration of the sleep, is the <b>idle jitter</b>. This number is useful in real-time environments, where CPU jitter can affect the quality of the service (like VoIP media gateways).'
348 + },
349 +
350 + 'system.ipv4': {
351 + info: 'Total IPv4 Traffic, read from <code>/proc/net/netstat</code>.'
352 + },
353 +
354 + 'system.ipv6': {
355 + info: 'Total IPv6 Traffic, read from <code>/proc/net/snmp6</code>.'
356 + },
357 +
358 + 'system.ram': {
359 + info: 'System memory, read from <code>/proc/meminfo</code>.'
360 + },
361 +
362 + 'system.swap': {
363 + info: 'System swap memory, read from <code>/proc/meminfo</code>.'
364 + },
365 +
366 + // ------------------------------------------------------------------------
367 + // MEMORY
368 +
369 + 'mem.ksm_savings': {
370 + heads: [
371 + netdataDashboard.gaugeChart('Saved', '12%', 'savings', '#0099CC')
372 + ]
373 + },
374 +
375 + 'mem.ksm_ratios': {
376 + heads: [
377 + function(id) {
378 + return '<div data-netdata="' + id + '"'
379 + + ' data-gauge-max-value="100"'
380 + + ' data-chart-library="gauge"'
381 + + ' data-title="Savings"'
382 + + ' data-units="percentage %"'
383 + + ' data-gauge-adjust="width"'
384 + + ' data-width="12%"'
385 + + ' data-before="0"'
386 + + ' data-after="-CHART_DURATION"'
387 + + ' data-points="CHART_DURATION"'
388 + + ' role="application"></div>';
389 + }
390 + ]
391 + },
392 +
393 + 'mem.committed': {
394 + colors: NETDATA.colors[3]
395 + },
396 +
397 + // ------------------------------------------------------------------------
398 + // network interfaces
399 +
400 + 'net.drops': {
401 + info: 'Packets that have been dropped at the network interface level. These are the same counters reported by <code>ifconfig</code> as <code>RX dropped</code> (inbound) and <code>TX dropped</code> (outbound). <b>inbound</b> packets can be dropped at the network interface level due to <a href="#system_softnet_stat">softnet backlog</a> overflow, bad / unintented VLAN tags, unknown or unregistered protocols, IPv6 frames when the server is not configured for IPv6. Check <a href="https://www.novell.com/support/kb/doc.php?id=7007165" target="_blank">this document</a> for more information.'
402 + },
403 +
404 + // ------------------------------------------------------------------------
405 + // IPv4
406 +
407 + 'ipv4.tcpmemorypressures': {
408 + 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).'
409 + },
410 +
411 + 'ipv4.tcpconnaborts': {
412 + 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.'
413 + },
414 +
415 + // ------------------------------------------------------------------------
416 + // APPS
417 +
418 + 'apps.cpu': {
419 + height: 2.0
420 + },
421 +
422 + 'apps.mem': {
423 + info: 'Real memory (RAM) used by applications. This does not include shared memory.'
424 + },
425 +
426 + 'apps.vmem': {
427 + 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.'
428 + },
429 +
430 + 'apps.preads': {
431 + height: 2.0
432 + },
433 +
434 + 'apps.pwrites': {
435 + height: 2.0
436 + },
437 +
438 + // ------------------------------------------------------------------------
439 + // USERS
440 +
441 + 'users.cpu': {
442 + height: 2.0
443 + },
444 +
445 + 'users.mem': {
446 + info: 'Real memory (RAM) used per user. This does not include shared memory.'
447 + },
448 +
449 + 'users.vmem': {
450 + 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.'
451 + },
452 +
453 + 'users.preads': {
454 + height: 2.0
455 + },
456 +
457 + 'users.pwrites': {
458 + height: 2.0
459 + },
460 +
461 + // ------------------------------------------------------------------------
462 + // GROUPS
463 +
464 + 'groups.cpu': {
465 + height: 2.0
466 + },
467 +
468 + 'groups.mem': {
469 + info: 'Real memory (RAM) used per user group. This does not include shared memory.'
470 + },
471 +
472 + 'groups.vmem': {
473 + 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.'
474 + },
475 +
476 + 'groups.preads': {
477 + height: 2.0
478 + },
479 +
480 + 'groups.pwrites': {
481 + height: 2.0
482 + },
483 +
484 + // ------------------------------------------------------------------------
485 + // NETWORK QoS
486 +
487 + 'tc.qos': {
488 + heads: [
489 + function(id) {
490 + if(id.match(/.*-ifb$/))
491 + return netdataDashboard.gaugeChart('Inbound', '12%', '', '#5555AA');
492 + else
493 + return netdataDashboard.gaugeChart('Outbound', '12%', '', '#AA9900');
494 + }
495 + ]
496 + },
497 +
498 + // ------------------------------------------------------------------------
499 + // NETWORK INTERFACES
500 +
501 + 'net.net': {
502 + heads: [
503 + netdataDashboard.gaugeChart('Received', '12%', 'received'),
504 + netdataDashboard.gaugeChart('Sent', '12%', 'sent')
505 + ]
506 + },
507 +
508 + // ------------------------------------------------------------------------
509 + // NETFILTER
510 +
511 + 'netfilter.sockets': {
512 + colors: '#88AA00',
513 + heads: [
514 + netdataDashboard.gaugeChart('Active Connections', '12%', '', '#88AA00')
515 + ]
516 + },
517 +
518 + 'netfilter.new': {
519 + heads: [
520 + netdataDashboard.gaugeChart('New Connections', '12%', 'new', '#5555AA')
521 + ]
522 + },
523 +
524 + // ------------------------------------------------------------------------
525 + // DISKS
526 +
527 + 'disk.util': {
528 + colors: '#FF5588',
529 + heads: [
530 + netdataDashboard.gaugeChart('Utilization', '12%', '', '#FF5588')
531 + ],
532 + info: 'Disk Utilization measures the amount of time the disk was busy with something. This is not related to its performance. 100% means that the Linux kernel always had an outstanding operation on the disk. Keep in mind that depending on the underlying technology of the disk, 100% here may or may not be an indication of congestion.'
533 + },
534 +
535 + 'disk.backlog': {
536 + colors: '#0099CC',
537 + info: 'Backlog is an indication of the duration of pending disk operations. On every I/O event the Linux kernel is multiplying the time spent doing I/O since the last update of this field with the number of pending operations. While not accurate, this metric can provide an indication of the expected completion time of the operations in progress.'
538 + },
539 +
540 + 'disk.io': {
541 + heads: [
542 + netdataDashboard.gaugeChart('Read', '12%', 'reads'),
543 + netdataDashboard.gaugeChart('Write', '12%', 'writes')
544 + ],
545 + info: 'Amount of data transferred to and from disk.'
546 + },
547 +
548 + 'disk.ops': {
549 + info: 'Completed disk I/O operations. Keep in mind the number of operations requested might be higher, since the Linux kernel is able to merge adjacent to each other (see merged operations chart).'
550 + },
551 +
552 + 'disk.qops': {
553 + info: 'I/O operations currently in progress. This metric is a snapshot - it is not an average over the last interval.'
554 + },
555 +
556 + 'disk.iotime': {
557 + height: 0.5,
558 + info: 'The sum of the duration of all completed I/O operations. This number can exceed the interval if the disk is able to execute I/O operations in parallel.'
559 + },
560 + 'disk.mops': {
561 + height: 0.5,
562 + info: 'The number of merged disk operations. The Linux kernel is able to merge adjacent I/O operations, for example two 4KB reads can become one 8KB read before given to disk.'
563 + },
564 + 'disk.svctm': {
565 + height: 0.5,
566 + info: 'The average service time for completed I/O operations. This metric is calculated using the total busy time of the disk and the number of completed operations. If the disk is able to execute multiple parallel operations the reporting average service time will be misleading.'
567 + },
568 + 'disk.avgsz': {
569 + height: 0.5,
570 + info: 'The average I/O operation size.'
571 + },
572 + 'disk.await': {
573 + height: 0.5,
574 + info: 'The average time for I/O requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them.'
575 + },
576 +
577 + 'disk.space': {
578 + info: 'Disk space utilization. reserved for root is automatically reserved by the system to prevent the root user from getting out of space.'
579 + },
580 + 'disk.inodes': {
581 + info: 'inodes (or index nodes) are filesystem objects (e.g. files and directories). On many types of file system implementations, the maximum number of inodes is fixed at filesystem creation, limiting the maximum number of files the filesystem can hold. It is possible for a device to run out of inodes. When this happens, new files cannot be created on the device, even though there may be free space available.'
582 + },
583 +
584 + 'mysql.net': {
585 + info: 'The amount of data sent to mysql clients (<strong>out</strong>) and received from mysql clients (<strong>in</strong>).'
586 + },
587 +
588 + // ------------------------------------------------------------------------
589 + // MYSQL
590 +
591 + 'mysql.queries': {
592 + info: 'The number of statements executed by the server.<ul>' +
593 + '<li><strong>queries</strong> counts the statements executed within stored SQL programs.</li>' +
594 + '<li><strong>questions</strong> counts the statements sent to the mysql server by mysql clients.</li>' +
595 + '<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.' +
596 + ' 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>' +
597 + '</ul>'
598 + },
599 +
600 + 'mysql.handlers': {
601 + info: 'Usage of the internal handlers of mysql. This chart provides very good insights of what the mysql server is actually doing.' +
602 + ' (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>' +
603 + '<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>' +
604 + '<li><strong>delete</strong>, the number of times that rows have been deleted from tables.</li>' +
605 + '<li><strong>prepare</strong>, a counter for the prepare phase of two-phase commit operations.</li>' +
606 + '<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>' +
607 + '<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>' +
608 + '<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>' +
609 + '<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>' +
610 + '<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>' +
611 + '<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>' +
612 + '<li><strong>rollback</strong>, the number of requests for a storage engine to perform a rollback operation.</li>' +
613 + '<li><strong>savepoint</strong>, the number of requests for a storage engine to place a savepoint.</li>' +
614 + '<li><strong>savepoint rollback</strong>, the number of requests for a storage engine to roll back to a savepoint.</li>' +
615 + '<li><strong>update</strong>, the number of requests to update a row in a table.</li>' +
616 + '<li><strong>write</strong>, the number of requests to insert a row in a table.</li>' +
617 + '</ul>'
618 + },
619 +
620 + 'mysql.table_locks': {
621 + info: 'MySQL table locks counters: <ul>' +
622 + '<li><strong>immediate</strong>, the number of times that a request for a table lock could be granted immediately.</li>' +
623 + '<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>' +
624 + '</ul>'
625 + },
626 +
627 + // ------------------------------------------------------------------------
628 + // APACHE
629 +
630 + 'apache.connections': {
631 + colors: NETDATA.colors[4],
632 + mainheads: [
633 + netdataDashboard.gaugeChart('Connections', '12%', '', NETDATA.colors[4])
634 + ]
635 + },
636 +
637 + 'apache.requests': {
638 + colors: NETDATA.colors[0],
639 + mainheads: [
640 + netdataDashboard.gaugeChart('Requests', '12%', '', NETDATA.colors[0])
641 + ]
642 + },
643 +
644 + 'apache.net': {
645 + colors: NETDATA.colors[3],
646 + mainheads: [
647 + netdataDashboard.gaugeChart('Bandwidth', '12%', '', NETDATA.colors[3])
648 + ]
649 + },
650 +
651 + 'apache.workers': {
652 + mainheads: [
653 + function(id) {
654 + return '<div data-netdata="' + id + '"'
655 + + ' data-dimensions="busy"'
656 + + ' data-append-options="percentage"'
657 + + ' data-gauge-max-value="100"'
658 + + ' data-chart-library="gauge"'
659 + + ' data-title="Workers Utilization"'
660 + + ' data-units="percentage %"'
661 + + ' data-gauge-adjust="width"'
662 + + ' data-width="12%"'
663 + + ' data-before="0"'
664 + + ' data-after="-CHART_DURATION"'
665 + + ' data-points="CHART_DURATION"'
666 + + ' role="application"></div>';
667 + }
668 + ]
669 + },
670 +
671 + 'apache.bytesperreq': {
672 + colors: NETDATA.colors[3],
673 + height: 0.5
674 + },
675 +
676 + 'apache.reqpersec': {
677 + colors: NETDATA.colors[4],
678 + height: 0.5
679 + },
680 +
681 + 'apache.bytespersec': {
682 + colors: NETDATA.colors[6],
683 + height: 0.5
684 + },
685 +
686 +
687 + // ------------------------------------------------------------------------
688 + // NGINX
689 +
690 + 'nginx.connections': {
691 + colors: NETDATA.colors[4],
692 + mainheads: [
693 + netdataDashboard.gaugeChart('Connections', '12%', '', NETDATA.colors[4])
694 + ]
695 + },
696 +
697 + 'nginx.requests': {
698 + colors: NETDATA.colors[0],
699 + mainheads: [
700 + netdataDashboard.gaugeChart('Requests', '12%', '', NETDATA.colors[0])
701 + ]
702 + },
703 +
704 + // ------------------------------------------------------------------------
705 + // NETDATA
706 +
707 + 'netdata.response_time': {
708 + info: 'The netdata API response time measures the time netdata needed to serve requests. This time includes everything, from the reception of the first byte of a request, to the dispatch of the last byte of its reply, therefore it includes all network latencies involved (i.e. a client over a slow network will influence these metrics).'
709 + },
710 +
711 + // ------------------------------------------------------------------------
712 + // RETROSHARE
713 +
714 + 'retroshare.bandwidth': {
715 + info: 'RetroShare inbound and outbound traffic.',
716 + mainheads: [
717 + netdataDashboard.gaugeChart('Received', '12%', 'bandwidth_down_kb'),
718 + netdataDashboard.gaugeChart('Sent', '12%', 'bandwidth_up_kb')
719 + ]
720 + },
721 +
722 + 'retroshare.peers': {
723 + info: 'Number of (connected) RetroShare friends.',
724 + mainheads: [
725 + function(id) {
726 + return '<div data-netdata="' + id + '"'
727 + + ' data-dimensions="peers_connected"'
728 + + ' data-append-options="friends"'
729 + + ' data-chart-library="easypiechart"'
730 + + ' data-title="connected friends"'
731 + + ' data-units=""'
732 + + ' data-width="8%"'
733 + + ' data-before="0"'
734 + + ' data-after="-CHART_DURATION"'
735 + + ' data-points="CHART_DURATION"'
736 + + ' role="application"></div>';
737 + }
738 + ]
739 + },
740 +
741 + 'retroshare.dht': {
742 + info: 'Statistics about RetroShare\'s DHT. These values are estimated!'
743 + },
744 +
745 + // ------------------------------------------------------------------------
746 + // fping
747 +
748 + 'fping.loss': {
749 + colors: NETDATA.colors[1],
750 + height: 0.5
751 + },
752 +
753 + 'fping.packets': {
754 + height: 0.5
755 + }
756 +
757 +};
web/demo.html
+1 -1
@@ -20,7 +20,7 @@
20 <meta property="og:title" content="netdata - real-time performance monitoring, done right!"/>
21 <meta property="og:description" content="Stunning real-time dashboards, blazingly fast and extremely interactive. Zero configuration, zero dependencies, zero maintenance." />
22 </head>
23 -<script type="text/javascript" src="dashboard.js?v20161030-10"></script>
23 +<script type="text/javascript" src="dashboard.js?v20161030-30"></script>
24 <body>
25
26 <div style="width: 100%; text-align: center;">
web/demo2.html
+1 -1
@@ -21,7 +21,7 @@
21 <meta property="og:description" content="Stunning real-time dashboards, blazingly fast and extremely interactive. Zero configuration, zero dependencies, zero maintenance." />
22 </head>
23 <script>var netdataTheme = 'slate';</script>
24 -<script type="text/javascript" src="http://my-netdata.io/dashboard.js?v20161030-10"></script>
24 +<script type="text/javascript" src="http://my-netdata.io/dashboard.js?v20161030-30"></script>
25 <body>
26
27 <div class="container" style="width: 90%; padding-top: 10px; text-align: center; color: #AAA">
web/demosites.html
+47 -3
@@ -52,7 +52,7 @@
52 and that you have chown it to be owned by netdata:netdata
53 -->
54 <!-- <script type="text/javascript" src="http://my.server:19999/dashboard.js"></script> -->
55 - <script type="text/javascript" src="dashboard.js?v20161030-10"></script>
55 + <script type="text/javascript" src="dashboard.js?v20161030-30"></script>
56
57 <script>
58 // --- OPTIONS FOR THE CHARTS --
@@ -87,7 +87,7 @@
87 display: inline-block;
88 min-height: 50px;
89 width: 100%;
90 - height: 8vmax;
90 + height: 7vmax;
91 text-align: left;
92 }
93
@@ -118,7 +118,7 @@
118 position: relative;
119 display: inline-block;
120 width: 100%;
121 - height: 14vmax;
121 + height: 12vmax;
122 min-height: 150px;
123 text-align: left;
124 }
@@ -199,6 +199,7 @@
199 data-title="EU - London"
200 data-chart-library="gauge"
201 data-decimal-digits="0"
202 + data-common-max="top-gauges"
203 data-width="100%"
204 data-after="-300"
205 data-points="300"
@@ -220,6 +221,7 @@
221 data-title="US - Atlanta"
222 data-chart-library="gauge"
223 data-decimal-digits="0"
224 + data-common-max="top-gauges"
225 data-width="100%"
226 data-after="-300"
227 data-points="300"
@@ -241,6 +243,7 @@
243 data-title="US - California"
244 data-chart-library="gauge"
245 data-decimal-digits="0"
246 + data-common-max="top-gauges"
247 data-width="100%"
248 data-after="-300"
249 data-points="300"
@@ -262,6 +265,7 @@
265 data-title="Canada"
266 data-chart-library="gauge"
267 data-decimal-digits="0"
268 + data-common-max="top-gauges"
269 data-width="100%"
270 data-after="-300"
271 data-points="300"
@@ -284,6 +288,7 @@
288 data-title="EU - Germany"
289 data-chart-library="easypiechart"
290 data-decimal-digits="0"
291 + data-common-max="top-gauges"
292 data-width="75%"
293 data-after="-300"
294 data-points="300"
@@ -305,6 +310,7 @@
310 data-title="US - New York"
311 data-chart-library="easypiechart"
312 data-decimal-digits="0"
313 + data-common-max="top-gauges"
314 data-width="75%"
315 data-after="-300"
316 data-points="300"
@@ -326,6 +332,7 @@
332 data-title="Singapore"
333 data-chart-library="easypiechart"
334 data-decimal-digits="0"
335 + data-common-max="top-gauges"
336 data-width="75%"
337 data-after="-300"
338 data-points="300"
@@ -347,6 +354,7 @@
354 data-title="India"
355 data-chart-library="easypiechart"
356 data-decimal-digits="0"
357 + data-common-max="top-gauges"
358 data-width="75%"
359 data-after="-300"
360 data-points="300"
@@ -409,6 +417,7 @@
417 data-dimensions="requests"
418 data-host="//london.my-netdata.io"
419 data-decimal-digits="0"
420 + data-common-max="web-requests"
421 data-chart-library="dygraph"
422 data-dygraph-theme="sparkline"
423 data-dygraph-type="area"
@@ -430,6 +439,7 @@
439 data-dimensions="requests"
440 data-host="//atlanta.my-netdata.io"
441 data-decimal-digits="0"
442 + data-common-max="web-requests"
443 data-chart-library="dygraph"
444 data-dygraph-theme="sparkline"
445 data-dygraph-type="area"
@@ -451,6 +461,7 @@
461 data-dimensions="requests"
462 data-host="//sanfrancisco.netdata.rocks"
463 data-decimal-digits="0"
464 + data-common-max="web-requests"
465 data-chart-library="dygraph"
466 data-dygraph-theme="sparkline"
467 data-dygraph-type="area"
@@ -472,6 +483,7 @@
483 data-dimensions="requests"
484 data-host="//toronto.netdata.rocks"
485 data-decimal-digits="0"
486 + data-common-max="web-requests"
487 data-chart-library="dygraph"
488 data-dygraph-theme="sparkline"
489 data-dygraph-type="area"
@@ -495,6 +507,7 @@
507 data-dimensions="active"
508 data-host="//london.my-netdata.io"
509 data-decimal-digits="0"
510 + data-common-max="web-connections"
511 data-chart-library="dygraph"
512 data-dygraph-theme="sparkline"
513 data-dygraph-type="area"
@@ -516,6 +529,7 @@
529 data-dimensions="active"
530 data-host="//atlanta.my-netdata.io"
531 data-decimal-digits="0"
532 + data-common-max="web-connections"
533 data-chart-library="dygraph"
534 data-dygraph-theme="sparkline"
535 data-dygraph-type="area"
@@ -537,6 +551,7 @@
551 data-dimensions="active"
552 data-host="//sanfrancisco.netdata.rocks"
553 data-decimal-digits="0"
554 + data-common-max="web-connections"
555 data-chart-library="dygraph"
556 data-dygraph-theme="sparkline"
557 data-dygraph-type="area"
@@ -558,6 +573,7 @@
573 data-dimensions="active"
574 data-host="//toronto.netdata.rocks"
575 data-decimal-digits="0"
576 + data-common-max="web-connections"
577 data-chart-library="dygraph"
578 data-dygraph-theme="sparkline"
579 data-dygraph-type="area"
@@ -595,6 +611,7 @@
611 <div class="myfullchart">
612 <div data-netdata="tc.world_out"
613 data-host="//london.my-netdata.io"
614 + data-common-max="tc-world-out"
615 data-chart-library="dygraph"
616 data-title="EU - London, traffic we send per service"
617 data-width="100%"
@@ -607,6 +624,7 @@
624 <div data-netdata="tc.world_out"
625 data-host="//atlanta.my-netdata.io"
626 data-chart-library="dygraph"
627 + data-common-max="tc-world-out"
628 data-title="US - Atlanta, traffic we send per service"
629 data-width="100%"
630 data-height="100%"
@@ -619,6 +637,7 @@
637 <div data-netdata="tc.world_out"
638 data-host="//sanfrancisco.netdata.rocks"
639 data-chart-library="dygraph"
640 + data-common-max="tc-world-out"
641 data-title="US - California, traffic we send per service"
642 data-width="100%"
643 data-height="100%"
@@ -630,6 +649,7 @@
649 <div data-netdata="tc.world_out"
650 data-host="//toronto.netdata.rocks"
651 data-chart-library="dygraph"
652 + data-common-max="tc-world-out"
653 data-title="Canada, traffic we send per service"
654 data-width="100%"
655 data-height="100%"
@@ -642,6 +662,7 @@
662 <div class="myfullchart">
663 <div data-netdata="tc.world_in"
664 data-host="//london.my-netdata.io"
665 + data-common-max="tc-world-in"
666 data-chart-library="dygraph"
667 data-title="EU - London, traffic we receive per service"
668 data-width="100%"
@@ -654,6 +675,7 @@
675 <div class="myfullchart">
676 <div data-netdata="tc.world_in"
677 data-host="//atlanta.my-netdata.io"
678 + data-common-max="tc-world-in"
679 data-chart-library="dygraph"
680 data-title="US - Atlanta, traffic we receive per service"
681 data-width="100%"
@@ -666,6 +688,7 @@
688 <div class="myfullchart">
689 <div data-netdata="tc.world_in"
690 data-host="//sanfrancisco.netdata.rocks"
691 + data-common-max="tc-world-in"
692 data-chart-library="dygraph"
693 data-title="US - California, traffic we receive per service"
694 data-width="100%"
@@ -677,6 +700,7 @@
700 <div class="myfullchart">
701 <div data-netdata="tc.world_in"
702 data-host="//toronto.netdata.rocks"
703 + data-common-max="tc-world-in"
704 data-chart-library="dygraph"
705 data-title="Canada, traffic we receive per service"
706 data-width="100%"
@@ -709,6 +733,7 @@
733 data-dimensions="received"
734 data-host="//london.my-netdata.io"
735 data-decimal-digits="0"
736 + data-common-max="synproxy-in"
737 data-chart-library="dygraph"
738 data-dygraph-theme="sparkline"
739 data-dygraph-type="area"
@@ -730,6 +755,7 @@
755 data-dimensions="received"
756 data-host="//atlanta.my-netdata.io"
757 data-decimal-digits="0"
758 + data-common-max="synproxy-in"
759 data-chart-library="dygraph"
760 data-dygraph-theme="sparkline"
761 data-dygraph-type="area"
@@ -751,6 +777,7 @@
777 data-dimensions="received"
778 data-host="//sanfrancisco.netdata.rocks"
779 data-decimal-digits="0"
780 + data-common-max="synproxy-in"
781 data-chart-library="dygraph"
782 data-dygraph-theme="sparkline"
783 data-dygraph-type="area"
@@ -772,6 +799,7 @@
799 data-dimensions="received"
800 data-host="//toronto.netdata.rocks"
801 data-decimal-digits="0"
802 + data-common-max="synproxy-in"
803 data-chart-library="dygraph"
804 data-dygraph-theme="sparkline"
805 data-dygraph-type="area"
@@ -873,6 +901,8 @@
901 </div>
902 <div data-netdata="apps.cpu"
903 data-dimensions="netdata"
904 + data-common-max="users-cpu"
905 + data-decimal-digits="1"
906 data-host="//london.my-netdata.io"
907 data-chart-library="dygraph"
908 data-dygraph-theme="sparkline"
@@ -893,6 +923,8 @@
923 </div>
924 <div data-netdata="apps.cpu"
925 data-dimensions="netdata"
926 + data-common-max="users-cpu"
927 + data-decimal-digits="1"
928 data-host="//atlanta.my-netdata.io"
929 data-chart-library="dygraph"
930 data-dygraph-theme="sparkline"
@@ -913,6 +945,8 @@
945 </div>
946 <div data-netdata="apps.cpu"
947 data-dimensions="netdata"
948 + data-common-max="users-cpu"
949 + data-decimal-digits="1"
950 data-host="//sanfrancisco.netdata.rocks"
951 data-chart-library="dygraph"
952 data-dygraph-theme="sparkline"
@@ -933,6 +967,8 @@
967 </div>
968 <div data-netdata="apps.cpu"
969 data-dimensions="netdata"
970 + data-common-max="users-cpu"
971 + data-decimal-digits="1"
972 data-host="//toronto.netdata.rocks"
973 data-chart-library="dygraph"
974 data-dygraph-theme="sparkline"
@@ -961,6 +997,8 @@
997 </div>
998 <div data-netdata="netdata.response_time"
999 data-host="//london.my-netdata.io"
1000 + data-common-max="netdata-response-time"
1001 + data-decimal-digits="1"
1002 data-chart-library="dygraph"
1003 data-dygraph-theme="sparkline"
1004 data-dygraph-type="area"
@@ -980,6 +1018,8 @@
1018 </div>
1019 <div data-netdata="netdata.response_time"
1020 data-host="//atlanta.my-netdata.io"
1021 + data-common-max="netdata-response-time"
1022 + data-decimal-digits="1"
1023 data-chart-library="dygraph"
1024 data-dygraph-theme="sparkline"
1025 data-dygraph-type="area"
@@ -999,6 +1039,8 @@
1039 </div>
1040 <div data-netdata="netdata.response_time"
1041 data-host="//sanfrancisco.netdata.rocks"
1042 + data-common-max="netdata-response-time"
1043 + data-decimal-digits="1"
1044 data-chart-library="dygraph"
1045 data-dygraph-theme="sparkline"
1046 data-dygraph-type="area"
@@ -1018,6 +1060,8 @@
1060 </div>
1061 <div data-netdata="netdata.response_time"
1062 data-host="//toronto.netdata.rocks"
1063 + data-decimal-digits="1"
1064 + data-common-max="netdata-response-time"
1065 data-chart-library="dygraph"
1066 data-dygraph-theme="sparkline"
1067 data-dygraph-type="area"
web/goto-host-from-alarm.html
+1 -1
@@ -18,7 +18,7 @@
18 var netdataTheme = 'slate';
19 var netdataShowHelp = true;
20 </script>
21 -<script type="text/javascript" src="dashboard.js?v20161030-10"></script>
21 +<script type="text/javascript" src="dashboard.js?v20161030-30"></script>
22
23 <script>
24 var urlOptions = {
web/index.html
+10 -2
@@ -1018,6 +1018,13 @@
1018 return '';
1019 },
1020
1021 + contextValueRange: function(id) {
1022 + if(typeof netdataDashboard.context[id] !== 'undefined' && typeof netdataDashboard.context[id].valueRange !== 'undefined')
1023 + return netdataDashboard.context[id].valueRange;
1024 + else
1025 + return '[null, null]';
1026 + },
1027 +
1028 contextHeight: function(id, def) {
1029 if(typeof netdataDashboard.context[id] !== 'undefined' && typeof netdataDashboard.context[id].height !== 'undefined')
1030 return def * netdataDashboard.context[id].height;
@@ -1298,6 +1305,7 @@
1305 chtml += netdataDashboard.contextInfo(chart.context) + '<div id="chart_' + NETDATA.name2id(chart.id) + '" data-netdata="' + chart.id + '"'
1306 + ' data-width="' + pcent_width.toString() + '%"'
1307 + ' data-height="' + netdataDashboard.contextHeight(chart.context, options.chartsHeight).toString() + 'px"'
1308 + + ' data-dygraph-valuerange="' + netdataDashboard.contextValueRange(chart.context) + '"'
1309 + ' data-before="0"'
1310 + ' data-after="-' + duration.toString() + '"'
1311 + ' data-id="' + NETDATA.name2id(options.hostname + '/' + chart.id) + '"'
@@ -2548,7 +2556,7 @@
2556 });
2557
2558 NETDATA.requiredJs.push({
2551 - url: NETDATA.serverDefault + 'dashboard_info.js?v20161030-2',
2559 + url: NETDATA.serverDefault + 'dashboard_info.js?v20161030-4',
2560 async: false,
2561 isAlreadyLoaded: function() { return false; }
2562 });
@@ -3168,4 +3176,4 @@
3176 </div>
3177 </body>
3178 </html>
3171 -<script type="text/javascript" src="dashboard.js?v20161030-10"></script>
3179 +<script type="text/javascript" src="dashboard.js?v20161030-30"></script>
web/registry.html
+1 -1
@@ -169,7 +169,7 @@ var netdataRegistryCallback = function(machines_array) {
169 and that you have chown it to be owned by netdata:netdata
170 -->
171 <!-- <script type="text/javascript" src="http://my.server:19999/dashboard.js"></script> -->
172 -<script type="text/javascript" src="dashboard.js?v20161030-10"></script>
172 +<script type="text/javascript" src="dashboard.js?v20161030-30"></script>
173
174 <script>
175 // Set options for TV operation
web/tv.html
+27 -1
@@ -50,7 +50,7 @@ var netdataTheme = 'slate'; // this is dark
50 and that you have chown it to be owned by netdata:netdata
51 -->
52 <!-- <script type="text/javascript" src="http://my.server:19999/dashboard.js"></script> -->
53 -<script type="text/javascript" src="dashboard.js?v20161030-10"></script>
53 +<script type="text/javascript" src="dashboard.js?v20161030-30"></script>
54
55 <script>
56 // Set options for TV operation
@@ -99,6 +99,7 @@ setTimeout(function(){
99 data-width="49%"
100 data-height="100%"
101 data-after="-300"
102 + data-dygraph-valuerange="[0, 100]"
103 ></div>
104 <div data-netdata="system.cpu"
105 data-title="CPU usage of your netdata server"
@@ -106,6 +107,7 @@ setTimeout(function(){
107 data-width="49%"
108 data-height="100%"
109 data-after="-300"
110 + data-dygraph-valuerange="[0, 100]"
111 ></div>
112 </div>
113 </div>
@@ -118,6 +120,8 @@ setTimeout(function(){
120 <div style="width: 100%; height: calc(100% - 15px); text-align: center; display: inline-block;">
121 <div data-netdata="system.io"
122 data-host="http://registry.my-netdata.io"
123 + data-common-max="io"
124 + data-common-min="io"
125 data-title="I/O on registry.my-netdata.io"
126 data-chart-library="dygraph"
127 data-width="49%"
@@ -126,6 +130,8 @@ setTimeout(function(){
130 ></div>
131 <div data-netdata="system.io"
132 data-title="I/O on your netdata server"
133 + data-common-max="io"
134 + data-common-min="io"
135 data-chart-library="dygraph"
136 data-width="49%"
137 data-height="100%"
@@ -142,6 +148,8 @@ setTimeout(function(){
148 <div style="width: 100%; height: calc(100% - 15px); text-align: center; display: inline-block;">
149 <div data-netdata="system.ipv4"
150 data-host="http://registry.my-netdata.io"
151 + data-common-max="traffic"
152 + data-common-min="traffic"
153 data-title="IPv4 traffic on registry.my-netdata.io"
154 data-chart-library="dygraph"
155 data-width="49%"
@@ -150,6 +158,8 @@ setTimeout(function(){
158 ></div>
159 <div data-netdata="system.ipv4"
160 data-title="IPv4 traffic on your netdata server"
161 + data-common-max="traffic"
162 + data-common-min="traffic"
163 data-chart-library="dygraph"
164 data-width="49%"
165 data-height="100%"
@@ -168,6 +178,8 @@ setTimeout(function(){
178 <br/>
179 <div data-netdata="netdata.requests"
180 data-host="http://registry.my-netdata.io"
181 + data-common-max="netdata-requests"
182 + data-decimal-digits="0"
183 data-title="Chart Refreshes/s"
184 data-chart-library="gauge"
185 data-width="20%"
@@ -177,6 +189,8 @@ setTimeout(function(){
189 ></div>
190 <div data-netdata="netdata.clients"
191 data-host="http://registry.my-netdata.io"
192 + data-common-max="netdata-clients"
193 + data-decimal-digits="0"
194 data-title="Sockets"
195 data-chart-library="gauge"
196 data-width="20%"
@@ -187,6 +201,8 @@ setTimeout(function(){
201 ></div>
202 <div data-netdata="netdata.net"
203 data-dimensions="in"
204 + data-common-max="netdata-net-in"
205 + data-decimal-digits="0"
206 data-host="http://registry.my-netdata.io"
207 data-title="Requests Traffic"
208 data-chart-library="easypiechart"
@@ -197,6 +213,8 @@ setTimeout(function(){
213 ></div>
214 <div data-netdata="netdata.net"
215 data-dimensions="out"
216 + data-common-max="netdata-net-out"
217 + data-decimal-digits="0"
218 data-host="http://registry.my-netdata.io"
219 data-title="Chart Data Traffic"
220 data-chart-library="easypiechart"
@@ -211,6 +229,8 @@ setTimeout(function(){
229 <br/>
230 <div data-netdata="netdata.requests"
231 data-title="Chart Refreshes/s"
232 + data-common-max="netdata-requests"
233 + data-decimal-digits="0"
234 data-chart-library="gauge"
235 data-width="20%"
236 data-height="100%"
@@ -218,6 +238,8 @@ setTimeout(function(){
238 data-points="300"
239 ></div>
240 <div data-netdata="netdata.clients"
241 + data-common-max="netdata-clients"
242 + data-decimal-digits="0"
243 data-title="Sockets"
244 data-chart-library="gauge"
245 data-width="20%"
@@ -228,6 +250,8 @@ setTimeout(function(){
250 ></div>
251 <div data-netdata="netdata.net"
252 data-dimensions="in"
253 + data-common-max="netdata-net-in"
254 + data-decimal-digits="0"
255 data-title="Requests Traffic"
256 data-chart-library="easypiechart"
257 data-width="15%"
@@ -237,6 +261,8 @@ setTimeout(function(){
261 ></div>
262 <div data-netdata="netdata.net"
263 data-dimensions="out"
264 + data-common-max="netdata-net-out"
265 + data-decimal-digits="0"
266 data-title="Chart Data Traffic"
267 data-chart-library="easypiechart"
268 data-width="15%"