Yes - it *is* possible to disable the "Domain Indexer is indexing..." and "Domain Indexer finished indexing ..." messages in the log :-)
Tags: Lotus Domino
My Domino log contained a bunch of messages like;
23.11.2009 08:28:42 Domain Indexer is indexing Database 'bla bla.nsf'
23.11.2009 08:28:42 Domain Indexer finished indexing Database 'bla bla.nsf'
Not really something I pay much attention to, and I would rather have any errors or warnings instead.
My Domino log contained a bunch of messages like;
23.11.2009 08:28:42 Domain Indexer is indexing Database 'bla bla.nsf'
23.11.2009 08:28:42 Domain Indexer finished indexing Database 'bla bla.nsf'
Not really something I pay much attention to, and I would rather have any errors or warnings instead.
So, a question was
posted in the Partner Forum 2009, and after a day or so, Susan Bullock
from IBM responded "You can set up log and/or console filters to filter
anything out. "....
He he, not much more than absolutely necessary, but enough to get me searching for Log filtering! I found out that log and console filters are defined in the Events4.nsf database;
Creating a filter looks like this;
The cool thing is that you can tell each area what messages you want to keep out of the log! Above I have specified that I don't want to see Normal messages from the Comm/Network-area.
Please refer to the "Using log filters to reduce server logging" article too, which I have copied the text from below;
Using log filters to reduce server logging Technote (troubleshooting)
Problem
In Lotus Domino, you have reduced the logging for individual server tasks such as the Replicator and Router to minimal levels but would like to further reduce logging. How can this be done?
Resolving the problem
Log filters can be created to reduce logging beyond what is available in notes.ini parameters like log_replication and log_mailrouting. These filters are useful for disabling logging of specific messages that cannot be otherwise disabled. As an example, the following message cannot be disabled from logging:
"ATTEMPT TO ACCESS SERVER by User/Acme was denied".
There may be situations where this type of message is generated so frequently that it consumes a significant portion of the overall server logging. If you do not want this type of message to be logged, you can enable a log filter that will discard events of a particular type and severity.
Here is an example of setting up a log filter to remove the error shown above:
1. Create a new Log Filter document in events4.nsf (Filters > Log Filters > New Event Filter).
2. Enter the server name on the Basics tab.
3. On the Database tab, choose the following:
Log unknown types/severities: Yes.
Select types > check all types (this will enable a row of tabs at the bottom).
In each tab except Misc, uncheck all severities (Fatal, Failure, Warning(High), Warning(Low), and Normal). This means those severities will be logged.
On the Misc tab, check Warning(Low) and Normal. Uncheck the other severities.
4. On the Console tab, choose the same settings as in Step 3 above.
5. Save and close the Log Filter document and restart the Event task.
The new log filter will prevent logging of the "ATTEMPT TO ACCESS SERVER" errors. Note that it will also filter any other events of type Misc with severity Warning(Low) or Normal.
He he, not much more than absolutely necessary, but enough to get me searching for Log filtering! I found out that log and console filters are defined in the Events4.nsf database;
Creating a filter looks like this;
The cool thing is that you can tell each area what messages you want to keep out of the log! Above I have specified that I don't want to see Normal messages from the Comm/Network-area.
Please refer to the "Using log filters to reduce server logging" article too, which I have copied the text from below;
Using log filters to reduce server logging Technote (troubleshooting)
Problem
In Lotus Domino, you have reduced the logging for individual server tasks such as the Replicator and Router to minimal levels but would like to further reduce logging. How can this be done?
Resolving the problem
Log filters can be created to reduce logging beyond what is available in notes.ini parameters like log_replication and log_mailrouting. These filters are useful for disabling logging of specific messages that cannot be otherwise disabled. As an example, the following message cannot be disabled from logging:
"ATTEMPT TO ACCESS SERVER by User/Acme was denied".
There may be situations where this type of message is generated so frequently that it consumes a significant portion of the overall server logging. If you do not want this type of message to be logged, you can enable a log filter that will discard events of a particular type and severity.
Here is an example of setting up a log filter to remove the error shown above:
1. Create a new Log Filter document in events4.nsf (Filters > Log Filters > New Event Filter).
2. Enter the server name on the Basics tab.
3. On the Database tab, choose the following:
Log unknown types/severities: Yes.
Select types > check all types (this will enable a row of tabs at the bottom).
In each tab except Misc, uncheck all severities (Fatal, Failure, Warning(High), Warning(Low), and Normal). This means those severities will be logged.
On the Misc tab, check Warning(Low) and Normal. Uncheck the other severities.
4. On the Console tab, choose the same settings as in Step 3 above.
5. Save and close the Log Filter document and restart the Event task.
The new log filter will prevent logging of the "ATTEMPT TO ACCESS SERVER" errors. Note that it will also filter any other events of type Misc with severity Warning(Low) or Normal.
| Permalink | 
