Activity Logs
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.
You can display Activity Log data in the Activity Log view of the web user interface, and you can also choose to write activity logs to a file. For more information, see Writing Activity Logs to files.
Activity Log columns
The data in Activity Logs is organized in columns. The following columns are displayed by default:
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 node) |
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 representing 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:
Name | Description | Valid values |
---|---|---|
RM | The name of the resource type to which the activity relates |
|
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 |
|
HOSTNAME | The name of the host server where the Activity Log message is generated | Any valid host name |
PORT | The listening port of the host server where the Activity Log message is generated | Any valid port |
CONNECTION_EVENT | An event relating to a change in the state of the connection |
|
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 |
CONFIGURABLESERVICE | The name of a configurable service | Any valid configurable service name |
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:
- Aggregation Activity Log
- CICS Activity Log
- Decision services activity log
- Global cache Activity Log
- IBM Sterling Connect:Direct Activity Log
- JMS Activity Log
- Kafka Activity log
- LoopBack Activity log
- MQTT Activity log
- ODBC Activity Log
- REST request Activity log
- Salesforce Activity log
- WebSphere Adapters Activity Log