Getting Access to your Flurry Exception Logs

Flurry won’t give you access to more than one 15 record page of your exception log!

If you take your unhandled exceptions seriously (we do), analyzing them regularly is a top priority. To take the tedium out of manually paging and downloading all the individual CSV exports, you can use the Internet’s Swiss Army Knife™, curl.

If you’re on Mac OS X, curl is already installed. On Windows you will need to download and install.

First, use curl to log in to Flurry, obtaining the session cookie for future requests:

<youremail> and <yourpassword> needs to be URL encoded:

$ /usr/bin/php -r 'echo urlencode("rob@domain.com")."\n";'
  rob%40domain.com

$ curl --cookie-jar ./flurry.jar \
  -d "loginEmail=<youremail>&loginPassword=<yourpassword>&rememberMe=true&__checkbox_rememberMe=true" \
  -k https://dev.flurry.com/secure/loginAction.do

• –cookie-jar stores the response cookie for later use
• -d sends the POST data
• -k turns off certificate verification

Grab the Project ID for your App by looking at the CSV download link from the Flurry Error listing page.

Now ask curl to repeatedly download each page of your exception log CSV export:

$ curl --cookie ./flurry.jar \
'http://dev.flurry.com/exceptionLogsCsv.do?projectID=<yourproject>&versionCut=versionsAll&intervalCut=allTime&direction=1&offset=[000-100:15]&pageSize=15' \
--output "exception#1.csv"

You’re ready to read those into iWork Numbers or Microsoft Excel one at a time, or you can go another step further and combine them all for a single exception log:

$ grep -h -v -e "^Timestamp" exception???.csv | sort > AllExceptions.csv

Now get on with tracking down your reported errors and uncaught exceptions.

Advertisement