SAS® Intelligent Decisioning diagnostic and data collection guide


This SAS KB article contains structured instructions for diagnosing and resolving problems in SAS Intelligent Decisioning. The information in this article will help you define the problem clearly, collect essential diagnostic data, and identify the next steps toward resolution. 

The sections below outline standard data collection practices along with key questions to help define and scope the problem effectively. Establishing a detailed and complete problem description early in the investigation process can significantly reduce time to resolution. 

Define the Problem 

Use the questions below to help clearly define the problem before collecting diagnostic data. 

Context and Observations 

  • What were you doing when the problem first occurred?
  • What part of SAS Intelligent Decisioning were you working in? 

Error or Unexpected Behavior 

  • Was an error message displayed?
    • If yes, provide the full message and a screenshot if possible.
    • If no error was displayed, what unexpected behavior occurred?
  • What occurred versus what did you expect? 

Steps to Reproduce 

  • What sequence of steps led to the problem?
  • Can you reproduce the issue consistently? 

Scope of Impact 

  • Does this issue occur for all decisions or only specific ones? 
  • Have you tested other decisions?
  • Does this issue affect all users or only certain users?  
    • Have other users attempted the same action?

History and Changes 

  • Has this worked previously? If so, when was it last successful?
  • Were there any recent changes? (For example, deployments, updates, configuration changes, data changes, or changes to decisions.) 

Diagnostic Data to Collect 

To support resolution, collect the following diagnostic data at the time that the problem occurs. 

  • Use the get-k8s-info script (documented in SAS KB0038941) to compile and collect information about the SAS® Viya® platform deployment and SAS Intelligent Decisioning Kubernetes artifacts.
  • Capture a HAR file from the browser during the issue, as documented in SAS KB0036430.
  • Include screenshots of observations, errors, or unexpected results. 

Note: You should provide these artifacts in addition to a clear problem description. 

If get-k8s-info Is Not Available 

If you are unable to provide the get-k8s-info output, collect a describe and the logs from the time of the issue from relevant pods: 

  • sas-decision-manager-app-*
  • sas-decisions-framework-*
  • sas-model-publish-*
  • sas-cas-*
  • sas-microanalytic-score-*

Optional or Additional Data to Collect

  • exported decision
  • browser console logs

Providing complete diagnostic data in advance can significantly reduce time to resolution. 

Next Steps: Navigate Resolution Paths 

Once you clearly define the problem and collect diagnostic data, engage SAS Technical Support for further assistance. Provide the detailed and complete problem description along with the prescribed diagnostic data.