Package Management Log

By default, whenever you execute a command using the Cloudhouse.Package.Management.exe, the Package Management Log Cloudhouse.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.

Log Format

The entries in the Cloudhouse.PackageManagement.log 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:

  • INFO – General information about what is happening during each command.

  • ERROR – Errors that have stopped the command from succeeding.

  • DEBUG – Detailed information of each command.

Component

The area 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-01-10 17:16:48,592 – 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.

Note: 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 more information.