[db-filter] Section

The DB Filter section controls the delivery of specified log events from specified applications and application types. See Sample Configuration.

This section must be called db-filter.

block-messages

Default Value: No default value
Valid Values: Comma-separated list of identifiers of any valid log events
Changes Take Effect: Immediately

Specifies the log events reported by any application that will not be recorded in the Central Log Database.

block-messages-by-<type>

Default Value: No default value
Valid Values: Identifiers of any applications, separated by commas
Changes Take Effect: Immediately

Specifies the log events reported by applications of the specified type that will not be recorded in the Central Log Database, where <type> is the numeric value of the application type.

For information about application types, refer to the Database Format section of the Log Format chapter in the Management Layer User's Guide.

block-messages-from-<DBID>

Default Value: No default value
Valid Values: Identifiers of any valid log events separated by commas
Changes Take Effect: Immediately

Specifies the log events reported by the specified application that will not be recorded in the Central Log Database, where <DBID> is the numeric value of the application.

Important

The application DBID can be retrieved by using the -getallappstatus parameter of the mlcmd command-line utility. Refer to the Management Layer User's Guide for the correct syntax of this command, and how to use it.

Sample Configuration

The following is a sample configuration of the db-filter section for Message Server:

[db-filter]
block-messages = 4001,4002,4003
block-messages-from-201 = 1001,1002,1003
block-messages-by-9 = 5003,5004,5005