Advanced Search

Enter a boolean search phrase.

Recognised fields: ip, sid, dns, cc, isp, recordid, testto,plus fields from plugins - eg: speed:dspeed, voip:jitter, route:hops

For a full list of available metrics click here.

Examples

[gbl:ip=1.2.3.4 and sid=*idname]

gbl can be used to target all results in the database for a given time period. This example would find all results that orginated at the IP 1.2.3.4 with a Session ID that ended in idname.

[voip:jitter>=2 and djitter>=2]

Results can also be targetted. In the example above the filter would return only VoIP results that had an upstream and downstream jitter of greater than or equal to 2ms

[voip:jitter>=2 and djitter>=2][act.dspeed<10000 or uspeed<10000]

When filtering more than one test type use separate square brackets, as shown above. As well as VoIP this example also filters Quality results with either a download or upload speed of less than 10,000 Kbps (10Mbps)

[voip:jitter>=2 and djitter>=2 and testto=test.visualware.com]

Specifying gbl within a test type bracket will apply it to just that test type. This example will filter the VoIP resulst and also ensure the test to target was test.visualware.com.

[gbl:sid=BCS][voip:jitter>=2 and djitter>=2 and testto=test.visualware.com]

This example would find all results across all tests regardless of checkboxes checked that matched a session ID of BCS. The VoIP results found would NOT obey the filters as gbl overrides. Instead you'd have to use the statement below:

[voip:jitter>=2 and djitter>=2 and testto=test.visualware.com and sid=BCS]