I have a distributable workflow, loosely coordinated using Redis and Supervisord - redis is used in two fashions: firstly using its lists as queues, buffering the communication between the workers, and secondly as a store, counting and associating the usage with the items and the metadata entities (people, subjects, etc) of those items.
I have written a very small python logger, that pushes loglines directly onto a redis list, providing me with live updating abilities, as well as manual log file parsing. This is currently switched on for testing in the live repository.
Current code base is here: http://github.com/benosteen/UsageLogAnalysis - it has a good number of things hardcoded to the perculiarities of my log files and repository. However, as part of the PIRUS 2 project, I am turning this into an easily reusable codebase, adding in the ability to push out OpenURLs to PIRUS statistics gatherers.
Overview:
Loglines -- lpush'd to 'q:loglines'
workers - 'debot.py' - pulls lines from this queue and parses them up, separating them into 4 categories:
- Any hit by a recognised Bot or spider
- Any view or download made by a real person on an item in the repository
- Any 404, etc
- And anything else
and the lines are moved onto 4 (5) queues respectively, q:bothits, q:objectviews (and q:count simultaneously), q:fof, and q:other. I am using prefixes as a convention when working with Redis keys - "q:" will almost always be a queue of some sort. These four queues are consumed by loggers, who commit the logs to disc, segregated into their categories.
The q:count queue is consumed by a further worker called - count.py. This does a number of jobs, and is the part that actually does the analysis.
For each repository item logged event, it finds the ID of the item and also whether this was a download of an item's files. With my repository, both these facts are deducible from the URL itself.
Given the ID, it checks redis to see if this item has had its metadata analysed before. If it hasn't, it grabs the metadata for the item from the repositories index (hosted by an instance of Apache Solr) and starts to add connections between metadata entity and ID to the redis index:
eg say item "pid:1" has the simple metadata of author_name='Ben' and subjects='foo, bar'
create unique IDs from the text by hashing the text and prefix it with the type of the field they came from:
Prefixes:
- name => "n:"
- institution => "i:"
- faculty => "f:"
- subjects => "s:"
- keyphrases => "k:"
- content type => "type:"
- collection => "col:"
- thesis type => "tt:"
eg
>>> from hashlib import md5
>>> md5("Ben").hexdigest()
'092f2ba9f39fbc2876e64d12cd662f72'
So, the hashkey of the 'name' 'Ben' is 'n:092f2ba9f39fbc2876e64d12cd662f72'
Now to make the connections in Redis:
- Add ID to the set 'objectitems' - to keep track of all the IDs (SADD objectitems {ID})
- Set 'n:092f2....' to 'Ben' (so we can keep a reverse mapping)
- Add 'n:092f2...' to 'names' set (to make it clearer. KEYS n:* should return an equivalent set)
- Add 'n:092f2...' to 'e:{id}' eg "e:pid:1" - (e -> prefix for collections of entities. e:{id} is a set of all entities that occur in id)
- Add 'e:pid:1' to 'e:n:092f2....' (gathers a list of item ids in which this entity 'Ben' occurs in)
Repeat for any entity you wish to track.
To make this more truth-manageable, you should include the id of record with the text when you generate the hashkey. That way, 'Ben' appearing in one record will have a different key than 'Ben' occuring in another. The assertion that these two entities are the same can easily take place in a different set, (I'm using b: as the prefix for these bundles of asserted equivalence)
Once you have made these assertions, you can set about counting :)
Conventions for tracking hits:
d[v|d|o]:{id} - set of the dates on which {id} was viewed (v), downloaded from (d) or any other page action (o)
eg dv:pid:1 -> set of dates on which pid:1 had page views.
YYYY-MM-DD:{id}:[v|d|o] - set of IP clients that accessed a particular item on a given day - v,d,o as above
eg 2010-02-03:pid:1:d - set of IP clients that downloaded a file from pid:1 on 2010-02-03
t:views:{hashkey}, t:dls:{hashkey}, t:other:{hashkey}
Grand totals of views, downloads or other accesses on a given entity or id. Good for quick lookups.
Let's walk through an example: consider that a client of IP 1.2.3.4 visits the record page for this 'pid:1' on 2010-01-01:
ID = pid:1
Add the User Agent string ("mozilla... etc") to the 'ua:{IP}' set, to keep track of the fingerprints of the visitors.
Try to add the IP address to the set - in this case "2010-01-01:pid:1:v"
If the IP isn't already in this set (the client hasn't accessed this page already today) then:
- make sure that "2010-01-01" is a part of the 'dv:pid:1' set
- go through all the entities that are part of pid:1 (n:092... etc) and increment their totals by one.
- INCR t:views:n:092...
- INCR t:views:pid:1
Now, what about querying?
Say we wish to look up the activity on a given entity, say for 'Ben'?
First, find the hashkey(s) that exist that are equivalent - either directly using the simple md5sum hash, or by checking which bundles are for this entity.
You can get the grand totals by simply querying "t:views:key", "t:dls..." for each key and summing them together.
You can get more refined answers by getting the set of IDs that this entity is associated with, and querying that to gather all the daily IP sets for them, and summing the answer. This gives me a nice way to generate data suitable for a daily activity sparkline, like:
I have added another set of keys to the store, of the form 'geocode:{IP}' that record country code to IP address, which gives me a nice way to plot out graphs like the following also using the google chart API:
Python logging to Redis
This functionality is mainly in one file in the github repo: redislogger.py
As you can see, most of that file is taken up with a demonstration of how to invoke it! The file that holds the logging configuration which this demo uses is in logging.conf.example.
NB The usage analysis code and UI is very much a WIP
but, I just wanted to post quickly on the rough overview on how it is set up and working.
