This SAS KB article provides guidance about MustGather information that you should collect to help SAS Technical Support troubleshoot issues with the following SAS Viya solutions:

• SAS^® Risk Cirrus Builder
• SAS^® Risk Cirrus Core
• SAS^® Expected Credit Loss
• SAS^® Allowance for Credit Loss
• SAS^® PC Pricing and SAS^® Dynamic Actuarial Modeling
• SAS^® Asset Liability Management
• SAS^® Risk Modeling

 

Enable DEBUG Trace

For all SAS Viya solutions listed above, run the following commands to enable DEBUG trace:

kubectl -n <namespace> set env deployment/sas-risk-cirrus-core SAS_LOG_LEVEL=DEBUG

kubectl -n <namespace> set env deployment/sas-risk-cirrus-builder SAS_LOG_LEVEL=DEBUG

kubectl -n <namespace> set env deployment/sas-credentials SAS_LOG_LEVEL=DEBUG

kubectl -n <namespace> set env deployment/sas-identities SAS_LOG_LEVEL=DEBUG

Additional DEBUG Trace Commands for Certain Solutions

Some solutions require additional DEBUG trace commands to be run. They are listed below by solution name.

SAS Expected Credit Loss

Run the commands listed here as well as the following:

kubectl -n <namespace> set env deployment/sas-risk-cirrus-ecl SAS_LOG_LEVEL=DEBUG

kubectl -n <namespace> set env deployment/sas-risk-cirrus-rfm SAS_LOG_LEVEL=DEBUG

SAS Allowance for Credit Loss

Run the commands listed here as well as the following:

kubectl -n <namespace> set env deployment/sas-risk-cirrus-acl SAS_LOG_LEVEL=DEBUG

kubectl -n <namespace> set env deployment/sas-risk-cirrus-rfm SAS_LOG_LEVEL=DEBUG

SAS PC Pricing and SAS Dynamic Actuarial Modeling

Run the commands listed here as well as the following:

kubectl -n <namespace> set env deployment/sas-risk-cirrus-pcpricing SAS_LOG_LEVEL=DEBUG

kubectl -n <namespace> set env deployment/sas-risk-cirrus-rm SAS_LOG_LEVEL=DEBUG

SAS Asset Liability Management

Run the commands listed here as well as the following:

kubectl -n <namespace> set env deployment/sas-risk-cirrus-alm SAS_LOG_LEVEL=DEBUG

kubectl -n <namespace> set env deployment/sas-risk-cirrus-rfm SAS_LOG_LEVEL=DEBUG

kubectl -n <namespace> set env deployment/sas-risk-cirrus-rm SAS_LOG_LEVEL=DEBUG

SAS Risk Modeling

Run the commands listed here as well as the following:

kubectl -n <namespace> set env deployment/sas-risk-cirrus-rm SAS_LOG_LEVEL=DEBUG

Collect Pod Describe and Log Files

For all SAS Viya solutions listed above, run the following commands to collect pod describe and log files:

sudo kubectl -n  <ns instance> describe pod  <sas-risk-cirrus-core pod>  >> sas-risk-cirrus-core-describe.log

sudo kubectl logs  <sas-risk-cirrus-core pod> -n  <ns instance> >> sas-risk-cirrus-core.log

sudo kubectl -n  <ns instance> describe pod  <sas-risk-cirrus-builder pod>  >> sas-risk-cirrus-builder-describe.log

sudo kubectl logs  <sas-risk-cirrus-builder pod> -n  <ns instance> >> sas-risk-cirrus-builder.log

sudo kubectl -n ingress-nginx describe pod  <ingress-nginx-controller pod>    >>  ingress-nginx-controller-describe.log

sudo kubectl  logs  <ingress-nginx-controller pod> -n ingress-nginx >> ingress-nginx.log

sudo kubectl logs  <sas-credentials pod> -n  <ns instance> >> sas-credentials.log

sudo kubectl -n  <ns instance> describe pod  <sas-credentials pod>  >> sas-credentials-describe.log

sudo kubectl logs  <sas-identities pod> -n  <ns instance> >> sas-identities.log

sudo kubectl -n  <ns instance> describe pod  <sas-identities pod>  >> sas-identities-describe.log

Additional Pod Describe and Log File Commands for Certain Solutions

Some solutions require additional commands to be run. They are listed below by solution name.

SAS Expected Credit Loss

Run the commands listed here as well as the following:

sudo kubectl -n  <ns instance> describe pod  <sas-risk-cirrus-ecl pod>  >> sas-risk-cirrus-ecl-describe.log

sudo kubectl logs  <sas-risk-cirrus-ecl pod> -n  <ns instance> >> sas-risk-cirrus-ecl.log

sudo kubectl -n  <ns instance> describe pod  <sas-risk-cirrus-rfm pod>  >> sas-risk-cirrus-rfm-describe.log

