Table of Contents

Search

  1. Preface
  2. Workflow Manager
  3. Workflows and Worklets
  4. Sessions
  5. Session Configuration Object
  6. Tasks
  7. Sources
  8. Targets
  9. Connection Objects
  10. Validation
  11. Scheduling and Running Workflows
  12. Sending Email
  13. Workflow Monitor
  14. Workflow Monitor Details
  15. Session and Workflow Logs
  16. Session Properties Reference
  17. Workflow Properties Reference

Log Events Window

Log Events Window

View log events in the Log Events window. The Log Events window displays the following information for each session and workflow:
  • Severity.
    Lists the type of message, such as informational or error.
  • Time stamp.
    Date and time the log event reached the Log Agent.
  • Node.
    Node on which the Integration Service process is running.
  • Thread.
    Thread ID for the workflow or session.
  • Process ID.
    Windows or UNIX process identification numbers. Displays in the Output window only.
  • Message Code.
    Message code and number.
  • Message.
    Message associated with the log event.
By default, the Log Events window displays log events according to the date and time the Integration Service writes the log event on the node. The Log Events window displays logs consisting of multiple log files by node name. When you run a session on a grid, log events for the partition groups are ordered by node name and grouped by log file.
You can perform the following tasks in the Log Events window:
  • Save log events to file.
    Click Save As to save log events as a binary, text, or XML file.
  • Copy log event text to a file.
    Click Copy to copy one or more log events and paste them into a text file.
  • Sort log events.
    Click a column heading to sort log events.
  • Search for log events.
    Click Find to search for text in log events.
  • Refresh log events.
    Click Refresh to view updated log events during a workflow or session run.
When you view a log larger than 2 GB, the Log Events window displays a warning that the file might be too large for system memory. If you continue, the Log Events window might shut down unexpectedly.