Blog

An administrator’s dirty laundry and getting himself scrubbed


Tags :


I have been teaching two of the Lotus admin classes this week (subbing in at the last minute for a partner of ours that is a LAEC and had a CLI cancel last minute) and one of the students asked a very personal matter from his job.  Since no one can track down who that might be, I share this little story for admins to learn by.

He walked away with a moral dilemma on his hands.  As a new administrator (under 9 months I recall from the introduction time) he came across another admin that seemed to be reading everyone's mail during the day.  He was unsure for a while and eventually caught on that is what this person did most of the day.  I asked why he didn't report this admin to someone and he informed me (and the class as they listened intently) that it was the senior admin that had been there for years.  Apparently for kicks he just went through and read email at will.  Now I am not sure what he was thinking, maybe that it was company owned mail system or whatever, but I am sure that wouldn't go over well.

The point here is that the admin did not know how to show that the senior was doing it.  User Activity from a database just doesn't show enough.  An admin could be checking just about anything and you would have to go to each database to gather he was even in there.  (see following image to see how hard it is from User Activity from database preferences)

Image:An administrator´s dirty laundry and getting himself scrubbed

Now I came across the exact answer he wanted in Domino 6.  Activity Logging.  This beautiful piece of code can log Domino.Database.Sessions fully and then export selected documents to a structured text or even delimited file to allow import easily into Excel for nice 3D graphics of how this admin is accessing databases.

Notes database activity logging
Notes database activity logging tracks Notes database activity that occurs during a server session. Database records include such information as the name of the database, the name and address of the database user, the number of documents read and written, the number of bytes read and written, the total number of transactions executed in the database, and the length of time the database was open. Servers, users, and API programs can all generate database activity.

So I hope he packed his clean skivvies for when the new admin walks in with this report and he craps on himself while packing his desk.

Moral of the story here?  If you have enough time to read the mail from your domain, there isn't enough to do or too many of you in the first place.