FlashComGuru.com - The Original Flash Video, Flash Media Server and Flash Platform Resource: Using Microsoft Logparser to process FMS2 logs

Using Microsoft Logparser to process FMS2 logs

Posted At : May 28, 2006 7:49 PM | Posted By : Stefan Richter | Related Categories: Tools

I just had a quick play with Microsoft's Logparser tool and boy it's a powerful piece of kit. I was able to quickly gather some log data using a SQL-like syntax. For example this piece of code parses all access logs of my FMS server, selects all cs-bytes fields where the event equals 'play' and lists them in the console window:

logparser "SELECT cs-bytes FROM 'C:\Program Files\Macromedia\Flash Media Server\logs\access*.log' where x-event='play'" -i:W3C

Ok, this query makes little sense but I guess it gives an idea of what can be done.

Logparser can not only output to text files but can also generate HTML reports, charts and even submit to a database (logging) server.

I guess all we need to do is figure out the syntax for meaningful queries and reports... Post in the comments if you can come up with anything. Things such as 'how much data has xyz application consumed' or 'how many users have logged on to this app in the last 2 weeks' would be useful starting points.

Download Logparser 2.2

Comments ( 4 ) |

Print |

Email This |

del.icio.us | 3781 Views

Sawmill Adds Support for Flash Media Server Logs (July 19, 2007)

Comments

[Add Comment]

Thanks for posting this!

After a bit of playing I've managed to call the com version of Logparser from an asp.net page and get queries printed out in the browser. Will post some queries soon.

# Posted By John B | 6/2/06 10:16 AM

Nice ! John, please post some queries and if possible the code for your asp.net page!

Thanks!

D.

# Posted By Dimitri | 8/3/06 4:18 PM

Log parser 2.2 seems to have a problem, however, with FMS2 W3C logs that are put out by Akamai's logging solution. It has trouble parsing them and frequently indicates that a "Log row is too long". I am trying to identify why, but have not discovered the root cause.

# Posted By EricS | 7/2/07 6:37 PM

I figured out the issue that was causing the FMS2 log files (from Akamai) to break logparser2.2. The #Fields line in the log file has each field (x-event, x-category, ..., etc.) space separated. the actual fields below with the data are tab separated, so if you use the -separator:tab you will get an row too long error on line 1, if you use 'space', you get the row too long error on the rest of the log file. So before I fed the log file to logparser I separated the #Fields line using tabs instead of spaces. it seems to have worked.

# Posted By Zed M. | 11/19/08 9:30 PM

[Add Comment]