SAS Audit and Performance Measurement Package

Frequently Asked Questions and Customization Tips

Support Statement For SAS 9.4, the supported solution for audit, performance, and measurement needs is SAS Environment Manager. See the main SAS Audit, Performance and Measurement page for more information. SAS has deprecated support of the SAS Audit, Performance and Measurement package. Customers are encouraged to upgrade to the most current release so they can take advantage of the integrated functionality now available in SAS Environment Manager.

The information on this page is provided as a convenience for customers who have already installed the old APM package and are not yet able to upgrade to the most current 9.4 release.

The following information is provided to help customers and system administrators with installation, configuration or customization questions related to the package features and capabilities.

Is there a description of the package elements and processing?

The package documentation includes a description of the key driver programs and data models used within the package under the chapters titled How APM Collects and Analyzes Usage Metrics and How APM Collects and Reports EBI Server Status.

Can the package be customized after installation?

Yes. The package as supplied contains numerous static reports for performance measurement and auditing as well as dynamic reports for server status. The package was designed specifically using well-known SAS language features, it is expected that customers will tailor the reports for the local site environment. Please note that SAS Technical Support cannot provide support for user-written additions or alterations to the package.

What is the performance overhead for the package?

The performance implications for SAS servers with the package enabled are minimal, generally adding one to two percent performance overhead. The change to the SAS server environment is to emit a new performance log file, where there are two log lines per SAS DATA step or PROC step and a few log lines for initialization and termination of the server.

In a server with a significant ELAPSED or CPU time profile, the additional log lines are marginal in the overall server performance, less than one percent. A server or job that has many small DATA or PROC steps AND millisecond ELAPSED or CPU time may observe a slightly higher performance impact, closer to two percent.

The collection of the performance logs and generation of the audit and performance reports are executed in a BATCH environment and therefore do not perturb the performance of the SAS Enterprise BI environment.

Is there a way to send email alerts for failures?

Yes, the package includes support using the SAS EMAIL access method to emit email alerts for status failures. Refer to the documentation chapter Enabling Alert Capabilities for Status Failures in section Enabling an Email Alert, via SMTP for configuration requirements to enable email alerting features.

Does the package integrate with enterprise system monitoring products?

Yes. The package includes the capability to emit status alerts into third-party enterprise management packages. Third-party packages include the Windows Event Viewer, Xymon, HP OpenView, IBM Tivoli Monitoring, and similar packages. Refer to the documentation chapter Enabling Alert Capabilities for Status Failures in section Enabling Third Party Alert Features for configuration requirements to enable third-party alert features.

What userid should be used for the META_USER= value?

The META_USER value is required to be a valid host account with approporiate permissions to execute programs on the SAS application server node. Additionally, the host account must be defined as a Metadata Server user account, with credentials to execute metadata queries. The "sas installation userid" or "sasdemo" accounts may be used as the META_USER account.

Does the package support multiple SASApp environments or multple machine deployments?

Yes, the package includes support for multiple SASApp and machine EBI deployments. The features are enabled by customizing unique setEnvLogs_*.sas programs, as described in the installation and configuration instructions for the package. Note that in multi-tier deployments, APM should correctly be installed on the compute (aka server) tier.

Is there a way to optimize the performance of the query and reporting features in the package?

Yes, the package includes two utilities, SASEnvironment/SASCode/Jobs directory, to facilitate performance optimizations for the SAS data libraries. The program allows administrators to archive reporting data and the program indexes the key SAS data sets used by the package.

Why do the StoredProcessServer logs contain an error message: ARM Application data not available?

The StoredProcessServer emits ARM information for internal ServerAdministration events associated with server administration actions. These events are classified as performance related events but do not contain metric data, therefore, an error message is emitted. These messages may be safely ignored. The text of the message will be similar to:

     2010-04-19T15:40:02,977 ERROR [00006305] 154:user@DOMAIN - ARM Application data not available.

To prevent the message from being emitted, sites may modify the server logconfig.xml file, in the StoredProcessSever configuration directory, modify the Perf.ARM.IOM.StoredProcessServer.ServerAdministration, logger defintion, by adding an additivity="false" statement. For example:

   <!-- Server Administration Message Logger -->
   <logger name="Perf.ARM.IOM.StoredProcessServer.ServerAdministration" additivity="false">
      <level value="Debug"/>
      <appender-ref ref="Events"/>

Additionally, a similar message my be observed in the MetadataServer log. The logconfig.xml file, in the MetadataServer configuration directory may be modified by updating the Perf.ARM.IOM.OMI.ServerAdministration logger defintion. For example:

   <!-- Server Administration Message Logger -->
   <logger name="Perf.ARM.IOM.OMI.ServerAdministration" additivity="false">
      <level value="Debug"/>
      <appender-ref ref="Events"/>

Why do the Enterprise Guide SAS logs contain messages related to MVA_DSIO.OPEN_CLOSE and _DISARM? How can these messages be eliminated from the SAS log for EG users?

The additional messages are a result of enabling ARM performance metrics for the Workspace Server environment. The performance metrics are used to capture data to create performance and usage reports on SAS PROC and DATASTEP execution for the environment. Sites have two options for minimizing the details emitted to the SAS log.