Configuring trace

To generate an output log with detailed information about IBM® Business Monitor components, you can enable tracing. To determine the level of detail to be included in the log, you can change the log details levels.

About this task

Unless Monitor server and Dashboard are federated into the same deployment manager, they are managed separately. Monitor server trace is managed by the WebSphere® Application Server that is embedded in Process Server. Dashboard trace is managed by WebSphere Application Server where WebSphere Portal is installed.

To enable tracing for lifecycle management, database services, or the Monitor server, you must configure the trace settings for the Monitor server. To enable tracing for KPI and database services, dashboards and views, you must configure the trace settings for Dashboard.

Enabling trace and altering the details that are logged in the trace logs might impact the performance of the system. Because of the performance impact, use tracing to help troubleshoot issues until they are resolved. After you have resolved the issue, you should disable tracing.

  • Enabling trace
    When enabling trace, you can configure the amount of data to be retained, as well as the location of the output that is generated. Trace is configured for each application server.
  • Changing log details levels
    To generate an output log with detailed information about IBM Business Monitor components, you can enable tracing. To determine the level of detail to be included in the log, you can change the log details levels.
Parent topic: Using logging and tracing