By default, whenever you execute a command using the Package Management Executable (using Cloudhouse.Package.Management.exe), the Package Management Log PackageManagement.log is created in the same folder that the executable was run from.
The log is also output to the console at the same time.
Note
The Package Management Log leverages log4net. Please see their website for further information.
The configuration of the Package Management log file and its behaviour is controlled via the Cloudhouse.package.management.exe.config configuration file, found in the same location as the Package Management Executable.
Note
The configuration file contains the recommended settings for a Compatibility Package, but you can modify this file to control the behaviour of logging, as detailed in Configuring Logging for an Alchemy Compatibility Package.
Log Format
The entries in the PackageManagement.txt are formatted as follows:
%Date% %LogLevel% %Component% - %Message%"where:
| Category | Description |
|---|---|
| Date | Date and time the log file entry was written. |
| LogLevel | Defines the type of log entry:
|
| Component | The command the log line relates to. For example, “VerificationWorkflow” relates to the --verify flag. |
| Message | The message associated with the log line. |
For example:
2023-10-17 10:46:07,281 INFO VerificationWorkflow - Verifying connection to licensing servers.
where:
- 2023-10-16 10:46:07,281 - is the Date and Time the message was written.
- INFO - is the log level.
- VerificationWorkflow - is the relevant Component
- Verifying connection to licensing servers - is the message.
Warning
By default, INFO logs are created during package management. Setting the log level to DEBUG increases the verbosity of the logs and should only be used during troubleshooting.
See the Configuring DEBUG Logging section of Configuring Logging for Alchemy Compatibility Packages.