Options:Web Engagement Cluster:log:affectedLoggers

View in ref guide.

Edit this option          Publish this option          Clear draft content

Published Option

affectedLoggers

Default Value: The default value is an empty string, which means that there aren't any affected loggers.
Valid Values: Comma-separated list of logger names, specified in the LOG4J2.xml. For example: com.genesyslab.webme.commons,PROTOCOL,org.apache.cassandra
Changes Take Effect: Immediately

Verbosity settings are explicitly applied for loggers, as specified in the extended description.

Extended Description: Verbosity settings are explicitly applied for the following loggers:

• Loggers that are not declared explicitly in the log4j2.xml configuration file.
• Loggers that are specified explicitly in the log4j2.xml and are specified in the value for this affectedLoggers option.

For other loggers specified in log4j2.xml, but not mentioned in the value for this option, the verbosity level is not re-applied.

Here is a use case for when you might need to set this option:

• Cassandra needs to write error messages to a log file, and at the same time, Genesys components also need to write debug messages to the log file.

To resolve this use case, you would:

1. Specify the following logger in log4j2.xml: <logger name="org.apache.cassandra" level="error" additivity="false">
2. Do not include org.apache.cassandra in the value for the affectedLoggers option.
3. The default log4j2.xml file contains the following logger: <logger name="com.genesyslab.platform" level="info" additivity="false">
4. Include com.genesyslab.platform in the value for the affectedLoggers option.
5. Set the verbose option to debug.

In the sample above, the value of affectedLoggers should be com.genesyslab.platform. Error (but no debug or info) messages from Cassandra will be available in logs, and debug messages from com.genesyslab.platform will be available in logs.

Draft Option

No draft option