(SM) Support Tip: Using SM dynamic-debugging functionality in SMA-SM

Service Managers dynamic debugging functionality is easy to use and works well for background schedulers, user sessions (from status monitor) and for integration sessions (programmatically by rtecall(“setdebug”)).

For more information see Dynamic debugging of user sessions or schedulers

SMA-SM is Micro Focus suite product that integrates Service Manager with UCMDB, Smart Analytics, Service Portal, Chat and more by running these single products containerized on a Container Deployment Platform using technologies like Docker and Kubernetes.

In SMA-SM log files can be found on network file system (NFS): So while using dynamic debugging is the same, localizing the log files is different:
The session that you are tracing runs on a servlet on a pod. The term “pod” may be understood as a virtual server in Kubernetes context. The name of the pod is part of the log file name.
To find the pod name, you need to check the “Hostname” column in status monitor. For background schedulers and user sessions, you can directly check the row of the existing session. For integration sessions, the session will be established when a request arrives, so you cannot lookup the session, yet. However, as the servlet should be running already, you can lookup the “Hostname” of any session running on this servlet. 

post1.png

 

Now we know the log file name:  sm_<hostname>.log     

in this example:  sm_sm-rte-545838427-hkk44.log

The location of the log file is a subdirectory of this path:  <SMA global volume>/logs/sm-<x.yz>       
For example:
for background processes: /var/vols/itom/itsma/itsma-itsma-global/logs/sm-9.52/scheduler
or for user sessions: /var/vols/itom/itsma/itsma-itsma-global/logs/sm-9.52/rte

This screenshot shows how to localized the log file in the log file NFS storage and how to display inside the shell using cat command:

post2.png

 

Output of the cat command: 

post3.png