By default, all of VUEM's components will log what they do to their own logs, and in some cases to Windows Event Viewer logs. This KB article covers where to find the logs for the various VUEM components.
Norskale VUEM Agent
The Agent will always create three logs, with a fourth log created only if the Agent service is in debug mode. By default, the logs are created in non-verbose mode. To enable verbose logging (debug mode), go to Advanced Settings > Agent Options in the Administration Console and tick the “Debug Mode” checkbox (Advanced Settings > Service Options for the Norskale Agent Host Service). This is a site-wide setting and will apply to every Agent/Service connected to the site for which you enabled debug mode.
Norskale VUEM Agent Init.log
This is the initialisation log for the Agent, which will log the Agent starting up. If the Agent fails to start up, this log will likely contain the relevant error message. This log is created in the root of the current user's Users folder. Errors in this log are listed as Exceptions.
Norskale VUEM Agent.log
This is the main Agent log, which will list what instructions the Agent is processing. If one of the actions assigned to the current user is not showing, this log will likely contain the relevant error message. This log is created in the root of the current user's Users folder. Errors in this log are listed as Exceptions.
Norskale Agent Service log (Event Viewer)
This event viewer log contains events pertaining directly to the Agent service (cached settings refresh and connection events). This log is under the Applications and Services Logs category in Event Viewer.
Norskale Agent Host Service Debug.log
When debug mode is enabled for the service, the Agent service will create a new log file in verbose mode in the Agent install directory with the name "Norskale Agent Host Service Debug.log."
Norskale Administration Console
The Administration Console only creates one log file.
Norskale Administration Console Trace.log
This is the main log for the Administration Console; it is only created if the admin console is in debug mode, and will only logs exceptions. If the Administration Console is erroring out, this log will likely contain the cause of the error. This log is created in the root of the current user's Users folder. To enable verbose logging (debug mode), go to the About tab in the ribbon > Local Options and tick the “Enable Debug Mode” checkbox.
Norskale Broker Service
The Broker Service creates only one log file by default, but will create a second if verbose logging is enabled.
Norskale Broker Service (Event Viewer)
This event viewer log is where the Broker Service will log all errors when not in debug mode. This log is under the Applications and Services Logs category in Event Viewer. To enable debug mode, run the Broker Service Configuration utility and select "Enable Debug Mode" under the Advanced Settings tab.
Norskale Broker Service Debug.log
This log is created in the Broker Service install directory when verbose logging is enabled. To enable verbose logging for the Broker Service, go to the Advanced Settings tab in the Broker Service Configuration utility and tick the “Enable Debug Mode” checkbox. This will log all events, and errors are logged as Exceptions.
Norskale Database Management utility
The Database Management utility only creates one log file.
Norskale Database Management Utility Debug Log.log
This log is created whenever the Database Management utility attempts a database creation or upgrade, and logs all errors pertaining to those operations. This log is created in the Norskale Infrastructure service's install directory.
Agent Debug Mode Local Override
In cases where the agent cannot connect to the broker, toggling debug mode on in the admin console will not work, as the agent will not be able to connect to retrieve the updated settings. To set debug mode as a local override, open regedit and browse to the following registry key:
To force debug mode on for the agent, set AgentDebugModeLocalOverride to 1, close the agent and re-launch it manually. To force debug mode on for the agent service, set AgentServiceDebugModeLocalOverride to 1, then restart the agent service.