Get the list of all the processes that were running when such HTTP request was served.This has been the driving force to combine system with network monitoring, so that when system administrators see an increase in HTTP application response time, they can: In essence we see hosts, ports, protocols and flows, but we lack visibility on the process that did all that. With flow-based paradigm what we see is depicted below. The idea is very simple: we want to associate a process name with every network activity, and monitor the process resources (CPU, memory and I/O) used to carry on such activity. Our Vision: Combine System with Network Information
#Setup ntopng on centos 7 code#
We have therefore put our experimental code in the trash and started hacking on top of sysdig. We have lived once more the early ntop days when last May our friends at Draios have introduced sysdig and made all this mess below history. Early this year we have started the development of some experimental PF_RING kernel module extensions able to give ntop applications visibility of process activities, this in order to bind network traffic with a process name. Nevertheless we have decided to develop ntop, because there was no tool able to show on a simple way what was happening on our network.
When in 1998 we have started the development of the original ntop, there were many Unix tools for monitoring network traffic: ping, tcpdump, netstat, and many others.