Open kimececmuedu opened 9 years ago
Guide to Traffic Monitor, Agent Analyzer and GUI
Part 1 Traffic Monitor Traffic monitor is responsible for recording the traffic as packets pass through a physical machine.
This module can be started by typing the command line: (on each of the physical machine)
cd /home/ke/nf_test/; ./new_monitor.sh
But typically we do not invoke this manually, it's called by the agent analyzer in the jar file. But for debug purposes, we can run this tool along and check the traffic log file in: /home/ke/nf_test/traffic.log
The parameters involved in this module is the sampling rate of recording. This can be modified in the /home/ke/nf_test/new_monitor.sh.
Part 2 Agent Analyzer
This module is a jar file located in the same place as the first module, which is: /home/ke/nf_test/cloudman0.9.jar
When we want to invoke it, Make sure that we should first cd into the directory: /home/ke/nf_test/ This is very important as this jar file invokes the new_monitor.sh. If we call the jar file in other directory, the script can not be called successfully.
Part3 GUI
Currently, the version with most features is located at 10.1.0.13:/usr/share/tomcat/webapps/ROOT/cloudman/test.html
Kejiang can integrate it into our main page if we are satisfied with the GUI.
The most popular bugs during maintenance and its corresponding solution
We need to resolve different GUI for different trigger mechanisms