[Sigia-l] C+S: search logging dilemma

[Billie Mandel]

Hi everyone - 
 
I have just found out something quite disturbing about the Intranet I
work on - it has no search logs.  At all.  I had assumed that Apache
must be logging them, and that we just weren't importing them to the
database so I could work with them, but alas, I was wrong.  It's only
logging how many searches there are and what IPs they come from.  (Yes,
I know I should fire the database architect - already did.  He's the
same guy who did the system architecture AND the UI design, too, but
that's another rant...)
 
My task:  I need to write up the requirements to give to the developer
to implement search logging for this site.  
 
What I'm asking for:
- Samples of search logs.  Just snippets, 10-50 lines, so I can see
what folks are logging and how.  It can be raw logs rather than reports
- reporting is going to be handled with SQL queries written by me and
the mouse in my pocket, and I'll have plenty of time to worry about that
once I've got the site started logging and am waiting to have enough
data to be useful.
- Any advice about some piece of data you find yourself wishing your
site were logging when it comes to reporting/analysis time.
- A fairy godmother might bring me some piece of open source code that
logs search queries and results on Apache servers... 
 
Relevant background information:  this is essentially a completely
custom Intranet app, written in PHP to talk to a MySQL db and run on an
Apache/Linux box. No CMS, no productized search engine, no hope of using
anything that someone else has debugged and shrinkwrapped.  
 
I'll summarize any relevant generalizable stuff for the list. 
 
Thanks to all, 
 
- Billie