About Duffbert...

Duffbert's Random Musings is a blog where I talk about whatever happens to be running through my head at any given moment... I'm Thomas Duff, and you can find out more about me here...

Email Me!

Search This Site!

Custom Search

I'm published!

Co-author of the book IBM Lotus Sametime 8 Essentials: A User's Guide
SametimeBookCoverImage.jpg

Purchase on Amazon

Co-author of the book IBM Sametime 8.5.2 Administration Guide
SametimeAdminBookCoverImage.jpg

Purchase on Amazon

MiscLinks

Visitor Count...



View My Stats

« True Confessions - I'm finally implementing OpenLog... | Main| Book Review - Lessons in Grid Computing - The System Is a Mirror by Stuart Robbins »

Duffbert does admin! Exclude From Log setting in the server doc is great...

Category IBM/Lotus
I rely upon the domlog.nsf file for a number of things in some of my web applications.  My user base wants to know basic hit counts for various items in the applications, so I parse out relevant entries into "webhit" databases that can then be sliced and diced.  So far so good...

But have you ever looked at the domlog.nsf file for an active Domino web server?  It gets really large, really fast.  And quite frankly, I don't care that the browser had requests to four different gif files every time a particular page was loaded.  I wondered if there was a way to filter out certain types of domlog.nsf entries so that I was getting more wheat, less chaff.

Keep in mind I'm a developer by nature, not an admin...  :)

Some research took me to the Exclude From Log section in the Server document.  The URL field allows you to place certain strings that, when appearing in the URL of the log entry, cause it not to be written to domlog.nsf.  I quickly determined that I really had no need for the following entries:

*.gif
*.jpg
*.jpeg
*.bmp
*.js
*.css
*IEmen.htc
*?OpenImageResource

After the filtering kicked in, I was starting to see a lot more important content rather than a ton of junk to sift through.  Very nice...

As an experiment to see how much volume I was saving, I compared a one hour time period (1 to 2 pm) from last Friday (pre-filter) and today (post-filter).  The number of domlog.nsf entries dropped from approximately 35000 documents to 16000 documents.  Over a 50% savings in volume.  I *really* like that!

Even better, that means my daily domlog.nsf parsing agents will only have to run against 50% of the previously normal volumes.  Whoo-hoo!

You know you're a geek when something like this really makes your day...

Comments

Gravatar Image1 - So Computer Dude, what does this mean for us? Can we revisit pulling reports on the marquee types?
Peace

Gravatar Image2 - Hi, Martin... it's something we've discussed doing, but there's always been a number of other more pressing items in front of it. Your posting is a good reminder to see if I can get that bumped up a bit higher in the priority list. Or at least experiment with it at home first...

Gravatar Image3 - Maybe... :)

Gravatar Image4 - Hi Duffbert,

have you ever considered "logging to files" instead of the domlog.nsf? The files created adher to to standard Apache/NCSA Logfile format and can therefor be analyzed with all the standard tools for that job.

Julian posted his article "Reporting On Domino Web Server Logs With AWStats" a while ago and this is IMHO way more usable and featurerich then any other solution.
http://www.nsftools.com/tips/UsingAwstatsWithDomino.htm

Post A Comment

:-D:-o:-p:-x:-(:-):-\:angry::cool::cry::emb::grin::huh::laugh::lips::rolleyes:;-)

Want to support this blog or just say thanks?

When you shop Amazon, start your shopping experience here.

When you do that, all your purchases during that session earn me an affiliate commission via the Amazon Affiliate program. You don't have to buy the book I linked you to (although I wouldn't complain!). Simply use that as your starting point.

Thanks!

Thomas "Duffbert" Duff

Ads of Relevance...