sudo kubectl logs  <sas-risk-cirrus-rfm pod> -n  <ns instance> >> sas-risk-cirrus-rfm.log

SAS Allowance for Credit Loss

Run the commands listed here as well as the following:

sudo kubectl -n  <ns instance> describe pod  <sas-risk-cirrus-acl pod>  >> sas-risk-cirrus-acl-describe.log

sudo kubectl logs  <sas-risk-cirrus-acl pod> -n  <ns instance> >> sas-risk-cirrus-acl.log

sudo kubectl -n  <ns instance> describe pod  <sas-risk-cirrus-rfm pod>  >> sas-risk-cirrus-rfm-describe.log

sudo kubectl logs  <sas-risk-cirrus-rfm pod> -n  <ns instance> >> sas-risk-cirrus-rfm.log

SAS PC Pricing and SAS Dynamic Actuarial Modeling

Run the commands listed here as well as the following:

sudo kubectl -n  <ns instance> describe pod  <sas-risk-cirrus-pcpricing pod>  >> sas-risk-cirrus-pcpricing-describe.log

sudo kubectl logs  <sas-risk-cirrus-pcpricing pod> -n  <ns instance> >> sas-risk-cirrus-pcpricing.log

sudo kubectl -n  <ns instance> describe pod  <sas-risk-cirrus-rm pod>  >> sas-risk-cirrus-rm-describe.log

sudo kubectl logs  <sas-risk-cirrus-rm pod> -n  <ns instance> >> sas-risk-cirrus-rm.log

SAS Asset Liability Management

Run the commands listed here as well as the following:

sudo kubectl -n  <ns instance> describe pod  <sas-risk-cirrus-alm pod>  >> sas-risk-cirrus-alm-describe.log

sudo kubectl logs  <sas-risk-cirrus-alm pod> -n  <ns instance> >> sas-risk-cirrus-alm.log

sudo kubectl -n  <ns instance> describe pod  <sas-risk-cirrus-rfm pod>  >> sas-risk-cirrus-rfm-describe.log

sudo kubectl logs  <sas-risk-cirrus-rfm pod> -n  <ns instance> >> sas-risk-cirrus-rfm.log

sudo kubectl -n  <ns instance> describe pod  <sas-risk-cirrus-rm pod>  >> sas-risk-cirrus-rm-describe.log

sudo kubectl logs  <sas-risk-cirrus-rm pod> -n  <ns instance> >> sas-risk-cirrus-rm.log

SAS Risk Modeling

Run the commands listed here as well as the following:

sudo kubectl -n  <ns instance> describe pod  <sas-risk-cirrus-rm pod>  >> sas-risk-cirrus-rm-describe.log

sudo kubectl logs  <sas-risk-cirrus-rm pod> -n  <ns instance> >> sas-risk-cirrus-rm.log

Gather Configuration Files

For all SAS Viya solutions listed above, gather the following configuration files:

<ViyaHome>/kustomization.yaml

<ViyaHome>/site-config/sas-risk-cirrus-core/resources/core_transform.yaml

<ViyaHome>/site-config/sas-risk-cirrus-builder/resources/sas_risk_cirrus_builder_transform.yaml

Additional Configuration File for Certain Solutions

Some solutions require additional configuration files to be collected. They are listed below by solution name.

SAS Expected Credit Loss

Collect the files listed here as well as the following:

<ViyaHome>/site-config/sas-risk-cirrus-ecl/resources/ecl_transform.yaml

<ViyaHome>/site-config/sas-risk-cirrus-rfm/resources/rfm_transform.yaml

SAS Allowance for Credit Loss

Collect the files listed here as well as the following:

<ViyaHome>/site-config/sas-risk-cirrus-acl/resources/acl_transform.yaml

<ViyaHome>/site-config/sas-risk-cirrus-rfm/resources/rfm_transform.yaml

SAS PC Pricing and SAS Dynamic Actuarial Modeling

Collect the files listed here as well as the following:

<ViyaHome>/site-config/sas-risk-cirrus-pcpricing/resources/pcpricing_transform.yaml

<ViyaHome>/site-config/sas-risk-cirrus-rfm/resources/rfm_transform.yaml

<ViyaHome>/site-config/sas-risk-cirrus-rm/resources/rm_transform.yaml

SAS Asset Liability Management

Collect the files listed here as well as the following:

<ViyaHome>/site-config/sas-risk-cirrus-alm/resources/alm_transform.yaml

<ViyaHome>/site-config/sas-risk-cirrus-rfm/resources/rfm_transform.yaml

SAS Risk Modeling

Collect the files listed here as well as the following:

<ViyaHome>/site-config/sas-risk-cirrus-rm/resources/rm_transform.yaml

 

Upload MustGather Information

After you enable DEBUG trace, collect pod describe and log files, and gather configuration files, share the information with SAS Technical Support. For instructions, see How to upload and download files using the SASTSDrive file sharing server.