Adjusting the Logging Configuration :: SAS® Visual Analytics 7.4: Administration Guide

Log Directories

In the standard configuration, logs are in the SAS configuration directory as follows:

Log configuration files are in /Web/Common/LogConfig.

Note: Log configuration files that have an _apm suffix are used by SAS Environment Manager. Do not make changes to those files.

Generated logs are in /Web/Logs/server. For exact locations for generated logs, see the file SAS-configuration-directory/Documents/Instructions.html on the middle-tier machine (for web applications) and the compute tier machine (for servers).

UNIX example:	`/opt/sas/config/Lev1/Documents/Instructions.html`
Windows example:	`C:\sas\Config\Lev1\Documents\Instructions.html`

Note: SAS Visual Statistics logs are included in logs for SAS Visual Analytics Explorer.

How to Change Log Levels

CAUTION:

Excessive logging can degrade performance.

Do not use the TRACE and DEBUG logging levels unless you are directed to do so by SAS Technical Support. Remember to revert your logging level after diagnosis is complete, or as directed by SAS Technical Support.

The preferred method for changing a logging level is to make a temporary, dynamic change in SAS Web Administration Console. See Administering Logging for SAS Web Applications in the SAS Intelligence Platform: Middle-Tier Administration Guide.

As an alternative to making a dynamic change, you can directly edit the appropriate log configuration file (after making a backup copy of the file).

The following example demonstrates how to change the log level to debug the explorer.

In the SASVisualAnalyticsExplorer-log4j.xml file, change the log level to DEBUG:

<category additivity="false" name="com.sas.biv">
<level value="DEBUG"/>
<appender-ref ref="SAS_CONSOLE"/>
<appender-ref ref="SAS_INFO_FILE"/>
</category>

Restart the SAS Web Application Server.

How to Log Submitted Code

To include SAS logs in the data builder and administrator logs:

In the SASVisualDataBuilder-log4j.xml file and the SASVisualAnalyticsAdministrator-log4j.xml file, uncomment the SAS Job submission section.
Restart the SAS Web Application Server.

Tip

Related functionality is provided by a user preference. See Record actions as SAS statements.

How to Log LASR Actions

To log commands that are issued to a SAS LASR Analytic Server from the designer or the web viewer:

In the logging contexts section of the SASVisualAnalyticsDesigner-log4j.xml file and the SASVisualAnalyticsViewer-log4j.xml file, uncomment the tags for the com.sas.lasr.command category.
Restart the SAS Web Application Server.

Logging of Access Denials

Metadata-layer access denials are logged as follows:

For requests from the administrator and the data builder, access denials are logged in the LASR authorization log (SASLASRAuthorizationVersion.log).
For requests from other SAS Visual Analytics applications, access denials are logged in the application’s log file (for example, SASVisualAnalyticsExplorerVersion.log).

Log entries provide details about the cause of the access denial, indicating which user lacks which permissions for which metadata object.

Logging for SAS Mobile BI

The logging configuration for SAS Mobile BI is defined in the SASVisualAnalyticsTransport-log4j.xml file.

You can use the viewerservices.validate.schema.* properties to increase logging for the rendering of reports in SAS Mobile BI. See Transport Service Properties.

Logging for Platform Servers

See Administering Logging for SAS Servers in the SAS Intelligence Platform: System Administration Guide.