Showing posts with label talk. Show all posts
Showing posts with label talk. Show all posts

Thursday, 28 May 2009

The powah of the client side.

I have added some js to parse logs found on the viewed page and make a few simple graphs. (With the help of jquery and google chart)

The magical code can be seen here

http://www.wetgenes.com/js/wetlogs.js

and a link to an example log post can be found here

http://wetlogs.blogspot.com/2009/05/14391.html

Which is to say when you view a raw log file, your browser scans it and turns it into a pretty picture.

This is very shallow parsing but consider it an example of what could be done :)

Obviously it is limited in that it only looks at the current page and it's not very useful information but hey, if I throw in some daily leaderboards here for max amount of time spent online then I'm sure the users will love it :)

Maybe I'll just do a few things this way, it turns out that it is rather simple.

Tuesday, 26 May 2009

it rolls down stairs

At the moment any post title that is just a number is a raw log dump. All other posts are random blogs just like this one :)

The number is unix days, IE unixtime/(24*60*60) yes that means we really are only 14000 odd days into the world of tomorrow.

I think I will have to split up some of the raw log posts, just to be sure that they do not get too large when we add in more real action tracking. But it will still be just a number probably 14000.0 14000.1 and so on as needed.

I'm also going to put together some example code that will hit up this blog and pull down the logs, lua of course because lua is nice and lua is your friend.

You should then be able to modify this code to scan logs and mine for interesting data. I'll probably start with examples of graphs of total users online over time.


I wonder if google will tell me off for using blogger like this? :) Sorry working on a shoestring budget here and this will probably be the only archive of the logs I'm just going to delete them server side as we cant afford reasonable backup of such things.

It's just nice to publish this data for others to use and this ended up looking like the simplest option. Logs are usually all so top secret and we need to do things that everybody else is not doing if we want to stand a chance. So here we are.

You can guess at the format, but hey you know you can just read the source of the server that writes these out? Thats hardcore documentation that is, really hardcore, you are hardcore right? No? best wait for some examples then.