Changing the debug logging level

BMC Customer Support might ask you to change the debug logging level in the course of diagnosing a problem.

The debug messages can be set in the order of severity.

The following table provides debug messages in the order of severity and verbosity:

Setting a log level gets you messages from the level at which the logs are set and higher in the sequence. The default setting is INFO level.

To change the debug logging level

1. Navigate to the configuration file for the component for which you want to collect logs, as shown in the following table.

   Component type	Location 1		Logging level property	Re-start required?
   Collection Station	Windows	\station\collection\conf\logback.xml	logger name="com.bmc.ola" level="INFO"	No
   	Linux	/station/collection/conf/logback.xml
   Collection Agent	Windows	\bww\udc\conf\logback.xml	logger name="com.bmc.ola" level="INFO"	No
   	Linux	/bww/udc/conf/logback.xml
   Search + Console Server	Windows	\conf\server\logback.xml	logger name="com.bmc.ola" level="INFO"	No
   	Linux	/conf/server/logback.xml
   Indexer	Windows	\conf\indexer\log4j2.properties	es.logger.level: INFO	Yes
   	Linux	/conf/indexer/log4j2.properties

   ¹The location paths provided in the table (except the Collection Agent) must be preceded by one of the following environment variables:

   • Windows: %BMC_ITDA_HOME%
   • Linux: $BMC_ITDA_HOME

   The Collection Agent location path must be preceded by one of the following environment variables:

   • Windows: %PATROL_HOME%

   • Linux: $PATROL_HOME

2. Edit the configuration file as described in the preceding step and change the value of the logging level property to one of the following, depending on the level of verbosity required.

   Logging level	Description
   TRACE	Designates finer-grained informational events than the DEBUG. Enables logging.
   DEBUG	Designates informational events that are useful for debugging an application.
   INFO	(Default) Designates informational messages that highlight the progress of the application at a high level.
   WARN	Designates potentially harmful events
   ERROR	Designates events that might still allow the application to keep running.
   OFF	Disables logging.

3. Save the file.
4. If you changed the logging level for the Indexer component, then re-start the Indexer. For more information, see Starting or stopping product services.

Where to go from here

After changing the logging level, use the  maintenance tool to create a zipped copy of the log files and send it to BMC Customer Support.