Skip to main content
NetApp Knowledge Base

What is the rotation rule for audit/trace.log in  SANtricity Web Services Proxy?

  1. Last updated
  2. Save as PDF
Views:
13
Visibility:
Public
Votes:
0
Category:
e-series-santricity-web-services-proxy
Specialty:
esg
Last Updated:

Applies to

  • E-Series
  • SANtricity Web Services Proxy
  • SANtricity firmware 11.90

Answer

  • Log rotation for audit.log and trace.log in NetApp SANtricity Web Services Proxy is supported and works as follows:
  • - Rotation occurs based on both time (daily) and file size.
  • - Time-based: Rotation is performed daily at the date change.
  • - Size-based: Rotation is triggered when the log file reaches the configured file size limit (default is 100MB).
  • - After rotation, files are compressed into ZIP format and saved using the following naming convention:
  • - audit.log: audit.YYYY-MM-DD.N.log.zip
  • - trace.log: trace.YYYY-MM-DD.N.log.zip
  • - YYYY-MM-DD is the date of rotation.
  • - N is a sequence number (starting from 0) for multiple rotations on the same day.
  • - Up to 90 days of rotated ZIP log files are retained by default.
  • - There is no documented or supported way to change the retention period or the number of generations kept for these logs.
  • Example rotated files:

trace.2021-10-18.0.log.zip

trace.2021-10-18.1.log.zip

trace.2021-10-18.2.log.zip

  • Log file location on Windows:

C:\Program Files\NetApp\SANtricity WebProxy\working\logs\

Additional Information

additionalInformation_text
NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.