Apache CLF access log format to CSV converter

#(see sample) $ cat x | perl -pe 'BEGIN{ print "TIME;...\n"; } s!(\S+) - (\S+) - \[(\d\d)/(\S\S\S)/(\S+):(\d\d):(\d\d:\d\d) \S+\] "(\S+) (.*/)(\S+)(?:\.([^?]*)(\?\S*)?) HTTP/\S+" (\d+) (\S+)!$3-$4-$5 $6:$7;$6;$2;$1;$8;$13;1;$14;$11;$10;$9;$12;!' > x.csv
- excel date compatible with a separate hour field - added a fixed 1 for easier request counter aggregation - split URL in directory, filename, fileext, query - used with tomcat valve with response bytes replaced by elapsed time
Sample Output
cat  access.log | perl -pe 'BEGIN{ print "TIME;HOUR;USER;HOST;METHOD;STATUS;REQ;COST;TYPE;PAGE;PATH;QUERY\n"; } s!(\S+) - (\S+) - \[(\d\d)/(\S\S\S)/(\S+):(\d\d):(\d\d:\d\d) \S+\] "(\S+) (.*/)(\S+)(?:\.([^?]*)(\?\S*)?) HTTP/\S+" (\d+) (\S+)!$3-$4-$5 $6:$7;$6;$2;$1;$8;$13;1;$14;$11;$10;$9;$12;!' > access.csv

$ head access.log - x2 - [07/Feb/2012:12:56:06 -0200] "GET /pmp/faces/jspx/MainWindow/Header.jspx HTTP/1.1" 200 0,010 - x2 - [07/Feb/2012:12:56:06 -0200] "GET /pmp/faces/jspx/MainWindow/Header/SearchDevice.jspx HTTP/1.1" 200 0,198 - x2 - [07/Feb/2012:12:56:06 -0200] "GET /pmp/faces/jspx/MainWindow/Panel.jspx HTTP/1.1" 200 0,012

$ head access.csv

07-Feb-2012 12:56:06;12;x2;;GET;200;1;0,010;jspx;Header;/pmp/faces/jspx/MainWindow/;;
07-Feb-2012 12:56:06;12;x2;;GET;200;1;0,198;jspx;SearchDevice;/pmp/faces/jspx/MainWindow/Header/;;
07-Feb-2012 12:56:06;12;x2;;GET;200;1;0,012;jspx;Panel;/pmp/faces/jspx/MainWindow/;;
07-Feb-2012 12:56:06;12;x2;;GET;200;1;0,024;jspx;WorkArea;/pmp/faces/jspx/MainWindow/Panel/;;

By: hute37
2012-02-10 16:58:50

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: