View List of Host Addresses for Configured Devices
Use the Log and Trace Settings page to see the list of Host Addresses for all configured devices and to configure log and trace settings for those devices.
The host address for the Controller displays two processes - OAMPserver and the name for the Unified Intelligence Center Reporting server processes running on the controller.
From the Actions column, click the ellipsis icon (...) to edit the Log, Syslog, and Subsystem server connection settings for that server process.
Logging and Tracing
Logging and Tracing are two mechanisms for application monitoring and management and are differentiated as follows:
-
Logs contain predefined, higher-level messages that can indicate everything from general system behavior to severe error conditions.
-
Traces are free-form, developer-oriented, detailed information that is not printed to the logs by default, but only when increased logging is enabled to debug problems.
You configure log levels to be Basic or Detailed. Basic is the default. When you change the log levels to Detailed, you have the opportunity to select specific trace level definitions.
There are two ways to review log and tracing information:
-
The Command Line Interface. Using the show trace command.
-
The Real Time Monitoring Tool (RTMT).
Edit Syslog Server Connection Settings
From the Log and Trace Settings list page > Actions column, click the ellipsis icon (...) and click Edit to edit the Log, Syslog, and Subsystem settings.
Caution |
Modify the settings on this page only under the direction of, and with the assistance of, your support provider. |
Log Settings
Use the following required fields to define the maximum size of the log directory and of each log file.
Field |
Description |
---|---|
Maximum Log Directory Size |
Enter a numeric value between 50 and 50,000. The default is 1,500. When the directory size exceeds 50,000, the oldest log files are deleted. |
Maximum Log File Size |
Enter a numeric value between 1 and 50. The default is 50. When a log size exceeds 50, a new log file is created. |
Syslog Settings
Use the following fields to identify the server where the log files are stored.
Note |
You must restart the Unified Intelligence Center server for the change to take effect. |
Field |
Description |
||
---|---|---|---|
Primary Host |
The host address of the primary syslog server that stores the log files.
|
||
Backup Host |
The host address of the backup syslog server that stores the log files.
|
Subsystem Settings
Click the Subsystem tab to set the log levels for each subsystem. For more information, see Log Levels and Trace Level Definitions: Basic and Detailed.
Actions on this page
-
Save - Save the changes you have made.
-
Cancel - Undo all changes you have made since the last save.
Log Levels and Trace Level Definitions: Basic and Detailed
There are two log levels for all subsystems:
Basic
This is the default log level. With this setting, messages and warnings are displayed (INFO, ERROR, and WARN).
When the log level is Basic, the trace definitions are not editable.
Detailed
If you check the detailed log level, the trace check boxes for Subsystem Specific Trace Definitions and Infrastructure Trace Definitions become editable. You can check the boxes to turn on specific trace code paths to output to the log file.
There are two ways to review log and trace information:
-
The Command Line Interface (show trace).
-
The Real Time Monitoring Tool (RTMT).
Infrastructure Trace Definitions
Infrastructure Trace definitions are the same for Unified Intelligence Center and for Operation Administration Maintenance and Provisioning (OAMP) Infrastructure and OAMP_BO. There are no Infrastructure Trace Definitions for OAMP WSM_BO.
Trace |
Description |
---|---|
TRACE_HANDLED_EXCEPTION |
Description of the exception and how it was handled |
TRACE_JMX |
JMX and management interface related traces |
TRACE_PARAM |
For any parameters (not just method arguments) |
TRACE_CALL |
For traces related to a call / call processing |
TRACE_GENERAL_CFG |
General traces for configuration API |
TRACE_OOOQUEUE |
Set this bit to enable OoOQueue tracing |
TRACE_METHOD |
When entering and exiting a method |
TRACE_LOW_LEVEL |
Bits and Bytes |
OAMP
Operation Administration Maintenance and Provisioning (OAMP) Subsystem Specific Trace Definitions
Trace |
Definition |
---|---|
TRACE_BULK |
To control logging for looping/bulk operations |
TRACE_GENERAL_UI |
For tracing the general OAMP UI |
TRACE_EXCEPTION |
For tracing Exceptions |
TRACE_PARAM |
For tracing Parameters |
TRACE_DBACCESS |
Trace DB Access for db fetch and modify such as Save, Update, Delete |
TRACE_METHOD |
For tracing of Entry/Exit of Methods |
Infrastructure
Infrastructure Subsystem Specific Trace Definitions
Trace |
Description |
---|---|
TRACE_HANDLED_EXCEPTION |
Description of the exception and how it was handled |
TRACE_JMX |
JMX and management interface related traces |
TRACE_PARAM |
For any parameters (not just method arguments) |
TRACE_CALL |
For traces related to a call / call processing |
TRACE_GENERAL_CFG |
General traces for configuration API |
TRACE_OOOQUEUE |
Set this bit to enable OoOQueue tracing |
TRACE_METHOD |
When entering and exiting a method |
TRACE_LOW_LEVEL |
Bits and Bytes |
OAMP-BO
OAMP-BO Subsystem Specific Trace Definitions
Trace |
Description |
---|---|
TRACE_BULK |
To control logging for looping/bulk operations |
TRACE_EXCEPTION |
For tracing Exceptions |
TRACE_GENERAL_BO |
General Traces for OAMP back-end |
TRACE_PARAM |
For tracing Parameters |
TRACE_DBACCESS |
Trace DB Access for db fetch and modify such as Save, Update, Delete |
TRACE_METHOD |
For tracing of Entry/Exit of Methods |
WSM-BO
WSM-BO Subsystem Specific Trace Definitions
Trace |
Description |
---|---|
TRACE_EXCEPTION |
For tracing Exceptions |
TRACE_GENERAL_BO |
General Traces for OAMP back-end |
TRACE_PARAM |
For tracing Parameters |
TRACE_DBACCESS |
Trace DB Access for db fetch and modify such as Save, Update, Delete |
TRACE_METHOD |
For tracing of Entry/Exit of Methods |
CUIC
CUIC Subsystem Specific Trace Definitions
CUIC Subsystem, Cache, Thread, Schedule, Util, Statistics, JMX, I18N, L10N, Message, Help
Trace |
Definition |
---|---|
CUIC_SUBSYS_SETUP |
Trace for CuicSubsystem setup |
CUIC_SUBSYS_OBJECT |
Trace for CuicSubsystem object dump |
Infrastructure
Infrastructure Subsystem Specific Trace Definitions
Trace |
Description |
---|---|
TRACE_HANDLED_EXCEPTION |
Description of the exception and how it was handled |
TRACE_JMX |
JMX and management interface related traces |
TRACE_PARAM |
For any parameters (not just method arguments) |
TRACE_CALL |
For traces related to a call / call processing |
TRACE_GENERAL_CFG |
General traces for configuration API |
TRACE_OOOQUEUE |
Set this bit to enable OoOQueue tracing |
TRACE_METHOD |
When entering and exiting a method |
TRACE_LOW_LEVEL |
Bits and Bytes |
CUIC Model Objects
CUIC Model Objects Specific Trace Definitions for Reports, Report Definitions, Templates, Dashboards, folders, Value Lists, and Collections.
Trace |
Description |
---|---|
MODEL_DASHBOARD |
Trace dashboard objects |
MODEL_DATA_SOURCE |
Trace data source objects |
MODEL_REPORT_DEFINITION |
Trace report definition objects |
MODEL_COLLECTION |
Trace collection objects |
MODEL_REPORT |
Trace report objects |
MODEL_VALUE_LIST |
Trace value list objects |
CUIC Data Processing
CUIC Data Processing Subsystem Specific Trace Definitions for Data Source, Data Processing, and Hibernate.
Trace |
Description |
---|---|
DCP |
Trace for DCP other than worker threads |
DCP_WORKER |
Trace for DCP worker threads |
CUIC Security
CUIC Data Processing Subsystem Specific Trace Definitions for Encryption, Permission, User, Group, and ICM User Synchronization.
Trace |
Description |
---|---|
PERMISSION_OPERATION |
Trace for security operation details |
PERMISSION_OBJECT |
Trace for security object details |