teastats web log analysis Code
Status: Pre-Alpha
Brought to you by:
james_time4tea
| File | Date | Author | Commit |
|---|---|---|---|
| lib | 2007-12-18 | james_time4tea | [r79] tidying up project a bit... |
| src | 2007-12-18 | james_time4tea | [r81] tidying up project |
| COMPILE.txt | 2006-05-07 | james_time4tea | [r20] |
| README.txt | 2006-08-14 | james_time4tea | [r26] show how to access simple attribute. |
| build.xml | 2007-07-24 | james_time4tea | [r70] can now save & reload more reliably. |
| teastats.iml | 2007-12-18 | james_time4tea | [r79] tidying up project a bit... |
| teastats.ipr | 2007-12-18 | james_time4tea | [r80] tidying up project |
Teastats web log analyser. This software is released under GPL v2. IMPORTANT - You need to supply your own log files. Place one in src/test-files/access.log before building & running tests, as they expect to find something there. contact me (james_time4tea@users.sourceforge.net) if you have any requests, ideas or would like to contribute. Current Things To Do -------------------- 0. totally re-do the way that we keep stats for sessions... suggestions welcome. 1. Add Date to Repository so we can save files day by day 2. Get some kind of composition working for Hitters so we can load multiple dates into a single one. 3. Get them to relate what kind of data they hold- this is particularly important for time based, and geo information. 4. Site generation - initially expect this to be very simple - and a basic basic freemarker one is there now. 5. Proxy detection 6. Use cookies to detect sessions, not IP addresses - (may be related to proxy requirement) 7. Maybe some kind of mule interaction, so we can turn the processing model around, so we are message based. 8. Site mapping - show how users navigate through site. - Nice to have something (free, but) like yfiles for this? 9. Allow certain hitters to specify their own sort order (where it knows the keys already) 10. Spruce up the charts. 11. Get some nice css for any site we generate! Why? ----- 1. I wanted a way look at my website usage. 2. I objected to awstats because of the way it was written. 3. webalyzer is years old. 4. google analytics sign up is closed. - plus maybe you don't want to send all your users there too, giving google all that knowledge about your site, and your customers web habits. 5. it can't be that hard! (tm) - how many projects started that way