Foglight Experience Viewer (FxV) URL Search Shortcuts

Jason here with the Quest Field Team. Ever need to have a direct link to replay a session in FxV or get right to a list of search results? This helpful template below will get you there! There is a great YouTube video showcasing this technology in action as well, hosted by our very own John Spirko.

(Please visit the site to view this video)

URLs
The *results.faces URLs will take you directly to the full-screen search results pages (search criteria hidden except for the summary at the top) while the other URLs will take you to the split search/results screen.
NOTE: Anything written in red MUST be a query parameter.

Common Time Parameters
lm = last minutes (lm=15); valid values are {1,5,15,30,60,120,240,480,1440,2880,4320}
sd = start date (sd=03/13/07)
st = start time (st=11:49)
tr = time range (tr=15); valid values are {1,5,15,30,60,120,240,480,1440,2880,4320}
et = exact times (et=yyyy-MM-dd'T'HH:mm:ss.SSSZ - yyyy-MM-dd'T'HH:mm:ss.SSSZ)
Example: et=2007-06-13T12:05:00.000-0600 - 2007-06-13T17:12:00.000-0600
You must specify a time range for the search. There are several ways to do this:
lm parameter only (search the last n minutes from “now”)
sd/st/tr parameters together (set the start date/time and the range)
et parameter only (two specific timestamps given that defines the range beginning/end)
Note: for the ‘et’ parameter time range; if a non-zero seconds value is given for the end time the end time will be rounded up to the next minute as the FxV GUI doesn’t support less than minute precision for searches. (Milliseconds currently ignored in general for this format)

Common Authentication Parameters
xloginx = login (xloginx=guest)
xpassx = password (xpassx=guest)
xforcex = force logout of open user session (xforcex=true)
It is valid to omit these authentication parameters; the standard FxV login prompt will appear before the search will be preformed if they are not given.
Other Common Parameters
s = use url search (s=1); this must be specified to trigger URL search
si = Session ID

Hit Search Parameters
sk = source keywords (content keywords)
ip = client ip
ii = interceptor id (monitor id)
ig = interceptor group (monitor group)
ti = html title
hm = http method
sv = web server
pt = path
ty = type
os = overall hit status
hc = http code
ht = hit filter

Hit Search Parameter Prefixes
rf = request field
qh = request header
sh = response header
ck = cookie
cf = custom field
mu = metric update
The above parameter prefixes are used like this (note that this is a change from previous releases which were actually broken):
rffieldname=fieldvalue
ckcookiename=cookievalue
(etc.)
For custom fields, the format for numeric custom fields is as follows:

cfFieldName=OperatorValue
for example:
cfMyField=>=20 (MyField >= 20)
cfMyField==0 (MyField = 0)
cfMyField=!=42.42 (MyField != 42.42)
For non-numeric fields, the operator is omitted:
cfMyNonNumericField=someValue
For metric updates (new in 5.0.2), the format is the same as custom fields however only numeric values are allowed.
cfMetricName=>=14 (MetricName>= 14)

Time Parameters available for Transaction Searches only

tm = time range mode (tm=SPAN); valid values are {START, STOP, SPAN, SPAN_NOW}

dd = timestamp date (dd=03/13/07); used with tm=SPAN only

tt = timestamp time (tt=11:49); used with tm=SPAN only

in = in progress/transactions to search (in=TRUE); valid values are {TRUE, FALSE, ANY}

For transaction searches, you must specify values for both the tm and the in parameters. Also, note the following restrictions on the in parameter:

1. If tm=STOP then in must be set to FALSE

2. if tm=SPAN_NOW then in must be set to TRUE

Transaction searches provide two additional options for specifying search time (in addition to the two "common" ones specified above):

tm parameter set to SPAN_NOW (search transactions in progress; no other time parameters should be specified)

tm/dd/tt parameters, with tm set to SPAN (search transactions in progress at the specified time)

Transaction Search Parameters

tf = Transaction Filter name (required)

xs = Transaction Status; valid values are {OK, ERROR, WARNING}

th = total hits (*)

hh = HTML hits (*)

he = HTML errors (*)

hw = HTML warnings (*)

te = total errors (*)

tw = total warnings (*)

(*) - the values for these parameters use the same format as the custom field values described early. For example:

th=>=17 (at least 17 total hits)

he==0 (0 html errors)

Transaction Search Prefixes

ev = event condition

cf = custom field

mu = metric update

The format of the ev parameters depends on the allow multiples setting defined for the transaction event. For events that do no allow multiples, the format is as follows:

evEventName=OCCURRENCE_SELECTION (where the valid values are OCCURRED, DID_NOT_OCCUR, DONT_CARE)

for example:

evMyStartEvent=OCCURRED

For events that do allow multiples, the format is as follows:

evEventName=OCCURREDOperatorValue

for example:

evMyRecurringEvent=OCCURRED>=3 (MyRecurringEvent occurred at least 3 times)

evMyRecurringEvent=OCCURRED=1 (MyRecurringEvent occurred exactly once)

 

custom fields and metric updates work exactly like they do in Hit Search as described above.

That's all for today...good luck and good monitoring!

Related
Recommended