I don't have any log, per se. Not enough hours in the day for me to do the recoveries and document everything about each case. I do, from time to time, blog and post about random cases on my company's blog and forum.
I can relate to you with regard to that.
In my time in the position I documented above I dealt with over 17,000 individual cases/escalations and failed to resolve exactly 223 (I don't count kludges or workarounds as resolutions). As far as I know I am unique in that for two days I had a clean sheet i.e. I had no open cases/escalations in my queue.
I was supposed to document my cases in the database and although I didn't bother quite a lot of the time a typical entry would be:
Problem Description:
"SCSI Problems"
Problem Resolution:
"Told customer to get a screwdriver."
When people were turned over to me after their "basic training" from the company which was long-winded, boring and short on substance (where the trainees invariably left as ignorant as they had started) I gave them the 30 second real tech support training.
I would get them to hold one hand up and take their forefinger under their thumb
I would then get them to take their little finger in their other hand and repeat:
"You cannot cure hardware problems in the OS, so get rid of the hardware problems"
I would then tell them to fold their little finger under their thumb
Next I told them to take their next finger and repeat:
"You cannot cure OS problems in the Application, so get rid of OS problems"
I then told them to fold that finger under their thumb
By this time they had a solitary middle finger sticking up and I would say:
"And whatever is left, we are f@#ked with".
I couldn't be arsed with all the bureaucratic nonsense which tried to get between me and the people who were really having problems - which was the poor guys standing in front of dead servers.
So I can pretty much understand why you wouldn't have much in the way of logs