logging to a CSV or TSV file

2,073 views
Skip to first unread message

TonyMu

unread,
May 1, 2009, 10:16:55 AM5/1/09
to Fiddler
Hi,

I'd like to get Fiddler output in a CSV or TSV file so I can do some
offline filtering. Is FiddlerScript the only way to do this, or did I
miss an option in the UI? I'm looking to get IIS style logging to
include values like below for each request:

Protocol, Host, URL, Result, X-PROCESSINFO, X-CLIENTPORT, X-
TRANSFER-SIZE, X-CLIENTIP, X-HOSTIP, X-TTFB, X-TTLB

I'm using v2.2.2.0 beta. Also, if I write this in FiddlerScript, can
it be run against a SAZ that I've already collected, or does the
script have to run in real-time when the data is being captured?

TIA,

...TonyMu

EricLaw

unread,
May 1, 2009, 7:10:18 PM5/1/09
to Fiddler
If you right-click some sessions and choose Copy > Full Summary and
paste the result into Excel, you'll effectively get a CSV file.

Alternatively, you can just save as a SAZ file, rename it to .ZIP, and
open it. The index.html file in the root will give you an HTML view
of the session list.

Or, yes, you can trivially write some FiddlerScript to export/save in
any format you'd like. The "Log sessions to a database" example here:
http://www.fiddler2.com/fiddler/dev/scriptsamples.asp might be useful.

You can do any of this either live or against a loaded .SAZ file.

-Eric

bmilling

unread,
May 7, 2009, 4:13:43 PM5/7/09
to Fiddler
I am trying to do something quite similar and tried each of the
suggested solutions, but they do not work for me. Specially, the
performance data like TFB and TLB are not included in the export,
unless they were enabled at the time the session was captured. Isn't
that timing data stored in the saved session file, somewhere? Is
there an additional procedure required to export that data with the
rest of the full session information?

-Bob

On May 1, 7:10 pm, EricLaw <bay...@gmail.com> wrote:
> If you right-click some sessions and choose Copy > Full Summary and
> paste the result into Excel, you'll effectively get a CSV file.
>
> Alternatively, you can just save as a SAZ file, rename it to .ZIP, and
> open it.  The index.html file in the root will give you an HTML view
> of the session list.
>
> Or, yes, you can trivially write some FiddlerScript to export/save in
> any format you'd like.  The "Log sessions to a database" example here:http://www.fiddler2.com/fiddler/dev/scriptsamples.aspmight be useful.
>
> You can do any of this either live or against a loaded .SAZ file.
>
> -Eric
>
> On May 1, 7:16 am, TonyMu <tony.mu...@gmail.com> wrote:
>
>
>
> > Hi,
>
> > I'd like to get Fiddler output in a CSV or TSV file so I can do some
> > offline filtering.  Is FiddlerScript the only way to do this, or did I
> > miss an option in the UI?  I'm looking to get IIS style logging to
> > include values like below for each request:
>
> >     Protocol, Host, URL, Result, X-PROCESSINFO, X-CLIENTPORT, X-
> > TRANSFER-SIZE, X-CLIENTIP, X-HOSTIP, X-TTFB, X-TTLB
>
> > I'm using v2.2.2.0 beta.  Also, if I write this in FiddlerScript, can
> > it be run against a SAZ that I've already collected, or does the
> > script have to run in real-time when the data is being captured?
>
> > TIA,
>
> > ...TonyMu- Hide quoted text -
>
> - Show quoted text -

TonyMu

unread,
May 12, 2009, 3:29:49 PM5/12/09
to Fiddler
sample provided on a seperate thread:

http://groups.google.com/group/httpfiddler/browse_thread/thread/7466fbd8763e8ef5


On May 7, 4:13 pm, bmilling <bmilling...@gmail.com> wrote:
> I am trying to do something quite similar and tried each of the
> suggested solutions, but they do not work for me.  Specially, the
> performance data like TFB and TLB are not included in the export,
> unless they were enabled at the time the session was captured.  Isn't
> that timing data stored in the saved session file, somewhere?  Is
> there an additional procedure required to export that data with the
> rest of the full session information?
>
> -Bob
>
> On May 1, 7:10 pm, EricLaw <bay...@gmail.com> wrote:
>
>
>
> > If you right-click some sessions and choose Copy > Full Summary and
> > paste the result into Excel, you'll effectively get a CSV file.
>
> > Alternatively, you can just save as a SAZ file, rename it to .ZIP, and
> > open it.  The index.html file in the root will give you an HTML view
> > of the session list.
>
> > Or, yes, you can trivially write some FiddlerScript to export/save in
> > any format you'd like.  The "Log sessions to a database" example here:http://www.fiddler2.com/fiddler/dev/scriptsamples.aspmightbe useful.
>
> > You can do any of this either live or against a loaded .SAZ file.
>
> > -Eric
>
> > On May 1, 7:16 am, TonyMu <tony.mu...@gmail.com> wrote:
>
> > > Hi,
>
> > > I'd like to get Fiddler output in a CSV or TSV file so I can do some
> > > offline filtering.  Is FiddlerScript the only way to do this, or did I
> > > miss an option in the UI?  I'm looking to get IIS style logging to
> > > include values like below for each request:
>
> > >     Protocol, Host, URL, Result, X-PROCESSINFO, X-CLIENTPORT, X-
> > > TRANSFER-SIZE, X-CLIENTIP, X-HOSTIP, X-TTFB, X-TTLB
>
> > > I'm using v2.2.2.0 beta.  Also, if I write this in FiddlerScript, can
> > > it be run against a SAZ that I've already collected, or does the
> > > script have to run in real-time when the data is being captured?
>
> > > TIA,
>
> > > ...TonyMu- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
Reply all
Reply to author
Forward
0 new messages