Activity log structure and types

Activity logs contain information about message flows and how they interact with external resources. They can be generated for a message flow or a resource type. Learn about the structure and content of activity logs and about the tags that enrich the log data and can be used to filter its content.

Activity log columns

The data in activity logs is organized in columns. The following columns are displayed by default:

Table 1. Log Columns
Column title Description
MessageNumber The message identifier
Severity The severity of the message (whether the message is informational, a warning or an error)
Timestamp The date and time that the activity occurred (taken from the computer that is hosting the integration server)
ThreadID The identifier of the thread on which the activity message was generated.
FormattedMessage The formatted activity message (with all inserts resolved)
Inserts The message inserts
RM A resource type name
MSGFLOW A message flow name

Activity log tags

One of the important features of the activity log is the use of tags to enrich the log data. Tags are strings that represent significant categories of data that can be used for filtering and for providing additional information.

In the Log Columns table, the column headings RM and MSGFLOW are examples of tags.

Some tags are generic across all types of log, but some are specific to individual resource types. The following tags apply to all types of activity log:

Table 2. Generic activity log tags
Name Description Valid values
RM The name of the resource type to which the activity relates
  • Aggregation
  • CICS®
  • Connect:Direct®
  • GlobalCache
  • JDEDWARDS
  • JMS
  • Kafka
  • Loopback
  • MQTT
  • ODBC
  • ODM
  • PEOPLESOFT
  • REST
  • Salesforce
  • SAP
  • SIEBEL
MSGFLOW The name of the message flow to which the activity relates Any valid message flow name
NODE The name of the message flow node from where the activity log message is generated. Any valid message flow node name
NODETYPE The type of the message flow node from where the activity log message is generated.
  • INPUT
  • OUTPUT
  • READ
  • REQUEST
  • REPLY
  • RECEIVE
  • LOG
HOSTNAME The name of the host server where the activity log message is generated. Any valid hostname
PORT The listening port of the host server where the activity log message is generated. Any valid port
CONNECTION_EVENT An event that relates to a change in the state of the connection.
  • CONNECTION_EVENT.CONNECTED
  • CONNECTION_EVENT.PLANNED_DISCONNECT
  • CONNECTION_EVENT.UNPLANNED_DISCONNECT
  • CONNECTION_EVENT.FAILURE
FILENAME A file name Any valid file name
FILEPATH The fully qualified path to the file specified using the FILENAME tag Any valid file path

For more information about the types of activities that are logged for individual resource types, and about the additional tags for particular resource types, see the following topics: