AppResponse CLI Export Command Reference
The following table lists the available AppResponse CLI export commands and usage information.
Table 2: AppResponse CLI Export Commands
exportToGuru |
Usage:cliext exportToGuru [-h] [-g <granularity>] [-s <unix start time or date> & -e <unix end time or date>] [-i <time interval>] [-d <time duration(in mins)>] [-r <IN|OUT>] [-t <threshold>] [-a] [-n] [-l] |
||
-h |
displays this information (help) | ||
-x |
check available data | ||
-s <start time> |
export traffic data with this start time | ||
-e <end time> |
export traffic data with this end time | ||
-i <time interval> |
time interval of analysis from current time Recognized values: ‘Last Hour’ 'Last 6 hours' 'Yesterday' 'Last Week' 'Last Month' 'Last 6 Months' 'Last 12 Months' |
||
-d <time in mins> |
maximum time allowed per file Only multiples of granularity are allowed [Default: time interval of analysis] |
||
-g <granularity> |
granularity in minutes Available granularities are: 1(1 min) 5(5 min) 60(1 hour) 1440(1 day) Only data at the chosen granularity level are being displayed [Default: 5 min] |
||
-r <IN/OUT> |
"incoming"('IN') or outgoing"('OUT')—direction of traffic applicable only for exporting NetFlow data [Default is 'OUT'] Note: Use the IN option if the observing device acts as a destination instead of being a transit or source. On pure transit devices the sum of traffic in the IN direction is equal to the sum of traffic in OUT direction. Either one exports all the flows that traversed through the device. |
||
-t <threshold> |
exclude traffic less than a specific value [Default: 0 ("include all traffic")] Note: Use this option to reduce the number of flows considered by eliminating smaller flows. For example, you can eliminate traffic flows that are less than 1500 bps by using the option -t 1500. |
||
-a |
aggregate traffic by IP-IP-App [Default: aggregate traffic by IP-IP] |
||
-n |
collect data only from router NetFlow probes [Default: collect data from both router NetFlow probes and the AppResponse merged data (options '-n and '-l' combined)] |
||
-l |
collect only AppResponse "merged" data, i.e., data received from the router NetFlow probes, combined and deduplicated with data received at AppResponse data monitoring port [Default: collect data from both router NetFlow probes and the AppResponse merged data (options '-n and '-l' combined)] |
||
-v |
verbose; provides more detailed information of the script progress | ||
-b <sleep time> |
sleep time between database queries (in seconds Use this option (in combination with smaller duration times) to minimize the performance impact of the 'exportToGuru' script to the AppResponse appliance | ||
For example,cliext exportToGuru -g 5 -s '2007-07-25 15:16:05' -e '2007-07-25 16:15:55' -d 20 -r 'IN' -t 1500 -nor cliext exportToGuru -g 5 -i 'Yesterday' -t 1500 -a -l |
|||
clearExport |
Usage:cliext clearExport [-h] -l|-r [-p <string pattern>|-f <filename>] |
||
-h |
print usage message | ||
-l |
list contents of 'Export' directory | ||
-r |
remove contents of 'Export' directory | ||
-p <string> |
string pattern to match | ||
-f <filename> |
file name to match | ||
For example,cliext clearExport -l -p '1224008'or cliext clearExport -r -f myArchive.zip |