Gathering log data to debug issues within SAS® Model Risk Management services on SAS® Viya®


If you are encountering issues with SAS Model Risk Management services on SAS Viya, gather the following pod describe and log files for further review:

sudo kubectl -n <namespace> describe pod <sas-risk-cirrus-mrm pod> >> sas-risk-cirrus-mrm-describe.log

sudo kubectl logs <sas-risk-cirrus-mrm pod> -n <namespace> >> sas-risk-cirrus-mrm.log

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

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

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

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

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

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

 

Also, gather the following configuration files for further review:

<ViyaHome>/kustomization.yaml

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

<ViyaHome>/site-config/sas-risk-cirrus-mrm/resources/mrm_transform.yaml

 

If you already have a case open with SAS Technical Support, work with your agent to upload the files that you gathered. If you do not have a case open, contact SAS Technical Support.