Data Flow Probe Log Files

WrapperProbeGw.log

Records all the Probe's console output in a single log file.

• Levels:

  • Error. Any error that occurs within the Probe Gateway.
  • Information. Important information messages, such as the arrival or removal of a new task.
  • Debug. N/A

• Basic Troubleshooting: Use this file for any Probe Gateway problems to verify what occurred with the Probe Gateway at any time as well as any important problems it encountered.

probe-error.log

Summary of the errors from the Probe.

• Levels:

  • Error. All errors in the Probe components.
  • Information. N/A
  • Debug. N/A

• Basic Troubleshooting: Messages from the Probe's infrastructure only.

wrapperLocal.log

When running the Probe in separate mode (that is, the Probe Manager and Probe Gateway are installed on separate machines), a log file is also saved to the Probe Manager.

• Levels:

  • Error. Any error that occurs within the Probe Manager.
  • Information. Important information messages such as received tasks, task activation, and the transferring of results.
  • Debug. N/A

• Basic Troubleshooting: Use this file for any Probe Manager problems to verify what occurred with the Probe Manager at any time as well as any important problems it encountered.

postgresql.log

Displays database related error during the installation.

pg_upgrade.log

Shows the running details of the pg_upgrade.bat script, including the details about PostgreSQL upgrade and table splitting.

The log does not appear in the log folder by default. It appears only when you manually run the pg_upgrade.bat script or may appear when you select the upgrade option during probe installation.

• Levels:

  • Error. Any error that occurs when PostgreSQL upgrade or table splitting fails.
  • Information. Shows the console output and suggestions when it fails.
  • Debug. N/A

• Basic Troubleshooting: Check this log file when PostgreSQL upgrade or table splitting fails.

probe_upgrade_conf_merge.log

Shows the related information when probe upgrader merges configuration files.

• Levels:

  • Error. Any error that occurs when merging configuration files.
  • Information. Shows the console output of normal information.
  • Debug. N/A

• Basic Troubleshooting: Check this log file when the probe upgrade fails.

probe_auto_upgrade.log

Shows the related information when the probe auto upgrade agent upgrades a probe.

It shows in the C:\UCMDB\DataFlowProbe\runtime\log\probeUpgradeLogs\<source_version>to<target_version> folder. For example: C:\UCMDB\DataFlowProbe\runtime\log\probeUpgradeLogs\10.32to11.0.

This log file is also sent to the UCMDB server and shows as <domain_name>_<probe_name>_auto_upgrade.log in the C:\UCMDB\UCMDBServer\runtime\log\probeUpgradeLogs\<source_version>to<target_version>\failed|success folder.

• Levels:

  • Error. Any error that occurs when the probe auto upgrade agent upgrades a probe.
  • Information. Shows the console output of normal information.
  • Debug. N/A

• Basic Troubleshooting: Check this log file when the probe auto upgrade fails.

probeGW-taskResults.log

Records all the task results sent from the Probe Gateway to the server.

• Levels:

  • Error. N/A
  • Information. Result details: task ID, job ID, number of CIs to delete or update.
  • Debug. The ObjectStateHolderVector results that are sent to the server (in an XML string).

• Basic Troubleshooting:

  • If there is a problem with the results that reach the server, check this log to see which results were sent to the server by the Probe Gateway.

  • The results in this log are written only after they are sent to the server. Before that, the results can be viewed through the Probe JMX console (use the ProbeGW Results Sender MBean). You may have to log in to the JMX console with a user name and password.

probeGW-tasks.log

Records all the tasks received by the Probe Gateway.

• Levels:

  • Error. N/A
  • Information. N/A
  • Debug. The task's XML.

• Basic Troubleshooting:

  • If the Probe Gateway tasks are not synchronized with the server tasks, check this log to determine which tasks the Probe Gateway received.

  • You can view the current task's state through the JMX console (use the Discovery Scheduler MBean).

probeMgr-performance.log

Performance statistics dump, collected every predefined period of time, which includes memory information and thread pool statuses.

• Levels:

  • Error. N/A
  • Information. N/A
  • Debug. N/A

• Basic Troubleshooting:

  • Check this log to investigate memory issues over time.

  • The statistics are logged every 1 minute, by default.

probeMgr-adaptersDebug.log

normalization.audit.log

Logs information about the processing of the Discovery Rules Engine.

• Levels:

  • Error. N/A

  • Information. Audits the number of element processed and the number of CIs that were changed.

    Example:

    Normalization (OSHV: 8 elements) (Time: 125 ms) (Modified CIs: 1)

  • Debug. N/A

Logs detailed information about the processing of the Discovery Rules Engine, enabling you to trace detailed information of the Discovery Rule Engine process.

• Levels:

  • Error. All discovery rule processing errors.

  • Information. Logs all levels of information about the processing of the Discovery Rules Engine.

  • Debug. Logs mainly for debugging purposes.
• Basic Troubleshooting. Check this log when you need to analyze why a CI was not enriched by the Discovery Rules Engine.