EVENTS Structure - 7.1

Talend ESB Infrastructure Services Configuration Guide

EnrichVersion
7.1
EnrichProdName
Talend Data Fabric
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Open Studio for ESB
Talend Real-Time Big Data Platform
EnrichPlatform
Talend ESB
Talend Runtime
task
Design and Development
Installation and Upgrade

This is the information stored in the Service Activity Monitoring Server database on a particular event:

Field

Type

Description

ID bigint(20) The persistence id of the Event.
MESSAGE_CONTENT longtext The SOAP or REST message content which comes from Service Provider/Service Consumer. Note: It will be null for all Lifecycle Events.
EI_TIMESTAMP datetime The time at which the Event is created.
EI_EVENT_TYPE varchar(255) EventType is an enumeration. Values: REQ_IN; REQ_OUT; RESP_IN; RESP_OUT; FAULT_IN; FAULT_OUT; SERVER_START; SERVER_STOP; SERVICE_START; SERVICE_STOP; CLIENT_CREATE; CLIENT_DESTROY
ORIG_CUSTOM_ID varchar(255) Reserved field. It is not being used, currently.
ORIG_PROCESS_ID varchar(255) The process id is the OS process id.
ORIG_HOSTNAME varchar(128) The name of the Host on which the SAM agent is running.
ORIG_IP varchar(64) The IP address of the Host on which the SAM agent is running.
MI_PORT_TYPE varchar(255) The Service port type which enabled the SAM agent. Note: It will be null for SERVER_START/SERVER_STOP Events.
MI_OPERATION_NAME varchar(255) The Service operation name which enabled the SAM agent. It can be standard QName operations for SOAP events and GET/POST methods for REST events. Note: It will be null for all Lifecycle Events.
MI_MESSAGE_ID varchar(255)

The MessageID which is generated/transfered using the CXF Addressing feature, for SOAP events. According to the common definition of the MessageId in the WS-Addressing specifications: REQ_OUT and REQ_In are the same message, so they should have the same MessageId; and, RESP_OUT and RESP_IN are the same message, so they should have the same MessageId too.

Note:

  1. The MessageID will be null for all Lifecycle Events.

  2. If log.enforceMessageIDTransfer=false and does not enable the WSAddressingFeature or Policy with Addressing explicitly, it will also be null.

  3. It will be null for REQ_IN/RESP_OUT if the WS-Addressing feature is enabled only on the provider side and not enabled on the consumer side.

For REST events, this field is null.

MI_FLOW_ID varchar(64) The unique id (UUID) for the message flow. All events with the same id belong together. Note: It will be null for all Lifecycle Events.
MI_TRANSPORT_TYPE varchar(255)
The transport type of the event:
  • http://schemas.xmlsoap.org/soap/http for SOAP events,

  • http://cxf.apache.org/transports/http for REST events.

Note: It will be null for all Lifecycle Events.
ORIG_PRINCIPAL varchar(255) The principal info in the message header. Note: It will be null for all Lifecycle Events.
CONTENT_CUT tinyint(1) Flag, if the event content has been cut from the Agent. Note: It will be null for all Lifecycle Events.