tags:

views:

100

answers:

1

I received a long Fiddler trace (with a complicated scenario) and need to correlate the requests with application logs.

Unfortunately, while Fiddler displays the requests chronologically, it doesn't display the timestamps of the request. To access that information (which is recorded) I have to right-click each line and look in the pop-up window with the properties. This is very time-consuming when having to comb through hundreds of lines. Looking at the raw capture data is not much better as each request has its own file and I do need the Fiddler interface.

Pedantic note: I'm aware there isn't a single timestamp to show (below are all the timestamps that are recorded). ClientConnected would be fine (or any other, as long as it's the same, that allows me to correlate the logs visually).

Thanks.

== TIMING INFO ============
ClientConnected:        10:32:57:8906
ClientDoneRequest:      10:32:57:8906
Gateway Determination:  0ms
DNS Lookup:         0ms
TCP/IP Connect:         0ms
ServerGotRequest:       10:32:57:9062
ServerBeginResponse:    10:32:58:2812
ServerDoneResponse: 10:32:58:2884
ClientBeginResponse:    10:32:58:2900
ClientDoneResponse: 10:32:58:2912
+3  A: 

This is very easy to do in Fiddler: click Rules > Customize Rules.

Inside the class Handlers, add the following script code:

public static BindUIColumn("BeginRequestTime", 60)
function BeginRequestTime(oS: Session)
{
    if (oS.Timers != null)
    {
        return oS.Timers.ClientBeginRequest.ToString();     
    }
    return String.Empty;
}

Then, simply reload your SAZ file.

EricLaw -MSFT-
Sorry for the delay, I was off. Just tried it and found that ClientBeginRequest was not available as a property for some reason (it was failing compilation) but ClientDoneRequest was and it's equally fine for my purpose so I'll mark this as the answer. Thanks!
wishihadabettername
If ClientBeginRequest isn't available, you're using an outdated version. Please upgrade. :-) thanks!
EricLaw -MSFT-