An optional SAS Micro
Analytic Service start-up parameter specifies the location of an XML
logging configuration file, which controls the logging levels and
the location of the log file or files.SAS Micro Analytic Service uses
the SAS 9.4 Logging Facility. For more information, see SAS Logging: Configuration and Programming Reference. Your SAS solution
provides a default logging configuration file, and that file specifies
loggers and appenders in addition to those described in this chapter.
For
example, on UNIX the logging configuration file might be /data1/<SAS-configuration-directory>/Lev1/Web/Common/LogConfig/SASMicroAnalyticService-log4sas.xml.
For more information, see your solution’s documentation.
SAS Micro Analytic Service
uses three loggers named App.tk.MAS, App.tk.MAS.Python, and App.tk.MAS.CodeGen.
Code that is hosted by SAS Micro Analytic Service, or the functions
that it calls, can use additional loggers.
The logger App.tk.MAS
is used for logging start-up, shut-down, and method execution events.
App.tk.MAS.CodeGen is used for code compilation and generation logging
events, such as compiler warnings and errors. App.tk.MAS.Python is
used for logging that is related to Python. Normal operations, such
as start-up and shut-down, are logged at the INFO level. Detailed
information about operations such as compilation start and finish
is logged at the DEBUG level. Warning and error conditions are logged
at the WARN or ERROR levels, as appropriate. By default, App.tk.MAS
is set to the ERROR level.
Your SAS solution might report
compilation messages automatically. Because these messages are available
programmatically, and to prevent compiler messages from cluttering
the log, App.tk.MAS.CodeGen is set to the FATAL logging level by default.
In order to see the
data source connection string information that has been logged, set
both the App.tk.MAS and Audit.Table.Connection loggers' level
to debug.
When diagnosing DS2
problems, it is important to note that the App.TableServices.DS2.Runtime.*
and App.TableServices.DS2.Configuration.* loggers do not inherit configuration
from their ancestors. They must be configured explicitly, if you want
to capture logging events directed to those loggers. It is recommended
that you configure them only when diagnosing a DS2 problem since the
additional logging traffic affects performance. For more information
about those DS2 loggers, see the “DS2 Loggers” section
of DS2 Language Reference.