Setting trace levels for the components of an internal System Monitoring shared service

You can set the trace level for the components of the System Monitoring shared service to determine the type and amount of information that is added to the log files.

1. Click Patterns > Shared Services Instances. If you are on 2.3.3.3, click Patterns > Manage > Shared Service Instances.
   The Shared Service Instances page displays the list of shared services, grouped by shared service type. The list is displayed in a table format, providing some basic details about each shared service.

   The following functions are available for you to work with the list of shared service instances:

   Refresh

   Refreshes the status of the shared service instances and updates the fields on the Shared Service Instances page.

   Create New

   Click Create New to create a new shared service instance.

   Filter

   Enter a term that is used to filter the shared service instances that display on the page.

2. Select the instance of the System Monitoring shared service for which you want to set the trace levels from the list.
   Details about the shared service display in the Shared Service Instances pane.
3. Click Manage.
   The Instance Console window opens and the Monitoring pane is displayed.
4. Click the Operations tab.
   The Operations pane is displayed.
5. Select one of the following components:
   • DW to set trace levels for one of the following components:
     • Summarization and Pruning Agent
     • Warehouse Proxy Agent
   • HTEMS to set trace levels for one of the following components:
     • Hub Tivoli® Enterprise Monitoring Server
     • Cloud Pak System Software Agent
     • Tivoli Enterprise Portal Server
   • RTEMS to set trace levels for one of the following components:
     • Remote Tivoli Enterprise Monitoring Server
     • Warehouse Proxy Agent
6. Depending on the role that you selected in step 5, do one of the following steps:
   • If you selected DW:
     1. Click Set Trace Level for Warehouse Proxy Agent or Set Trace Level for Summarization and Pruning Agent, depending on the service component for which you want to set a trace level.
     2. In the Trace Log Parameters field, enter the trace command that corresponds to the trace information you want to log. There are two types of tracing, component level tracing and file level tracing. The following list describes the tracing levels available:

        Trace levels

        All: Provides all trace levels.

        Flow: Provides control flow data describing function entry and exit.

        Error: Logs internal error conditions.

        Detail: Produces a detailed level of tracing.

        Input: Records data created by a particular API, function, or process.

        Metrics: Records data for a particular metric.

        Output: Records data disseminated by a particular API, function, or process.

        State: Records the condition or current setting of flags and variables in the process. If state tracing is enabled, you can see the current state of particular variables or flags as the process is running.

        For example, if you enter the following command in the Trace Log Parameters field:

        (UNIT:kbbacdl Flow State)

        it turns on the flow and state tracing for all files whose names start with kbbacdl in the IBM® Tivoli Monitoring component.
        If you enter the following command,

        (COMP:kdh Detail)

        it turns the detail tracing on for all files that are identified as part of the kdh component.
     3. Click Submit to confirm.
   • If you selected HTEMS:
     1. Click Set Trace Level for Hub TEMS, Set Trace Level for TEPS, or Set Trace Level for Cloud Pak System Software Agent, depending on the service component for which you want to set a trace level.
     2. In the Trace Log Parameters field, enter the trace command that corresponds to the trace information you want to log. There are two types of tracing, component level tracing and file level tracing. The following list describes the tracing levels available:

        Trace levels

        All: Provides all trace levels.

        Flow: Provides control flow data describing function entry and exit.

        Error: Logs internal error conditions.

        Detail: Produces a detailed level of tracing.

        Input: Records data created by a particular API, function, or process.

        Metrics: Records data for a particular metric.

        Output: Records data disseminated by a particular API, function, or process.

        State: Records the condition or current setting of flags and variables in the process. If state tracing is enabled, you can see the current state of particular variables or flags as the process is running.

        For example, if you enter the following command in the Trace Log Parameters field:

        (UNIT:kbbacdl Flow State)

        it turns on the flow and state tracing for all files whose names start with kbbacdl in the IBM Tivoli Monitoring component.
        If you enter the following command,

        (COMP:kdh Detail)

        it turns the detail tracing on for all files that are identified as part of the kdh component.
     3. Click Submit to confirm.
   • If you selected RTEMS:
     1. Click Set Trace Level for Remote TEMS or Set Trace Level for Warehouse Proxy Agent depending on the service component for which you want to set a trace level.
     2. In the Trace Log Parameters field, enter the trace command that corresponds to the trace information you want to log. There are two types of tracing, component level tracing and file level tracing. The following list describes the tracing levels available:

        Trace levels

        All: Provides all trace levels.

        Flow: Provides control flow data describing function entry and exit.

        Error: Logs internal error conditions.

        Detail: Produces a detailed level of tracing.

        Input: Records data created by a particular API, function, or process.

        Metrics: Records data for a particular metric.

        Output: Records data disseminated by a particular API, function, or process.

        State: Records the condition or current setting of flags and variables in the process. If state tracing is enabled, you can see the current state of particular variables or flags as the process is running.

        For example, if you enter the following command in the Trace Log Parameters field:

        (UNIT:kbbacdl Flow State)

        it turns on the flow and state tracing for all files whose names start with kbbacdl in the IBM Tivoli Monitoring component.
        If you enter the following command,

        (COMP:kdh Detail)

        it turns the detail tracing on for all files that are identified as part of the kdh component.
     3. In the Virtual Machine IP Address field, enter the IP Address of the virtual machine on which the instance of remote Tivoli Enterprise Monitoring Server is hosted.
     4. Click Submit to confirm.