(9.0+) Core Monitor logging

Core Monitor generates the following log files:

core_monitor
queue_manager_controller
component_controller
notification_client

The Core Monitor's site.config is used to configure where the active files are located.

Where the active files are located

Core Monitor site.config File Location

This can be located on each server in the registry

HKEY_LOCAL_MACHINE\SOFTWARE\Virtual Hold
- InstallationLocation

The folder InstallationLocation is appended with \Core Monitor folder:

example = C:\Program Files (x86)\Virtual Hold Technology\Core Monitor

core_monitor logs

The Core Monitor logs show the stopping and starting of the Core Monitor. In HA environments, you will also see role negotiation during startup, and the execution of the HA failover SQL script.

core_monitor site.config logging setting

The core_monitor site.config file is located by default at C:\Program Files (x86)\Virtual Hold Technology\Core Monitor.

[ {ha_monitor,
    [
      { vht_logger_options, [{ base_log_file_path, "C:/Program Files (x86)/Virtual Hold Technology/VHLogs/Logs"}]}


Setting	Description	Value	Default
base_log_file_path	File path where the active logs should be written	Any valid directory path. This value should be the root for all log files.	C:/Program Files (x86)/Virtual Hold Technology/VHLogs/Logs

queue_manager_controller logs

Here you will see the stopping and starting of Queue Manager. You will also see the creation and deletion of records in the callback sync mnesia datastore.

Core Monitor site.config Logging Setting

{vht_ha_qm,

[

{ vht_logger_options, [{ base_log_file_path, "C:/Program Files (x86)/Virtual Hold Technology/VHLogs/Logs"}]},


Description	Setting	Values	Default
File path where active logs should be written	base_log_file_path	*Any valid directory path	N/A
Log level to write active logs	Only one log level available
Size of the active Log	N/A		10 MB
Name of log folder	base_log_file_path	Text	N/A
Name of log file	base_log_file_path	Text	N/A
How many active files to keep in the active directory	Controlled by Archive Service
When to start new log file	Active file size exceeds 10MB

*Should always be the root for ALL log files.

component_controller logs

This log records the stopping and starting of monitored components on the Core Monitor. But not Queue Manager

Core Monitor site.config Logging Setting

{vht_ha_qm,

[

{ vht_logger_options, [{ base_log_file_path, "C:/Program Files (x86)/Virtual Hold Technology/VHLogs/Logs"}]},


Description	Setting	Values	Default
File path where active logs should be written	base_log_file_path	*Any valid directory path	N/A
Log level to write active logs	Only one log level available
Size of the active Log	N/A		10 MB
Name of log folder	base_log_file_path	Text	N/A
Name of log file	base_log_file_path	Text	N/A
How many active files to keep in the active directory	Controlled by Archive Service
When to start new log file	Active file size exceeds 10MB

*Should always be the root for ALL log files.

notification_client logs

Here the status of monitored components and the Core Monitor are recorded. This will be the same status being reported to System Management.

Core Monitor site.config Logging Setting

{vht_ha_qm,

[

{ vht_logger_options, [{ base_log_file_path, "C:/Program Files (x86)/Virtual Hold Technology/VHLogs/Logs"}]},


Description	Setting	Values	Default
File path where active logs should be written	base_log_file_path	*Any valid directory path	N/A
Log level to write active logs	Only one log level available
Size of the active Log	N/A		10 MB
Name of log folder	base_log_file_path	Text	N/A
Name of log file	base_log_file_path	Text	N/A
How many active files to keep in the active directory	Controlled by Archive Service
When to start new log file	Active file size exceeds 10MB

*Should always be the root for ALL log files.