The type of history search you want can be changed using the radio buttons at the very top.
The next choice is the time interval. There is a preset drop down menu or a specific date and time can be defined using the from radio button.
Next stage is the criteria you want to search by. Each variable has an explanation about the data it is expecting to help fill out this dialog box. The advanced text box allows you to enter advanced search criteria, see the examples below:
The advanced text box accepts boolean logic i.e. rtt>30 and ipto=19.19.19.2.
">" - Greater than not equal to
">=" - Greater than or equal
"<" - Less than not equal
"<=" - Less than or equal
"=" - Equal to
"!=" - Not equal to
Tags you can use are:
rtt
ipto
ipresp
sent_ttl |
The history search dialog for ping looks like the image below:
The type of history search you want can be changed using the radio buttons at the very top.
The next choice is the time interval. There is a preset drop down menu or a specific date and time can be defined using the from radio button.
Next stage is the criteria you want to search by. Each variable has an explanation about the data it is expecting to help fill out this dialog box. The advanced text box allows you to enter advanced search criteria, see the examples below:
The advanced text box accepts boolean logic i.e. rtt>30 and ipto=19.19.19.2.
">" - Greater than not equal to
">=" - Greater than or equal
"<" - Less than not equal
"<=" - Less than or equal
"=" - Equal to
"!=" - Not equal to
Tags you can use are:
maxloss
endloss
endms
maxms
numhops
endip
endname
So to specify all traceroutes with an endloss greater than 30 and endms less than 50 you would put:
endloss>30 and endms<50
Wildcards are supported for the endip and endname ONLY (i.e. not for pings). This means you can do endname=*.visualware.com. |
|
