Remedy with Smart IT - How to enable the Smart IT Debug Log for versions 18.xx, 19.xx and 20.02 - INCLUDES VIDEO

Manage Support IDs

Use checkboxes to 'Remove support IDs/Users' or 'Allow to create Cases'
Support IDs for BMC Customer Support Site Guest User
Profiles Which Include    Back to All Support IDs
 

Knowledge Article

Remedy with Smart IT - How to enable the Smart IT Debug Log for versions 18.xx, 19.xx and 20.02 - INCLUDES VIDEO
How to enable Smart IT Debug Log for versions 18.xx, 19.xx and 20.02
Remedy with Smart IT
Remedy with Smart IT
Remedy with Smart IT 18.05
Remedy with Smart IT 20.02
Remedy with Smart IT
Remedy with Smart IT
Remedy with Smart IT 18.05
Remedy with Smart IT 20.02
How to enable the DEBUG logging for Smart IT versions 18.xx, 19.xx and 20.02



This article describes how to debug logging can be enabled for Smart IT versions 18.xx, 19.xx and 20.02. These logs are useful for troubleshooting purposes and often required by BMC Support.

Note: Starting with Smart IT 20.08, a new ‘log.level’ Centralized Configuration parameter has been introduced for Smart IT to more easily enable debug logging for this application.
 
  1. With an AR System Administrator account open the "AR System Configuration Component Setting" form in Mid-Tier
  2. From the menu associated with the ‘Component Name’ field, select the entry related to the Smart IT server where you want to enable the Debug logging, as indicated below:
Component Name:  com.bmc.arsys.smartit  -->  [smartITServerHostName-port]

 
User-added image
  1. Press ‘Search’ to find the matching record
  2. To enable DEBUG logging for Smart IT’s default logger for this server, update the record using the following steps (see also the screenshot below for further detail):
A.  Confirm the record shows the expected Smart IT server reference in the ‘Component Name’ field and ‘logback.configuration’ in the ‘Setting Name’ field
B.  Use the Expand button next to the ‘Setting Value’ field to expand the field's contents
C.  Use the browser’s search function (CTRL+F) to find the text: ‘Default DEBUG logger’
D.  If the log level is not set to DEBUG already, update the following line from:
 
     <logger name="com.bmc.bsm" level="INFO">

    To:

    <logger name="com.bmc.bsm" level="DEBUG">
 
User-added image
  1. Save the record, the Smart IT Server should pick up this new log setting within 60 seconds and you should see log lines with the word ‘DEBUG’ appearing in the smartit.log file (default location: ..\BMC Software\Smart_IT\Smart_IT\Logs), e.g.:
<date_time> | Thread-5                       | RID: none | DEBUG   | c.b.b.m.i.Application | There are 0 users need to be reset.
  1. In case of a Smart IT Server cluster, repeat steps 2 to 5 for all Smart IT Servers where DEBUG logging should get enabled
  2. Once the required logs have been created, use similar steps to reset the log level to its original value


Note: next to the ‘Default DEBUG logger’, the XML in the ‘Setting Value’ contains references to several other more detailed loggers, all have a similar format:

<logger name="logger_name" level="current_log_level" [additivity="false"]>

If required, DEBUG logging for these detailed loggers can be enabled in the same way as described above, i.e. by updating the ‘level’ value to DEBUG.
Remedy with Smart IT
Remedy with Smart IT
Remedy with Smart IT 18.05
Remedy with Smart IT 20.02
Attachment(s):