forked from YuanzhuL/netdata-cpatch
-
Notifications
You must be signed in to change notification settings - Fork 0
/
dashboard_info.js
2400 lines (2006 loc) · 122 KB
/
dashboard_info.js
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
// SPDX-License-Identifier: GPL-3.0-or-later
// Codacy declarations
/* global NETDATA */
var netdataDashboard = window.netdataDashboard || {};
// Informational content for the various sections of the GUI (menus, sections, charts, etc.)
// ----------------------------------------------------------------------------
// Menus
netdataDashboard.menu = {
'system': {
title: '系统概观',
icon: '<i class="fas fa-bookmark"></i>',
info: '一眼掌握系统效能关键指标。'
},
'services': {
title: '系统服务',
icon: '<i class="fas fa-cogs"></i>',
info: '系统服务的使用情况。netdata 以 CGROUPS 监视所有系统服务。'
},
'ap': {
title: 'Access Points',
icon: '<i class="fas fa-wifi"></i>',
info: 'Performance metrics for the access points (i.e. wireless interfaces in AP mode) found on the system.'
},
'tc': {
title: 'Quality of Service',
icon: '<i class="fas fa-globe"></i>',
info: 'Netdata collects and visualizes <code>tc</code> class utilization using its ' +
'<a href="https://github.com/netdata/netdata/blob/master/collectors/tc.plugin/tc-qos-helper.sh.in" target="_blank">tc-helper plugin</a>. ' +
'If you also use <a href="http://firehol.org/#fireqos" target="_blank">FireQOS</a> for setting up QoS, ' +
'netdata automatically collects interface and class names. If your QoS configuration includes overheads ' +
'calculation, the values shown here will include these overheads (the total bandwidth for the same ' +
'interface as reported in the Network Interfaces section, will be lower than the total bandwidth ' +
'reported here). QoS data collection may have a slight time difference compared to the interface ' +
'(QoS data collection uses a BASH script, so a shift in data collection of a few milliseconds ' +
'should be justified).'
},
'net': {
title: '网路介面',
icon: '<i class="fas fa-sitemap"></i>',
info: '网路介面的效能指标。'
},
'ip': {
title: '网路堆叠',
icon: '<i class="fas fa-cloud"></i>',
info: function (os) {
if(os === "linux")
return 'Metrics for the networking stack of the system. These metrics are collected from <code>/proc/net/netstat</code>, apply to both IPv4 and IPv6 traffic and are related to operation of the kernel networking stack.';
else
return 'Metrics for the networking stack of the system.';
}
},
'ipv4': {
title: 'IPv4 网路',
icon: '<i class="fas fa-cloud"></i>',
info: 'IPv4 效能指标。' +
'<a href="https://en.wikipedia.org/wiki/IPv4" target="_blank">Internet Protocol version 4 (IPv4)</a> is ' +
'the fourth version of the Internet Protocol (IP). It is one of the core protocols of standards-based ' +
'internetworking methods in the Internet. IPv4 is a connectionless protocol for use on packet-switched ' +
'networks. It operates on a best effort delivery model, in that it does not guarantee delivery, nor does ' +
'it assure proper sequencing or avoidance of duplicate delivery. These aspects, including data integrity, ' +
'are addressed by an upper layer transport protocol, such as the Transmission Control Protocol (TCP).'
},
'ipv6': {
title: 'IPv6 网路',
icon: '<i class="fas fa-cloud"></i>',
info: 'IPv6 效能指标。 <a href="https://en.wikipedia.org/wiki/IPv6" target="_blank">Internet Protocol version 6 (IPv6)</a> is the most recent version of the Internet Protocol (IP), the communications protocol that provides an identification and location system for computers on networks and routes traffic across the Internet. IPv6 was developed by the Internet Engineering Task Force (IETF) to deal with the long-anticipated problem of IPv4 address exhaustion. IPv6 is intended to replace IPv4.'
},
'sctp': {
title: 'SCTP Networking',
icon: '<i class="fas fa-cloud"></i>',
info: '<a href="https://en.wikipedia.org/wiki/Stream_Control_Transmission_Protocol" target="_blank">Stream Control Transmission Protocol (SCTP)</a> is a computer network protocol which operates at the transport layer and serves a role similar to the popular protocols TCP and UDP. SCTP provides some of the features of both UDP and TCP: it is message-oriented like UDP and ensures reliable, in-sequence transport of messages with congestion control like TCP. It differs from those protocols by providing multi-homing and redundant paths to increase resilience and reliability.'
},
'ipvs': {
title: 'IP Virtual Server',
icon: '<i class="fas fa-eye"></i>',
info: '<a href="http://www.linuxvirtualserver.org/software/ipvs.html" target="_blank">IPVS (IP Virtual Server)</a> implements transport-layer load balancing inside the Linux kernel, so called Layer-4 switching. IPVS running on a host acts as a load balancer at the front of a cluster of real servers, it can direct requests for TCP/UDP based services to the real servers, and makes services of the real servers to appear as a virtual service on a single IP address.'
},
'netfilter': {
title: '防火墙 (netfilter)',
icon: '<i class="fas fa-shield-alt"></i>',
info: 'netfilter 元件效能指标。'
},
'ipfw': {
title: '防火墙 (ipfw)',
icon: '<i class="fas fa-shield-alt"></i>',
info: 'Counters and memory usage for the ipfw rules.'
},
'cpu': {
title: 'CPU',
icon: '<i class="fas fa-bolt"></i>',
info: '系统中每一个 CPU 的详细资讯。全部 CPU 的总量可以到 <a href="#menu_system">系统概观</a> 区段查看。'
},
'mem': {
title: '记忆体',
icon: '<i class="fas fa-microchip"></i>',
info: '系统记忆体管理的详细资讯。'
},
'disk': {
title: '磁碟',
icon: '<i class="fas fa-hdd"></i>',
info: '系统中所有磁碟效能资讯图表。特别留意：这是以 <code>iostat -x</code> 所取得的效能数据做为呈现。在预设情况下，netdata 不会显示单一分割区与未挂载的虚拟磁碟效能图表。若仍想要显示，可以修改 netdata 设定档中的相关设定。'
},
'sensors': {
title: '感测器',
icon: '<i class="fas fa-leaf"></i>',
info: '系统已配置相关感测器的读数'
},
'ipmi': {
title: 'IPMI',
icon: '<i class="fas fa-leaf"></i>',
info: 'The Intelligent Platform Management Interface (IPMI) is a set of computer interface specifications for an autonomous computer subsystem that provides management and monitoring capabilities independently of the host system\'s CPU, firmware (BIOS or UEFI) and operating system.'
},
'samba': {
title: 'Samba',
icon: '<i class="fas fa-folder-open"></i>',
info: 'Performance metrics of the Samba file share operations of this system. Samba is a implementation of Windows services, including Windows SMB protocol file shares.'
},
'nfsd': {
title: 'NFS 伺服器',
icon: '<i class="fas fa-folder-open"></i>',
info: 'Performance metrics of the Network File Server. NFS is a distributed file system protocol, allowing a user on a client computer to access files over a network, much like local storage is accessed. NFS, like many other protocols, builds on the Open Network Computing Remote Procedure Call (ONC RPC) system. The NFS is an open standard defined in Request for Comments (RFC).'
},
'nfs': {
title: 'NFS 客户端',
icon: '<i class="fas fa-folder-open"></i>',
info: '显示本机做为 NFS 客户端的效能指标。'
},
'zfs': {
title: 'ZFS 档案系统',
icon: '<i class="fas fa-folder-open"></i>',
info: 'ZFS 档案系统的效能指标。以下图表呈现来自 <a href="https://github.com/zfsonlinux/zfs/blob/master/cmd/arcstat/arcstat.py" target="_blank">arcstat.py</a> 与 <a href="https://github.com/zfsonlinux/zfs/blob/master/cmd/arc_summary/arc_summary.py" target="_blank">arc_summary.py</a> 的效能数据。'
},
'btrfs': {
title: 'BTRFS 档案系统',
icon: '<i class="fas fa-folder-open"></i>',
info: 'BTRFS 档案系统磁碟空间使用指标。'
},
'apps': {
title: '应用程序',
icon: '<i class="fas fa-heartbeat"></i>',
info: 'Per application statistics are collected using netdata\'s <code>apps.plugin</code>. This plugin walks through all processes and aggregates statistics for applications of interest, defined in <code>/etc/netdata/apps_groups.conf</code>, which can be edited by running <code>$ /etc/netdata/edit-config apps_groups.conf</code> (the default is <a href="https://github.com/netdata/netdata/blob/master/collectors/apps.plugin/apps_groups.conf" target="_blank">here</a>). The plugin internally builds a process tree (much like <code>ps fax</code> does), and groups processes together (evaluating both child and parent processes) so that the result is always a chart with a predefined set of dimensions (of course, only application groups found running are reported). The reported values are compatible with <code>top</code>, although the netdata plugin counts also the resources of exited children (unlike <code>top</code> which shows only the resources of the currently running processes). So for processes like shell scripts, the reported values include the resources used by the commands these scripts run within each timeframe.',
height: 1.5
},
'users': {
title: '使用者',
icon: '<i class="fas fa-user"></i>',
info: 'Per user statistics are collected using netdata\'s <code>apps.plugin</code>. This plugin walks through all processes 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.',
height: 1.5
},
'groups': {
title: '使用者群组',
icon: '<i class="fas fa-users"></i>',
info: 'Per user group statistics are collected using netdata\'s <code>apps.plugin</code>. This plugin walks through all processes 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.',
height: 1.5
},
'netdata': {
title: 'Netdata 监视',
icon: '<i class="fas fa-chart-bar"></i>',
info: 'netdata 本身与外挂程式的效能数据。'
},
'example': {
title: '范例图表',
info: '范例图表，展示外挂程式的架构之用。'
},
'cgroup': {
title: '',
icon: '<i class="fas fa-th"></i>',
info: '容器资源使用率指标。netdata 从 <b>cgroups</b> (<b>control groups</b> 的缩写) 中读取这些资讯，cgroups 是 Linux 核心的一个功能，做限制与计算程序集中的资源使用率 (CPU、记忆体、磁碟 I/O、网路...等等)。<b>cgroups</b> 与 <b>namespaces</b> (程序之间的隔离) 结合提供了我们所说的：<b>容器</b>。'
},
'cgqemu': {
title: '',
icon: '<i class="fas fa-th-large"></i>',
info: 'QEMU 虚拟机资源使用率效能指标。QEMU (Quick Emulator) 是自由与开源的虚拟机器平台，提供硬体虚拟化功能。'
},
'fping': {
title: 'fping',
icon: '<i class="fas fa-exchange-alt"></i>',
info: 'Network latency statistics, via <b>fping</b>. <b>fping</b> is a program to send ICMP echo probes to network hosts, similar to <code>ping</code>, but much better performing when pinging multiple hosts. fping versions after 3.15 can be directly used as netdata plugins.'
},
'httpcheck': {
title: 'Http Check',
icon: '<i class="fas fa-heartbeat"></i>',
info: 'Web Service availability and latency monitoring using HTTP checks. This plugin is a specialized version of the port check plugin.'
},
'memcached': {
title: 'memcached',
icon: '<i class="fas fa-database"></i>',
info: 'Performance metrics for <b>memcached</b>. Memcached is a general-purpose distributed memory caching system. It is often used to speed up dynamic database-driven websites by caching data and objects in RAM to reduce the number of times an external data source (such as a database or API) must be read.'
},
'monit': {
title: 'monit',
icon: '<i class="fas fa-database"></i>',
info: 'Statuses of checks in <b>monit</b>. Monit is a utility for managing and monitoring processes, programs, files, directories and filesystems on a Unix system. Monit conducts automatic maintenance and repair and can execute meaningful causal actions in error situations.'
},
'mysql': {
title: 'MySQL',
icon: '<i class="fas fa-database"></i>',
info: 'Performance metrics for <b>mysql</b>, the open-source relational database management system (RDBMS).'
},
'postgres': {
title: 'Postgres',
icon: '<i class="fas fa-database"></i>',
info: 'Performance metrics for <b>PostgresSQL</b>, the object-relational database (ORDBMS).'
},
'redis': {
title: 'Redis',
icon: '<i class="fas fa-database"></i>',
info: 'Performance metrics for <b>redis</b>. Redis (REmote DIctionary Server) is a software project that implements data structure servers. It is open-source, networked, in-memory, and stores keys with optional durability.'
},
'rethinkdbs': {
title: 'RethinkDB',
icon: '<i class="fas fa-database"></i>',
info: 'Performance metrics for <b>rethinkdb</b>. RethinkDB is the first open-source scalable database built for realtime applications'
},
'retroshare': {
title: 'RetroShare',
icon: '<i class="fas fa-share-alt"></i>',
info: 'Performance metrics for <b>RetroShare</b>. RetroShare is open source software for encrypted filesharing, serverless email, instant messaging, online chat, and BBS, based on a friend-to-friend network built on GNU Privacy Guard (GPG).'
},
'ipfs': {
title: 'IPFS',
icon: '<i class="fas fa-folder-open"></i>',
info: 'Performance metrics for the InterPlanetary File System (IPFS), a content-addressable, peer-to-peer hypermedia distribution protocol.'
},
'phpfpm': {
title: 'PHP-FPM',
icon: '<i class="fas fa-eye"></i>',
info: 'Performance metrics for <b>PHP-FPM</b>, an alternative FastCGI implementation for PHP.'
},
'portcheck': {
title: 'Port Check',
icon: '<i class="fas fa-heartbeat"></i>',
info: 'Service availability and latency monitoring using port checks.'
},
'postfix': {
title: 'postfix',
icon: '<i class="fas fa-envelope"></i>',
info: undefined
},
'dovecot': {
title: 'Dovecot',
icon: '<i class="fas fa-envelope"></i>',
info: undefined
},
'hddtemp': {
title: 'HDD Temp',
icon: '<i class="fas fa-thermometer-half"></i>',
info: undefined
},
'nginx': {
title: 'nginx',
icon: '<i class="fas fa-eye"></i>',
info: undefined
},
'apache': {
title: 'Apache',
icon: '<i class="fas fa-eye"></i>',
info: undefined
},
'lighttpd': {
title: 'Lighttpd',
icon: '<i class="fas fa-eye"></i>',
info: undefined
},
'web_log': {
title: undefined,
icon: '<i class="fas fa-file-alt"></i>',
info: 'Information extracted from a server log file. <code>web_log</code> plugin incrementally parses the server log file to provide, in real-time, a break down of key server performance metrics. For web servers, an extended log file format may optionally be used (for <code>nginx</code> and <code>apache</code>) offering timing information and bandwidth for both requests and responses. <code>web_log</code> plugin may also be configured to provide a break down of requests per URL pattern (check <a href="https://github.com/netdata/netdata/blob/master/conf.d/python.d/web_log.conf" target="_blank"><code>/etc/netdata/python.d/web_log.conf</code></a>).'
},
'named': {
title: 'named',
icon: '<i class="fas fa-tag"></i>',
info: undefined
},
'squid': {
title: 'squid',
icon: '<i class="fas fa-exchange-alt"></i>',
info: undefined
},
'nut': {
title: 'UPS',
icon: '<i class="fas fa-battery-half"></i>',
info: undefined
},
'apcupsd': {
title: 'UPS',
icon: '<i class="fas fa-battery-half"></i>',
info: undefined
},
'smawebbox': {
title: 'Solar Power',
icon: '<i class="fas fa-sun"></i>',
info: undefined
},
'fronius': {
title: 'Fronius',
icon: '<i class="fas fa-sun"></i>',
info: undefined
},
'stiebeleltron': {
title: 'Stiebel Eltron',
icon: '<i class="fas fa-thermometer-half"></i>',
info: undefined
},
'snmp': {
title: 'SNMP',
icon: '<i class="fas fa-random"></i>',
info: undefined
},
'go_expvar': {
title: 'Go - expvars',
icon: '<i class="fas fa-eye"></i>',
info: 'Statistics about running Go applications exposed by the <a href="https://golang.org/pkg/expvar/" target="_blank">expvar package</a>.'
},
'chrony': {
icon: '<i class="fas fa-clock"></i>',
info: 'chronyd parameters about the system’s clock performance.'
},
'couchdb': {
icon: '<i class="fas fa-database"></i>',
info: 'Performance metrics for <b><a href="https://couchdb.apache.org/">CouchDB</a></b>, the open-source, JSON document-based database with an HTTP API and multi-master replication.'
},
'beanstalk': {
title: 'Beanstalkd',
icon: '<i class="fas fa-tasks"></i>',
info: 'Provides statistics on the <b><a href="http://kr.github.io/beanstalkd/">beanstalkd</a></b> server and any tubes available on that server using data pulled from beanstalkc'
},
'rabbitmq': {
title: 'RabbitMQ',
icon: '<i class="fas fa-comments"></i>',
info: 'Performance data for the <b><a href="https://www.rabbitmq.com/">RabbitMQ</a></b> open-source message broker.'
},
'ceph': {
title: 'Ceph',
icon: '<i class="fas fa-database"></i>',
info: 'Provides statistics on the <b><a href="http://ceph.com/">ceph</a></b> cluster server, the open-source distributed storage system.'
},
'ntpd': {
title: 'ntpd',
icon: '<i class="fas fa-clock"></i>',
info: 'Provides statistics for the internal variables of the Network Time Protocol daemon <b><a href="http://www.ntp.org/">ntpd</a></b> and optional including the configured peers (if enabled in the module configuration). The module presents the performance metrics as shown by <b><a href="http://doc.ntp.org/current-stable/ntpq.html">ntpq</a></b> (the standard NTP query program) using NTP mode 6 UDP packets to communicate with the NTP server.'
},
'spigotmc': {
title: 'Spigot MC',
icon: '<i class="fas fa-eye"></i>',
info: 'Provides basic performance statistics for the <b><a href="https://www.spigotmc.org/">Spigot Minecraft</a></b> server.'
},
'unbound': {
title: 'Unbound',
icon: '<i class="fas fa-tag"></i>',
info: undefined
},
'boinc': {
title: 'BOINC',
icon: '<i class="fas fa-microchip"></i>',
info: 'Provides task counts for <b><a href="http://boinc.berkeley.edu/">BOINC</a></b> distributed computing clients.'
},
'w1sensor': {
title: '1-Wire Sensors',
icon: '<i class="fas fa-thermometer-half"></i>',
info: 'Data derived from <a href="https://en.wikipedia.org/wiki/1-Wire">1-Wire</a> sensors. Currently temperature sensors are automatically detected.'
},
'logind': {
title: 'Logind',
icon: '<i class="fas fa-user"></i>',
info: undefined
},
'powersupply': {
title: 'Power Supply',
icon: '<i class="fas fa-battery-half"></i>',
info: 'Statistics for the various system power supplies. Data collected from <a href="https://www.kernel.org/doc/Documentation/power/power_supply_class.txt">Linux power supply class</a>.'
}
};
// ----------------------------------------------------------------------------
// submenus
// information to be shown, just below each submenu
// information about the submenus
netdataDashboard.submenu = {
'web_log.squid_bandwidth': {
title: '频宽',
info: 'Bandwidth of responses (<code>sent</code>) by squid. This chart may present unusual spikes, since the bandwidth is accounted at the time the log line is saved by the server, even if the time needed to serve it spans across a longer duration. We suggest to use QoS (e.g. <a href="http://firehol.org/#fireqos" target="_blank">FireQOS</a>) for accurate accounting of the server bandwidth.'
},
'web_log.squid_responses': {
title: '回应',
info: 'Information related to the responses sent by squid.'
},
'web_log.squid_requests': {
title: 'requests',
info: 'Information related to the requests squid has received.'
},
'web_log.squid_hierarchy': {
title: 'hierarchy',
info: 'Performance metrics for the squid hierarchy used to serve the requests.'
},
'web_log.squid_squid_transport': {
title: 'transport'
},
'web_log.squid_squid_cache': {
title: '快取',
info: 'Performance metrics for the performance of the squid cache.'
},
'web_log.squid_timings': {
title: 'timings',
info: 'Duration of squid requests. Unrealistic spikes may be reported, since squid logs the total time of the requests, when they complete. Especially for HTTPS, the clients get a tunnel from the proxy and exchange requests directly with the upstream servers, so squid cannot evaluate the individual requests and reports the total time the tunnel was open.'
},
'web_log.squid_clients': {
title: 'clients'
},
'web_log.bandwidth': {
info: 'Bandwidth of requests (<code>received</code>) and responses (<code>sent</code>). <code>received</code> requires an extended log format (without it, the web server log does not have this information). This chart may present unusual spikes, since the bandwidth is accounted at the time the log line is saved by the web server, even if the time needed to serve it spans across a longer duration. We suggest to use QoS (e.g. <a href="http://firehol.org/#fireqos" target="_blank">FireQOS</a>) for accurate accounting of the web server bandwidth.'
},
'web_log.urls': {
info: 'Number of requests for each <code>URL pattern</code> defined in <a href="https://github.com/netdata/netdata/blob/master/conf.d/python.d/web_log.conf" target="_blank"><code>/etc/netdata/python.d/web_log.conf</code></a>. This chart counts all requests matching the URL patterns defined, independently of the web server response codes (i.e. both successful and unsuccessful).'
},
'web_log.clients': {
info: 'Charts showing the number of unique client IPs, accessing the web server.'
},
'web_log.timings': {
info: 'Web server response timings - the time the web server needed to prepare and respond to requests. This requires an extended log format and its meaning is web server specific. For most web servers this accounts the time from the reception of a complete request, to the dispatch of the last byte of the response. So, it includes the network delays of responses, but it does not include the network delays of requests.'
},
'mem.ksm': {
title: 'deduper (ksm)',
info: 'Kernel Same-page Merging (KSM) 效能监视，经由读取 <code>/sys/kernel/mm/ksm/</code> 下的档案而来。KSM 是在 Linux 核心 (自 2.6.32 版起) 内含的一种节省记忆体使用率重复资料删除功能。)。 KSM 服务程序 ksmd 会定期扫描记忆体区域，寻找正有资料要更新进来且相同资料存在的分页。KSM 最初是从 KVM 专案开发中而来，利用这种共用相同资料的机制，即可以让更多的虚拟机器放到记忆体中。另外，对许多会产生同样内容的应用程序来说，这个功能是相当有效益的。'
},
'mem.hugepages': {
info: 'Hugepages is a feature that allows the kernel to utilize the multiple page size capabilities of modern hardware architectures. The kernel creates multiple pages of virtual memory, mapped from both physical RAM and swap. There is a mechanism in the CPU architecture called "Translation Lookaside Buffers" (TLB) to manage the mapping of virtual memory pages to actual physical memory addresses. The TLB is a limited hardware resource, so utilizing a large amount of physical memory with the default page size consumes the TLB and adds processing overhead. By utilizing Huge Pages, the kernel is able to create pages of much larger sizes, each page consuming a single resource in the TLB. Huge Pages are pinned to physical RAM and cannot be swapped/paged out.'
},
'mem.numa': {
info: 'Non-Uniform Memory Access (NUMA) 是一种记忆体存取分隔设计，在 NUMA 之下，一个处理器存取自己管理的的记忆体，将比非自己管理的记忆体 (另一个处理器所管理的记忆体或是共用记忆体) 具有更快速的效能。在 <a href="https://www.kernel.org/doc/Documentation/numastat.txt" target="_blank">Linux 核心文件</a> 中有详细说明这些指标。'
},
'ip.ecn': {
info: '<a href="https://en.wikipedia.org/wiki/Explicit_Congestion_Notification" target="_blank">Explicit Congestion Notification (ECN)</a> is a TCP extension that allows end-to-end notification of network congestion without dropping packets. ECN is an optional feature that may be used between two ECN-enabled endpoints when the underlying network infrastructure also supports it.'
},
'netfilter.conntrack': {
title: 'connection tracker',
info: 'Netfilter connection tracker 效能指标。Connection tracker 会追踪这台主机上所有的连接，包括流入与流出。工作原理是将所有开启的连接都储存到资料库，以追踪网路、位址转换与连接目标。'
},
'netfilter.nfacct': {
title: 'bandwidth accounting',
info: 'The following information is read using the <code>nfacct.plugin</code>.'
},
'netfilter.synproxy': {
title: 'DDoS protection',
info: 'DDoS protection performance metrics. <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.'
},
'ipfw.dynamic_rules': {
title: 'dynamic rules',
info: 'Number of dynamic rules, created by correspondent stateful firewall rules.'
},
'system.softnet_stat': {
title: 'softnet',
info: function (os) {
if (os === 'linux')
return 'Statistics for CPUs SoftIRQs related to network receive work. Break down per CPU core can be found at <a href="#menu_cpu_submenu_softnet_stat">CPU / softnet statistics</a>. <b>processed</b> states the number of packets processed, <b>dropped</b> is the number packets dropped because the network device backlog was full (to fix them on Linux use <code>sysctl</code> to increase <code>net.core.netdev_max_backlog</code>), <b>squeezed</b> is the number of packets dropped because the network device budget ran out (to fix them on Linux use <code>sysctl</code> to increase <code>net.core.netdev_budget</code> and/or <code>net.core.netdev_budget_usecs</code>). More information about identifying and troubleshooting network driver related issues can be found at <a href="https://access.redhat.com/sites/default/files/attachments/20150325_network_performance_tuning.pdf" target="_blank">Red Hat Enterprise Linux Network Performance Tuning Guide</a>.';
else
return 'Statistics for CPUs SoftIRQs related to network receive work.';
}
},
'cpu.softnet_stat': {
title: 'softnet',
info: function (os) {
if (os === 'linux')
return 'Statistics for per CPUs core SoftIRQs related to network receive work. Total for all CPU cores can be found at <a href="#menu_system_submenu_softnet_stat">System / softnet statistics</a>. <b>processed</b> states the number of packets processed, <b>dropped</b> is the number packets dropped because the network device backlog was full (to fix them on Linux use <code>sysctl</code> to increase <code>net.core.netdev_max_backlog</code>), <b>squeezed</b> is the number of packets dropped because the network device budget ran out (to fix them on Linux use <code>sysctl</code> to increase <code>net.core.netdev_budget</code> and/or <code>net.core.netdev_budget_usecs</code>). More information about identifying and troubleshooting network driver related issues can be found at <a href="https://access.redhat.com/sites/default/files/attachments/20150325_network_performance_tuning.pdf" target="_blank">Red Hat Enterprise Linux Network Performance Tuning Guide</a>.';
else
return 'Statistics for per CPUs core SoftIRQs related to network receive work. Total for all CPU cores can be found at <a href="#menu_system_submenu_softnet_stat">System / softnet statistics</a>.';
}
},
'go_expvar.memstats': {
title: 'memory statistics',
info: 'Go runtime memory statistics. See <a href="https://golang.org/pkg/runtime/#MemStats" target="_blank">runtime.MemStats</a> documentation for more info about each chart and the values.'
},
'couchdb.dbactivity': {
title: 'db activity',
info: 'Overall database reads and writes for the entire server. This includes any external HTTP traffic, as well as internal replication traffic performed in a cluster to ensure node consistency.'
},
'couchdb.httptraffic': {
title: 'http traffic breakdown',
info: 'All HTTP traffic, broken down by type of request (<tt>GET</tt>, <tt>PUT</tt>, <tt>POST</tt>, etc.) and response status code (<tt>200</tt>, <tt>201</tt>, <tt>4xx</tt>, etc.)<br/><br/>Any <tt>5xx</tt> errors here indicate a likely CouchDB bug; check the logfile for further information.'
},
'couchdb.ops': {
title: 'server operations'
},
'couchdb.perdbstats': {
title: 'per db statistics',
info: 'Statistics per database. This includes <a href="http://docs.couchdb.org/en/latest/api/database/common.html#get--db">3 size graphs per database</a>: active (the size of live data in the database), external (the uncompressed size of the database contents), and file (the size of the file on disk, exclusive of any views and indexes). It also includes the number of documents and number of deleted documents per database.'
},
'couchdb.erlang': {
title: 'erlang statistics',
info: 'Detailed information about the status of the Erlang VM that hosts CouchDB. These are intended for advanced users only. High values of the peak message queue (>10e6) generally indicate an overload condition.'
},
'ntpd.system': {
title: 'system',
info: 'Statistics of the system variables as shown by the readlist billboard <code>ntpq -c rl</code>. System variables are assigned an association ID of zero and can also be shown in the readvar billboard <code>ntpq -c "rv 0"</code>. These variables are used in the <a href="http://doc.ntp.org/current-stable/discipline.html">Clock Discipline Algorithm</a>, to calculate the lowest and most stable offset.'
},
'ntpd.peers': {
title: 'peers',
info: 'Statistics of the peer variables for each peer configured in <code>/etc/ntp.conf</code> as shown by the readvar billboard <code>ntpq -c "rv <association>"</code>, while each peer is assigned a nonzero association ID as shown by <code>ntpq -c "apeers"</code>. The module periodically scans for new/changed peers (default: every 60s). <b>ntpd</b> selects the best possible peer from the available peers to synchronize the clock. A minimum of at least 3 peers is required to properly identify the best possible peer.'
}
};
// ----------------------------------------------------------------------------
// chart
// information works on the context of a chart
// Its purpose is to set:
//
// info: the text above the charts
// heads: the representation of the chart at the top the subsection (second level menu)
// mainheads: the representation of the chart at the top of the section (first level menu)
// colors: the dimension colors of the chart (the default colors are appended)
// height: the ratio of the chart height relative to the default
//
var cgroupCPULimitIsSet = 0;
var cgroupMemLimitIsSet = 0;
netdataDashboard.context = {
'system.cpu': {
info: function (os) {
void(os);
return 'CPU 使用率总表 (全部核心)。 当数值为 100% 时，表示您的 CPU 非常忙碌没有闲置空间。您可以在 <a href="#menu_cpu">CPU</a> 区段及以及 <a href="#menu_apps">应用程序</a> 区段深入了解每个核心与应用程序的使用情况。'
+ netdataDashboard.sparkline('<br/>请特别关注 <b>iowait</b> ', 'system.cpu', 'iowait', '%', '，如果它一直处于较高的情况，这表示您的磁碟是效能瓶颈，您的系统效能会明显降低。')
+ netdataDashboard.sparkline('<br/>另一个重要的指标是 <b>softirq</b> ', 'system.cpu', 'softirq', '%', '，若这个数值持续在较高的情况，很有可能是您的网路驱动部份有问题。');
},
valueRange: "[0, 100]"
},
'system.load': {
info: '目前系统负载，也就是指 CPU 使用情况或正在等待系统资源 (通常是 CPU 与磁碟)。这三个指标分别是 1、5、15 分钟。系统每 5 秒会计算一次。更多的资讯可以参阅 <a href="https://en.wikipedia.org/wiki/Load_(computing)" target="_blank">维基百科</a> 说明。',
height: 0.7
},
'system.io': {
info: function (os) {
var s = '磁碟 I/O 总计, 包含所有的实体磁碟。您可以在 <a href="#menu_disk">磁碟</a> 区段查看每一个磁碟的详细资讯，也可以在 <a href="#menu_apps">应用程序</a> 区段了解每一支应用程序对于磁碟的使用情况。';
if (os === 'linux')
return s + ' 实体磁碟指的是 <code>/sys/block</code> 中有列出，但是没有在 <code>/sys/devices/virtual/block</code> 的所有磁碟。';
else
return s;
}
},
'system.pgpgio': {
info: '从记忆体分页到磁碟的 I/O。通常是这个系统所有磁碟的总 I/O。'
},
'system.swapio': {
info: '所有的 Swap I/O. (netdata 会合并显示 <code>输入</code> 与 <code>输出</code>。如果图表中没有任何数值，则表示为 0。 - 您可以修改这一页的设定，让图表显示固定的维度。'
},
'system.pgfaults': {
info: '所有的 Page 错误. <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="#menu_apps">Applications Monitoring</a> section.'
},
'system.entropy': {
colors: '#CC22AA',
info: '<a href="https://en.wikipedia.org/wiki/Entropy_(computing)" target="_blank">熵 (Entropy)</a>，主要是用在密码学的乱数集区 (<a href="https://en.wikipedia.org/wiki//dev/random" target="_blank">/dev/random</a>)。如果熵的集区为空，需要乱数的程序可能会导致执行变慢 (这取决于每个程序使用的介面)，等待集区补充。在理想情况下，有高度熵需求的系统应该要具备专用的硬体装置 (例如 TPM 装置)。您也可以安装纯软体的方案，例如 <code>haveged</code>，通常这些方案只会使用在伺服器上。'
},
'system.forks': {
colors: '#5555DD',
info: '建立新程序的数量。'
},
'system.intr': {
colors: '#DD5555',
info: 'CPU 中断的总数。透过检查 <code>system.interrupts</code>，得知每一个中断的细节资讯。在 <a href="#menu_cpu">CPU</a> 区段提供每一个 CPU 核心的中断情形。'
},
'system.interrupts': {
info: 'CPU 中断的细节。在 <a href="#menu_cpu">CPU</a> 区段中，依据每个 CPU 核心分析中断。'
},
'system.softirqs': {
info: 'CPU softirqs 的细节。在 <a href="#menu_cpu">CPU</a> 区段中，依据每个 CPU 核心分析 softirqs。'
},
'system.processes': {
info: '系统程序。<b>running</b> 显示正在 CPU 中的程序。<b>Blocked</b> 显示目前被挡下无法进入 CPU 执行的程序，例如：正在等待磁碟完成动作，才能继续。'
},
'system.active_processes': {
info: '所有的系统程序。'
},
'system.ctxt': {
info: '<a href="https://en.wikipedia.org/wiki/Context_switch" target="_blank">Context Switches</a>，指 CPU 从一个程序、工作或是执行绪切换到另一个程序、工作或是执行绪。如果有许多程序或执行绪需要执行，但可以使用的 CPU 核心很少，即表示系统将会进行更多的 context switching 用来平衡它们所使用的 CPU 资源。这个过程需要大量的运算，因此 context switches 越多，整个系统就会越慢。'
},
'system.idlejitter': {
info: 'Idle jitter 是由 netdata 计算而得。当一个执行绪要求睡眠 (Sleep) 时，需要几个微秒的时间。当系统要唤醒它时，会量测它用了多少个微秒的时间。要求睡眠与实际睡眠时间的差异就是 <b>idle jitter</b>。这个数字在即时的环境中非常有用，因为 CPU jitter 将会影响服务的品质 (例如 VoIP media gateways)。'
},
'system.net': {
info: function (os) {
var s = '所有实体网路介面的总频宽。不包含 <code>lo</code>、VPN、网路桥接、IFB 装置、介面聚合 (Bond).. 等。将合并显示实体网路介面的频宽使用情况。';
if (os === 'linux')
return s + ' 实体网路介面是指在 <code>/proc/net/dev</code> 有列出，但不在 <code>/sys/devices/virtual/net</code> 里。';
else
return s;
}
},
'system.ip': {
info: 'IP 总流量。'
},
'system.ipv4': {
info: 'IPv4 总流量。'
},
'system.ipv6': {
info: 'IPv6 总流量。'
},
'system.ram': {
info: '系统随机存取记忆体 (也就是实体记忆体) 使用情况。'
},
'system.swap': {
info: '系统交换空间 (Swap) 记忆体使用情况。Swap 空间会在实体记忆体 (RAM) 已满的情况下使用。当系统记忆体已满但还需要使用更多记忆体情况下，系统记忆体中的比较没有异动的 Page 将会被移动到 Swap 空间 (通常是磁碟、磁碟分割区或是档案)。'
},
// ------------------------------------------------------------------------
// CPU charts
'cpu.cpu': {
commonMin: true,
commonMax: true,
valueRange: "[0, 100]"
},
'cpu.interrupts': {
commonMin: true,
commonMax: true
},
'cpu.softirqs': {
commonMin: true,
commonMax: true
},
'cpu.softnet_stat': {
commonMin: true,
commonMax: true
},
// ------------------------------------------------------------------------
// MEMORY
'mem.ksm_savings': {
heads: [
netdataDashboard.gaugeChart('Saved', '12%', 'savings', '#0099CC')
]
},
'mem.ksm_ratios': {
heads: [
function (os, id) {
void(os);
return '<div data-netdata="' + id + '"'
+ ' data-gauge-max-value="100"'
+ ' data-chart-library="gauge"'
+ ' data-title="Savings"'
+ ' data-units="percentage %"'
+ ' data-gauge-adjust="width"'
+ ' data-width="12%"'
+ ' data-before="0"'
+ ' data-after="-CHART_DURATION"'
+ ' data-points="CHART_DURATION"'
+ ' role="application"></div>';
}
]
},
'mem.pgfaults': {
info: 'A <a href="https://en.wikipedia.org/wiki/Page_fault" target="_blank">page fault</a> is a type of interrupt, called trap, raised by computer hardware when a running program accesses a memory page that is mapped into the virtual address space, but not actually loaded into main memory. If the page is loaded in memory at the time the fault is generated, but is not marked in the memory management unit as being loaded in memory, then it is called a <b>minor</b> or soft page fault. A <b>major</b> page fault is generated when the system needs to load the memory page from disk or swap memory.'
},
'mem.committed': {
colors: NETDATA.colors[3],
info: 'Committed 记忆体，是指程序分配到的所有记忆体总计。'
},
'mem.available': {
info: '可用记忆体是由核心估算而来，也就是使用者空间程序可以使用的 RAM 总量，而不会造成交换 (Swap) 发生。'
},
'mem.writeback': {
info: '<b>Dirty</b> 是等待写入磁碟的记忆体量。<b>Writeback</b> 是指有多少记忆体内容被主动写入磁碟。'
},
'mem.kernel': {
info: 'The total amount of memory being used by the kernel. <b>Slab</b> is the amount of memory used by the kernel to cache data structures for its own use. <b>KernelStack</b> is the amount of memory allocated for each task done by the kernel. <b>PageTables</b> is the amount of memory decicated to the lowest level of page tables (A page table is used to turn a virtual address into a physical memory address). <b>VmallocUsed</b> is the amount of memory being used as virtual address space.'
},
'mem.slab': {
info: '<b>Reclaimable</b> is the amount of memory which the kernel can reuse. <b>Unreclaimable</b> can not be reused even when the kernel is lacking memory.'
},
'mem.hugepages': {
info: 'Dedicated (or Direct) HugePages is memory reserved for applications configured to utilize huge pages. Hugepages are <b>used</b> memory, even if there are free hugepages available.'
},
'mem.transparent_hugepages': {
info: 'Transparent HugePages (THP) is backing virtual memory with huge pages, supporting automatic promotion and demotion of page sizes. It works for all applications for anonymous memory mappings and tmpfs/shmem.'
},
// ------------------------------------------------------------------------
// network interfaces
'net.drops': {
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="#menu_system_submenu_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.'
},
// ------------------------------------------------------------------------
// IP
'ip.inerrors': {
info: 'Errors encountered during the reception of IP packets. ' +
'<code>noroutes</code> (<code>InNoRoutes</code>) counts packets that were dropped because there was no route to send them. ' +
'<code>truncated</code> (<code>InTruncatedPkts</code>) counts packets which is being discarded because the datagram frame didn\'t carry enough data. ' +
'<code>checksum</code> (<code>InCsumErrors</code>) counts packets that were dropped because they had wrong checksum. '
},
'ip.tcpmemorypressures': {
info: 'Number of times a socket was put in <b>memory pressure</b> due to a non fatal memory allocation failure (the kernel attempts to work around this situation by reducing the send buffers, etc).'
},
'ip.tcpconnaborts': {
info: 'TCP connection aborts. <b>baddata</b> (<code>TCPAbortOnData</code>) happens while the connection is on <code>FIN_WAIT1</code> and the kernel receives a packet with a sequence number beyond the last one for this connection - the kernel responds with <code>RST</code> (closes the connection). <b>userclosed</b> (<code>TCPAbortOnClose</code>) happens when the kernel receives data on an already closed connection and responds with <code>RST</code>. <b>nomemory</b> (<code>TCPAbortOnMemory</code> happens when there are too many orphaned sockets (not attached to an fd) and the kernel has to drop a connection - sometimes it will send an <code>RST</code>, sometimes it won\'t. <b>timeout</b> (<code>TCPAbortOnTimeout</code>) happens when a connection times out. <b>linger</b> (<code>TCPAbortOnLinger</code>) happens when the kernel killed a socket that was already closed by the application and lingered around for long enough. <b>failed</b> (<code>TCPAbortFailed</code>) happens when the kernel attempted to send an <code>RST</code> but failed because there was no memory available.'
},
'ip.tcp_syn_queue': {
info: 'The <b>SYN queue</b> of the kernel tracks TCP handshakes until connections get fully established. ' +
'It overflows when too many incoming TCP connection requests hang in the half-open state and the server ' +
'is not configured to fall back to SYN cookies*. Overflows are usually caused by SYN flood DoS attacks ' +
'(i.e. someone sends lots of SYN packets and never completes the handshakes). ' +
'<b>drops</b> (or <code>TcpExtTCPReqQFullDrop</code>) is the number of connections dropped because the ' +
'SYN queue was full and SYN cookies were disabled. ' +
'<b>cookies</b> (or <code>TcpExtTCPReqQFullDoCookies</code>) is the number of SYN cookies sent because the ' +
'SYN queue was full.'
},
'ip.tcp_accept_queue': {
info: 'The <b>accept queue</b> of the kernel holds the fully established TCP connections, waiting to be handled ' +
'by the listening application. <b>overflows</b> (or <code>ListenOverflows</code>) is the number of ' +
'established connections that could not be handled because the receive queue of the listening application ' +
'was full. <b>drops</b> (or <code>ListenDrops</code>) is the number of incoming ' +
'connections that could not be handled, including SYN floods, overflows, out of memory, security issues, ' +
'no route to destination, reception of related ICMP messages, socket is broadcast or multicast.'
},
// ------------------------------------------------------------------------
// IPv4
'ipv4.tcpsock': {
info: 'The number of established TCP connections (known as <code>CurrEstab</code>). This is a snapshot of the established connections at the time of measurement (i.e. a connection established and a connection disconnected within the same iteration will not affect this metric).'
},
'ipv4.tcpopens': {
info: '<b>active</b> or <code>ActiveOpens</code> is the number of outgoing TCP <b>connections attempted</b> by this host.'
+ ' <b>passive</b> or <code>PassiveOpens</code> is the number of incoming TCP <b>connections accepted</b> by this host.'
},
'ipv4.tcperrors': {
info: '<code>InErrs</code> is the number of TCP segments received in error (including header too small, checksum errors, sequence errors, bad packets - for both IPv4 and IPv6).'
+ ' <code>InCsumErrors</code> is the number of TCP segments received with checksum errors (for both IPv4 and IPv6).'
+ ' <code>RetransSegs</code> is the number of TCP segments retransmitted.'
},
'ipv4.tcphandshake': {
info: '<code>EstabResets</code> is the number of established connections resets (i.e. connections that made a direct transition from <code>ESTABLISHED</code> or <code>CLOSE_WAIT</code> to <code>CLOSED</code>).'
+ ' <code>OutRsts</code> is the number of TCP segments sent, with the <code>RST</code> flag set (for both IPv4 and IPv6).'
+ ' <code>AttemptFails</code> is the number of times TCP connections made a direct transition from either <code>SYN_SENT</code> or <code>SYN_RECV</code> to <code>CLOSED</code>, plus the number of times TCP connections made a direct transition from the <code>SYN_RECV</code> to <code>LISTEN</code>.'
+ ' <code>TCPSynRetrans</code> shows retries for new outbound TCP connections, which can indicate general connectivity issues or backlog on the remote host.'
},
// ------------------------------------------------------------------------
// APPS
'apps.cpu': {
height: 2.0
},
'apps.mem': {
info: 'Real memory (RAM) used by applications. This does not include shared memory.'
},
'apps.vmem': {
info: 'Virtual memory allocated by applications. Please check <a href="https://github.com/netdata/netdata/tree/master/daemon#virtual-memory" target="_blank">this article</a> for more information.'
},
'apps.preads': {
height: 2.0
},
'apps.pwrites': {
height: 2.0
},
// ------------------------------------------------------------------------
// USERS
'users.cpu': {
height: 2.0
},
'users.mem': {
info: 'Real memory (RAM) used per user. This does not include shared memory.'
},
'users.vmem': {
info: 'Virtual memory allocated per user. Please check <a href="https://github.com/netdata/netdata/tree/master/daemon#virtual-memory" target="_blank">this article</a> for more information.'
},
'users.preads': {
height: 2.0
},
'users.pwrites': {
height: 2.0
},
// ------------------------------------------------------------------------
// GROUPS
'groups.cpu': {
height: 2.0
},
'groups.mem': {
info: 'Real memory (RAM) used per user group. This does not include shared memory.'
},
'groups.vmem': {
info: 'Virtual memory allocated per user group. Please check <a href="https://github.com/netdata/netdata/tree/master/daemon#virtual-memory" target="_blank">this article</a> for more information.'
},
'groups.preads': {
height: 2.0
},
'groups.pwrites': {
height: 2.0
},
// ------------------------------------------------------------------------
// NETWORK QoS
'tc.qos': {
heads: [
function (os, id) {
void(os);
if (id.match(/.*-ifb$/))
return netdataDashboard.gaugeChart('Inbound', '12%', '', '#5555AA');
else
return netdataDashboard.gaugeChart('Outbound', '12%', '', '#AA9900');
}
]
},
// ------------------------------------------------------------------------
// NETWORK INTERFACES
'net.net': {
mainheads: [
function (os, id) {
void(os);
if (id.match(/^cgroup_.*/)) {
var iface;
try {
iface = ' ' + id.substring(id.lastIndexOf('.net_') + 5, id.length);
}
catch (e) {
iface = '';
}
return netdataDashboard.gaugeChart('Received' + iface, '12%', 'received');
}
else
return '';
},
function (os, id) {
void(os);
if (id.match(/^cgroup_.*/)) {
var iface;
try {
iface = ' ' + id.substring(id.lastIndexOf('.net_') + 5, id.length);
}