Increasing the Logging Level for the AppVolumes Manager
search cancel

Increasing the Logging Level for the AppVolumes Manager

book

Article ID: 344596

calendar_today

Updated On:

Products

VMware

Issue/Introduction

This article provides information to increase the Logging level to Debug for troubleshooting purposes
 
Note: By default, AppVolumes Manager logs are set to the INFO level.


Environment

VMware App Volumes 2.6.0
VMware App Volumes 2.5.x
VMware App Volumes 2.10.x
VMware App Volumes 2.7.x
VMware App Volumes 2.5.0
VMware App Volumes 2.9.x
VMware App Volumes 2.5.2
VMware App Volumes 2.5.1
VMware App Volumes 4.x

Resolution

To increase the Logging level to DEBUG:
  1. Log in to the AppVolumes Manager.
  2. Navigate to C:\Program Files (x86)\CloudVolumes\Manager\config
  3. Open the log4r.yml file using a text editor such as Notepad or Wordpad.
     
    Note: Ensure to take a backup of log4r.yml file before proceeding.

     
  4. Search for these lines in the log4r.yml file:
    standard_debug_dev: &standard_debug_dev
    <<: *standard
    level: <%= !Rails.env.production? || DEBUG ? 'DEBUG' : 'INFO' %>
    
    standard_debug_only: &standard_debug_only
    <<: *standard
    level: <%= DEBUG ? 'DEBUG' : 'INFO' %>
  5. Change the value INFO to DEBUG:
     
    standard_debug_dev: &standard_debug_dev
    <<: *standard
    level: <%= !Rails.env.production? || DEBUG ? 'DEBUG' : 'DEBUG' %>
    
    standard_debug_only: &standard_debug_only
    <<: *standard
    level: <%= DEBUG ? 'DEBUG' : 'DEBUG' %>
  6. Save and close the file.
  7. Restart the AppVolumes Service.
  8. Log in to the Appvolumes page and enter http://Appvolumes:Port/log. It should have Debug entries.
Note: Leaving the log4r.yml file to DEBUG may consume a lot of space. Therefore, it is recommended to change it back to INFO after the required Log Bundle is collected.


Last Validated: November 2023
Next Validation: November 2024