Changing log levels at runtime

For each service that you have running in BMC Discovery, you can dynamically change the log level without having to restart the appliance.

To change log levels

  1. From the main menu, click the Administration iconThe Administration page displays. 
    For a full description, see the Administration Page.
  2. From the Appliance section, click Logs.
    The Logs page is displayed showing the Logging Levels tab.
    Each of the available service settings has a drop-down menu which enables you to change the log level for that setting without having to restart the appliance. The current logging level for each setting is also displayed for reference purposes.

The following log levels are available for selection:

  • Debug — Specifies fine-grained informational events that are most useful to debug the application.
  • Info — Specifies informational messages that highlight the progress of the application at coarse-grained level.
  • Warning — Specifies potentially harmful situations.
  • Error — Specifies error events that might still allow the application to continue running.
  • Critical — Specifies severe error events that might cause the application to abort.

The log levels are cumulative in the order they are displayed in the drop-down. Therefore, the Debug log level includes everything including debug messages, Info includes everything up to and including the Info level, and so forth.

If you change the log levels on this page, the levels will persist. In other words, the next time that you restart the appliance the log level settings that you have selected will remain.

When you change one or more of the log levels from the drop-down menu against any setting, click Apply. A message is displayed informing you that the change you have made has been successful. This message will continue to be displayed until you select another page in BMC Discovery and return to the Logging window. The Apply button is not enabled until you have changed one or more of the log levels.

Potential performance impact of Debug log level

If you select Debug for any setting a pop-up warning is displayed asking you to confirm your selection. This is because the Debug log level can impact the performance of the system.

To add a custom marker to the logs

You can add an additional custom marker with custom text to the logs to aid with problem diagnosis.For example, if you add the custom marker, "My error marker" when you are about to test for an error which occurs when you perform a particular operation, you can ignore the log file up to the point where you find your marker.

To add a custom marker:

  1. From the main menu, click the Administration iconThe Administration page displays. 
    For a full description, see the Administration Page.
  2. From the Appliance section, click Logs.
    The Logs page is displayed showing the Logging Levels tab.
  3. Enter the text for the custom marker into the field by the Add log Marker button, for example, "My error marker" and click Add log Marker.
  4. The marker is added to all logs along with a timestamp. For example:
    ...
    140576255624960: 2017-09-08 12:29:41,945: websession.servants: USEFUL: MARKER: system: My error marker
    ...



Was this page helpful? Yes No Submitting... Thank you

Comments