This SAS Note is part of a series of SAS Notes about diagnosing and resolving issues with SAS Micro Analytic Service (MAS) on SAS Viya 3.5 and SAS Viya. For additional information, see the related SAS Notes below:

• SAS Note 70240, “General questions about diagnosing and resolving issues with SAS^® Micro Analytic Service (MAS) on SAS^® Viya^® 3.5 and SAS^® Viya^®”
• SAS Note 70229, “Database considerations for diagnosing and resolving issues with SAS^® Micro Analytic Service on SAS^® Viya^® 3.5 and SAS^® Viya^®”
• SAS Note 70242, “Performance considerations for diagnosing and resolving issues with SAS^® Micro Analytic Service on SAS^® Viya^® 3.5 and SAS^® Viya^®”

SAS Micro Analytic Service Logging

The default logging levels are helpful in many cases. However, sometimes more detailed logging is needed to solve problems. If you encounter an issue with MAS, complete the following steps:

1. Set the following loggers to DEBUG through SAS® Environment Manager:

• Audit.Table.Connection
• App.tk.MAS
• MAS_CONTROLLER
• App.TableServices.DS2.Config.Source
• App.TableServices.DS2.Runtime.SQL

2. Restart MAS for the changes to take effect.
3. Recreate the problem.
4. Provide the logs to Technical Support.

Change the Logging Levels

The following instructions and screenshots describe and illustrate how to set the App.tk.MAS logger to DEBUG in a SAS Viya environment. Use this section as an example of the steps that you need to complete for each of the loggers that were mentioned above.

1. In SAS Environment Manager, select Configuration from the left pane. 
2. Change the View to All services in the View drop-down list. 
3. Enter micro in the search box immediately below the View drop-down list. 
4. Click Micro Analytic Score service. 
5. In the right pane, find the entry labeled logging.level: App.tk.MAS.
6. To edit the entry, click the Pencil icon that is associated with the App.tk.MAS entry, as shown in the following image:

7. In the Edit logging.level Configuration dialog box that appears, change the level to DEBUG, as shown in the following image:

8. Click the Save button.

Note: Repeat steps 1-8 for all of the desired loggers.

9. Restart MAS for the changes to take effect.

Where to Find the Logs

In SAS Viya 3.5, MAS generates two log files in the /opt/sas/viya/config/var/log/microanalytic/default directory. One of the log files is named sas-microanalytic*, and the other log file is named sas-microanalytic-core*. Technical Support requires both of the log files to diagnose and resolve most issues.

In SAS Viya, MAS generates a single log file that is associated with each sas-microanalytic-score pod.  Technical Support requires the logs that are associated with the sas-microanalytic-score pods to diagnose and resolve most issues. You might be able to collect the logs by using a log aggregator or through kubectl. Note that the logs that you collect through kubectl might be incomplete if the logs rolled over. If the logs that you collected through kubectl are truncated, use the method described in the “Generate and Collect a Complete Log Using kubectl” section.

Other Loggers

Technical Support might advise you to enable other loggers while diagnosing and resolving a problem.  You should enable these loggers only if you were advised to do so by SAS Technical Support.

Other documented loggers include the following:

• SAS Viya 3.5: SAS Micro Analytic Service Logging
• SAS Viya: SAS Micro Analytic Service Logging
• For MAS start-up issues, set com.sas.mas.api.MASFactory to DEBUG or higher. The additional output is printed on a logger called MAS_ENV in the log file.
• For MAS issues that are related to the Subject Contacts service, set com.sas.mas.service.history.MASHistoryPublisher to TRACE.

Generate and Collect a Complete Log Using kubectl

Complete the following steps to capture all the logs that are generated by the sas-microanalytic-score pod:

1. Delete the following pod. (It will auto restart.)

kubectl -n <namespace> delete pod sas-microanalytic-score-<id>

• Where <namespace> is the Kubernetes namespace that contains a sas-microanalytic-score pod.
• Where <id> is the specific ID associated with the currently running sas-microanalytic-score pod.

2. Note the new pod name.

kubectl -n <namespace> get pods | grep sas-microanalytic-score

• Where <namespace> is the Kubernetes namespace that contains a sas-microanalytic-score pod.

3. Redirect and follow the log using the -F parameter along with a redirect and the new pod name that you obtained from step two. This command does not return control to the shell.

kubectl -n <namespace> logs sas-microanalytic-score-<new_id> -f --all-containers > /tmp/sas-microanalytic-score_<new_id>.log

• Where <namespace> is the Kubernetes namespace that contains a sas-microanalytic-score pod.
• Where <new_id> is the ID of the sas-microanalytic-score pod that you obtained in step two.

4. Recreate the problem or event to be captured in the logs.

5. Use CTRL-C to stop the log redirection that you started in step three. The resulting log file, which was specified in step three, contains all the log messages from the sas-microanalytic-score pod.

Operating System and Release Information

Product Family	Product	System	SAS Release
			Reported	Fixed*
SAS System	SAS Micro Analytic Service	Linux for x64	Viya platform

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

---

Type:	Problem Note
Priority:	low

Date Modified:	2023-07-31 10:20:38
Date Created:	2023-07-06 10:08:41