add proc_net_netstat charts info (#11554)
Co-authored-by: Vladimir Kobal <vlad@prokk.net>
Ilya Mashchenko committed
Sep 23, 2021 at 10:38 UTC
c30194f00b259d20d3dd22dbdfa02307f8964144
1 file changed
+69
-4
web/gui/dashboard_info.js
+69
-4
@@ -734,7 +734,23 @@ netdataDashboard.submenu = {
734
},
735
736
'ip.ecn': {
737
- 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.'
737
+ info: '<a href="https://en.wikipedia.org/wiki/Explicit_Congestion_Notification" target="_blank">Explicit Congestion Notification (ECN)</a> '+
738
+ 'is an extension to the IP and to the TCP that allows end-to-end notification of network congestion without dropping packets. '+
739
+ 'ECN is an optional feature that may be used between two ECN-enabled endpoints when '+
740
+ 'the underlying network infrastructure also supports it.'
741
+ },
742
+
743
+ 'ip.multicast': {
744
+ info: '<a href="https://en.wikipedia.org/wiki/Multicast" target="_blank">IP multicast</a> is a technique for '+
745
+ 'one-to-many communication over an IP network. '+
746
+ 'Multicast uses network infrastructure efficiently by requiring the source to send a packet only once, '+
747
+ 'even if it needs to be delivered to a large number of receivers. '+
748
+ 'The nodes in the network take care of replicating the packet to reach multiple receivers only when necessary.'
749
+ },
750
+ 'ip.broadcast': {
751
+ info: 'In computer networking, '+
752
+ '<a href="https://en.wikipedia.org/wiki/Broadcasting_(networking)" target="_blank">broadcasting</a> refers to transmitting a packet that will be received by every device on the network. '+
753
+ 'In practice, the scope of the broadcast is limited to a broadcast domain.'
754
},
755
756
'netfilter.conntrack': {
@@ -1314,9 +1330,58 @@ netdataDashboard.context = {
1330
1331
'ip.inerrors': {
1332
info: 'Errors encountered during the reception of IP packets. ' +
1317
- '<code>noroutes</code> (<code>InNoRoutes</code>) counts packets that were dropped because there was no route to send them. ' +
1318
- '<code>truncated</code> (<code>InTruncatedPkts</code>) counts packets which is being discarded because the datagram frame didn\'t carry enough data. ' +
1319
- '<code>checksum</code> (<code>InCsumErrors</code>) counts packets that were dropped because they had wrong checksum. '
1333
+ '<b>noroutes</b> (<code>InNoRoutes</code>) counts packets that were dropped because there was no route to send them. ' +
1334
+ '<b>truncated</b> (<code>InTruncatedPkts</code>) counts packets which is being discarded because the datagram frame didn\'t carry enough data. ' +
1335
+ '<b>checksum</b> (<code>InCsumErrors</code>) counts packets that were dropped because they had wrong checksum. '
1336
+ },
1337
+
1338
+ 'ip.mcast': {
1339
+ info: 'Total multicast traffic in the system.'
1340
+ },
1341
+
1342
+ 'ip.mcastpkts': {
1343
+ info: 'Total transferred multicast packets in the system.'
1344
+ },
1345
+
1346
+ 'ip.bcast': {
1347
+ info: 'Total broadcast traffic in the system.'
1348
+ },
1349
+
1350
+ 'ip.bcastpkts': {
1351
+ info: 'Total transferred broadcast packets in the system.'
1352
+ },
1353
+
1354
+ 'ip.ecnpkts': {
1355
+ info: 'Total number of received IP packets with ECN bits set in the system. '+
1356
+ '<b>CEP</b> - congestion encountered. '+
1357
+ '<b>NoECTP</b> - non ECN-capable transport. '+
1358
+ '<b>ECTP0</b> and <b>ECTP1</b> - ECN capable transport.'
1359
+ },
1360
+
1361
+ 'ip.tcpreorders': {
1362
+ info: 'TCP prevents out-of-order packets by either sequencing them in the correct order or by requesting the retransmission of out-of-order packets. '+
1363
+ '<b>Timestamp</b> - detected re-ordering using the timestamp option. '+
1364
+ '<b>SACK</b> - detected re-ordering using Selective Acknowledgment algorithm. '+
1365
+ '<b>FACK</b> - detected re-ordering using Forward Acknowledgment algorithm. '+
1366
+ '<b>Reno</b> - detected re-ordering using Fast Retransmit algorithm.'
1367
+ },
1368
+
1369
+ 'ip.tcpofo': {
1370
+ info: 'TCP maintains an out-of-order (OOO) queue to keep the OOO packets in the TCP communication. '+
1371
+ '<b>InQueue</b> - the TCP layer receives an OOO packet and has enough memory to queue it. '+
1372
+ '<b>Dropped</b> - the TCP layer receives an OOO packet but does not have enough memory, so drops it. '+
1373
+ '<b>Merged</b> - the received OOO packet has an overlay with the previous packet. '+
1374
+ 'The overlay part will be dropped. All these packets will also be counted into <b>InQueue</b>. '+
1375
+ '<b>Pruned</b> - packets dropped from out-of-order queue because of socket buffer overrun.'
1376
+ },
1377
+
1378
+ 'ip.tcpsyncookies': {
1379
+ info: '<a href="https://en.wikipedia.org/wiki/SYN_cookies" target="_blank">SYN cookies</a> are used to mitigate SYN flood. '+
1380
+ '<b>Received</b> - after sending a SYN cookie, it came back to us and passed the check. '+
1381
+ '<b>Sent</b> - an application was not able to accept a connection fast enough, so the kernel could not store '+
1382
+ 'an entry in the queue for this connection. Instead of dropping it, it sent a SYN cookie to the client. '+
1383
+ '<b>Failed</b> - the MSS decoded from the SYN cookie is invalid. When this counter is incremented, '+
1384
+ 'the received packet won’t be treated as a SYN cookie.'
1385
},
1386
1387
'ip.tcpmemorypressures': {