Configuring Logging and Rolling Policies for DevTest VS Catalog

Products

• Service Virtualization

Issue/Introduction

Configuration steps to manage log file sizes through rolling policies and to adjust logging levels for troubleshooting VS Catalog.

Environment

DevTest 10.8.4 and up

Cause

N/A

Resolution

Log Rolling Configuration

To prevent log files from growing indefinitely and to manage disk space, update the application.yml file with the following rollingpolicy settings. These properties define the maximum file size, retention history, and the naming pattern for archived logs Errors in VS Catalog.

logging:
  file:
    name: log/vscatalog.log
  logback:
    rollingpolicy:
      # Max size of each file before rolling (e.g. 10MB, 50MB, 100MB)
      max-file-size: 50MB
      # How many archived files to keep (by date/size policy)
      max-history: 30
      # Optional: cap total size of all archives
      total-size-cap: 1GB
      # Optional: pattern for rolled files (default is next to main file with date)
      file-name-pattern: log/vscatalog.%d{yyyy-MM-dd}.%i.log
      # Optional: delete old archives on startup
      clean-history-on-start: false

Logging Level Configuration

Adjust the logging levels to capture detailed debug information or to suppress verbose warnings from specific components. Set the com.ca.ad.sv.bespin level to WARN or DEBUG when troubleshooting connection or certificate issues Errors in VS Catalog.

logging:
  file:
    name: log/vscatalog.log
  level:
    root: INFO
    com.ca.ad.sv: INFO
    com.ca.ad.sv.bespin: DEBUG
    org.springframework: WARN
    org.eclipse.jetty.security.SecurityHandler: ERROR

Implementation

1. Open the application.yml file located in your VS Catalog configuration directory.
2. Apply the desired logging and rolling policy properties as shown above.
3. Restart the VS Catalog server for the new logging configuration to take effect