tc QoS classes for all interfaces.
If you also use FireQOS it will collect interface and class names.
There is a shell helper for this (all parsing is done by the plugin in
C code - this shell script is just a configuration for the command to run to get
The source of the tc plugin is here. It is somewhat complex, because a state machine was needed to keep track of all the
tc classes, including the pseudo classes tc dynamically creates.
You can see a live demo here.
One category of metrics missing in Linux monitoring, is bandwidth consumption for each open socket (inbound and outbound traffic). So, you cannot tell how much bandwidth your web server, your database server, your backup, your ssh sessions, etc are using.
To solve this problem, the most adventurous Linux monitoring tools install kernel modules to capture all traffic, analyze it and provide reports per application. A lot of work, CPU intensive and with a great degree of risk (due to the kernel modules involved which might affect the stability of the whole system). Not to mention that such solutions are probably better suited for a core linux router in your network.
Others use NFACCT, the netfilter accounting module which is already part of the Linux firewall. However, this would require configuring a firewall on every system you want to measure bandwidth (just FYI, I do install a firewall on every server - and I strongly advise you to do so too - but configuring accounting on all servers seems overkill when you don't really need it for billing purposes).
There is however a much simpler approach.
One of the features the Linux kernel has, but it is rarely used, is its ability to apply QoS on traffic. Even most interesting is that it can apply QoS to both inbound and outbound traffic.
QoS is about 2 features:
Classification is the process of organizing traffic in groups, called classes. Classification can evaluate every aspect of network packets, like source and destination ports, source and destination IPs, netfilter marks, etc.
When you classify traffic, you just assign a label to it. Of course classes have some properties themselves (like queuing mechanisms), but let's say it is that simple: a label. For example I call
web servertraffic, the traffic from my server's tcp/80, tcp/443 and to my server's tcp/80, tcp/443, while I call
web surfingall other tcp/80 and tcp/443 traffic. You can use any combinations you like. There is no limit.
Apply traffic shaping rules to these classes
Traffic shaping is used to control how network interface bandwidth should be shared among the classes. Normally, you need to do this, when there is not enough bandwidth to satisfy all the demand, or when you want to control the supply of bandwidth to certain services. Of course classification is sufficient for monitoring traffic, but traffic shaping is also quite important, as we will explain in the next section.
Why you want QoS
Monitoring the bandwidth used by services
Netdata provides wonderful real-time charts, like this one (wait to see the orange
Ensure sensitive administrative tasks will not starve for bandwidth
Have you tried to ssh to a server when the network is congested? If you have, you already know it does not work very well. QoS can guarantee that services like ssh, dns, ntp, etc will always have a small supply of bandwidth. So, no matter what happens, you will be able to ssh to your server and DNS will always work.
Ensure administrative tasks will not monopolize all the bandwidth
Services like backups, file copies, database dumps, etc can easily monopolize all the available bandwidth. It is common for example a nightly backup, or a huge file transfer to negatively influence the end-user experience. QoS can fix that.
Ensure each end-user connection will get a fair cut of the available bandwidth.
Several QoS queuing disciplines in Linux do this automatically, without any configuration from you. The result is that new sockets are favored over older ones, so that users will get a snappier experience, while others are transferring large amounts of traffic.
Protect the servers from DDoS attacks.
When your system is under a DDoS attack, it will get a lot more bandwidth compared to the one it can handle and probably your applications will crash. Setting a limit on the inbound traffic using QoS, will protect your servers (throttle the requests) and depending on the size of the attack may allow your legitimate users to access the server, while the attack is taking place.
Using QoS together with a SYNPROXY will provide a great degree of protection against most DDoS attacks. Actually when I wrote that article, a few folks tried to DDoS the Netdata demo site to see in real-time the SYNPROXY operation. They did not do it right, but anyway a great deal of requests reached the Netdata server. What saved Netdata was QoS. The Netdata demo server has QoS installed, so the requests were throttled and the server did not even reach the point of resource starvation. Read about it here.
On top of all these, QoS is extremely light. You will configure it once, and this is it. It will not bother you again and it will not use any noticeable CPU resources, especially on application and database servers.
- ensure administrative tasks (like ssh, dns, etc) will always have a small but guaranteed bandwidth. So, no matter what happens, I will be able to ssh to my server and DNS will work.
- ensure other administrative tasks will not monopolize all the available bandwidth. So, my nightly backup will not hurt my users, a developer that is copying files over the net will not get all the available bandwidth, etc.
- ensure each end-user connection will get a fair cut of the available bandwidth.
Once traffic classification is applied, we can use netdata to visualize the bandwidth consumption per class in real-time (no configuration is needed for Netdata - it will figure it out).
QoS, is extremely light. You will configure it once, and this is it. It will not bother you again and it will not use any noticeable CPU resources, especially on application and database servers.
This is QoS from a home linux router. Check these features:
- It is real-time (per second updates)
- QoS really works in Linux - check that the
backgroundtraffic is squeezed when
QoS in Linux?
tc is probably the most undocumented, complicated and unfriendly command in Linux.
For example, do you know that for matching a simple port range in
tc, e.g. all the high ports, from 1025 to 65535 inclusive, you have to match these:
Qos Configuration with FireHOL
With FireQOS, it is really simple for everyone to use QoS in Linux. Just install the package
firehol. It should already be available for your distribution. If not, check the FireHOL Installation Guide. After that, you will have the
fireqos command which uses a configuration like the following
/etc/firehol/fireqos.conf, used at the Netdata demo site:
# configure the Netdata ports
interface eth0 world bidirectional ethernet balanced rate 50Mbit
class dns commit 1Mbit
class ssh commit 2Mbit
class rsync commit 2Mbit max 10Mbit
class web_server commit 40Mbit
class nms commit 1Mbit
match input src 10.2.3.5
Nothing more is needed. You just run
fireqos start to apply this configuration, restart Netdata and you have real-time visualization of the bandwidth consumption of your applications. FireQOS is not a daemon. It will just convert the configuration to
tc commands. It will run them and it will exit.
IMPORTANT: If you copy this configuration to apply it to your system, please adapt the speeds - experiment in non-production environments to learn the tool, before applying it on your servers.
And this is what you are going to get:
QoS Configuration with tc
First, setup the tc rules in rc.local using commands to assign different QoS markings to different classids. You can see one such example in github issue #4563.
Then, map the classids to names by creating
/etc/iproute2/tc_cls. For example:
Add the following configuration option in
enable show all classes and qdiscs for all interfaces = yes
/etc/netdata/tc-qos-helper.conf with this content:
Please note, that by default Netdata will enable monitoring metrics only when they are not zero. If they are constantly zero they are ignored. Metrics that will start having values, after Netdata is started, will be detected and charts will be automatically added to the dashboard (a refresh of the dashboard is needed for them to appear though). Set
yes for a chart instead of
auto to enable it permanently. You can also set the
enable zero metrics option to
yes in the
[global] section which enables charts with zero metrics for all internal Netdata plugins.