(CO) Support Tip: How to configure VMware collection trace logging using the pvsupport.sh utility
Hello CO Community,
In a previous CO Support Tip post, I mentioned how to configure debugging or trace level logging for for VMware data collection. Select this link to read that post.
It's nice to know how to configure this logging but is there a more automated way to do it without requiring manual modification of the VILog4j.xml file? The answer is yes.
Included within the PVTK utilities is the pvsupport.sh command. This command has the ability to set trace level logging options for different parts of the product using the "-trace" feature. Please read the Quick Reference Guide included with the bundle for more information. One of those options is setting the trace level logging for the 'collector'.
The "-trace" feature of the pvsupport.sh script has many different options that can be very helpful in many ways. Here are some of the different options that are available for the 'collector'.
- Show the current collector trace settings:
# /opt/OV/contrib/PVTK/pvsupport.sh -trace collector
- Set 'trace' level logging for collector (maximum info)
# /opt/OV/contrib/PVTK/pvsupport.sh -trace collector:trace
- Set 'trace' level logging for collector (maximum info) and set maximum log file size to 40960 and maximum 20 backup log files.
# /opt/OV/contrib/PVTK/pvsupport.sh -trace collector:trace:40960:20
- Set 'trace' level logging for collector back to the default settings of 'info' level logging, the maximum log file size to 20480 and maximum 5 backup log files..
# /opt/OV/contrib/PVTK/pvsupport.sh -trace collector:info:20480:5
An additional feature is that each time you run any of the commands that modifies the VILog4j.xml file, it creates a backup copy of the previous file prior to the modification in the same directory with the date/timestamp appended to the end of the file.
I hope that this information is helpful.
Have a great weekend!
Micro Focus SW Support Engineer