This SAS KB article describes two methods about how to enable debug traces for sas-risk-cirrus-objects pod services.

---

Method One: The SAS Environment Manager User Interface

To enable debug traces for sas-risk-cirrus-objects pod services from the SAS Environment Manager (SAS Viya) user interface (UI), complete the following steps:

1. Go to the SAS Environment Manager UI view.
2. Click Configuration (the wrench icon).
3. Filter the search for logging.level.
4. Add a new logging level for Risk Cirrus Business Objects service with a parameter name and a level value.
   
   
   

   Parameter Name	Level Value
   com.sas.commons.rest.ExceptionLog	DEBUG
   com.sas.logging.stacktrace	DEBUG
   com.sas.risk.rgf.search	DEBUG
   org.opensearch.client	TRACE
   tracer	TRACE
   com.sas.risk.rgf.search.opensearch.OpenSearchApplicationEventListener	INFO

---

Method Two: Update ConfigMap

Complete the following steps to enable debug traces by updating ConfigMapces for the sas-risk-cirrus-objects pod service:

1. Set the following properties in the sas-risk-cirrus-objects config map from the command line:
   
   kubectl edit cm <sas-risk-cirrus-objects pod service name>
   
   Note: Replace <sas-risk-cirrus-objects pod service name> with the actual pod name.
   
   
2. Add the following properties within ConfigMap:
   • JAVA_OPTION_LOGGING1: '-Dlogging.level.com.sas.commons.rest.ExceptionLog=DEBUG'
   • JAVA_OPTION_LOGGING2: '-Dlogging.level.com.sas.logging.stacktrace=DEBUG'
   • JAVA_OPTION_LOGGING3: '-Dlogging.level.com.sas.risk.rgf.search=DEBUG'
   • JAVA_OPTION_LOGGING4: '-Dlogging.level.org.opensearch.client=TRACE'
   • JAVA_OPTION_LOGGING5: '-Dlogging.level.tracer=TRACE'
   • JAVA_OPTION_LOGGING6: '-Dlogging.level.com.sas.risk.rgf.search.opensearch.OpenSearchApplicationEventListener=INFO'
     
     
3. Restart the pod. Then, collect the pod with additional debug traces for further review.