Administering Mediator : Mediator Configurations : Performance Metrics and Run-Time Events Schema Published to Elasticsearch and API Portal : Transaction Events Type
Transaction Events Type
Event Type: TransactionalEvents
Key
Description
apiId
Sequential primary key. This column does not contain a NULL value.
Example: c0f84954-9732-11e5-b9f4-f159eafe47b2
apiName
Name of the API invoked. This column does not contain a NULL value.
Example: VirtualService_TransactionEvent
apiVersion
Version of the API. By default, for every version of an API a system version number is generated. At the same time, user can also provide a version number which is set as a user version.
Example: API 1.0 and API 2.0
consumerId
The system generated consumer application ID.
Example: c0f84954-9732-11e5-b9f4-f159eafe47b2
consumerIp
Consumer IP.
Example: 10.20.248.33
consumerName
Comma-separated consumer names identified based on the policy that triggered the event.
Example: <consumer application name>
creationDate
Timestamp when the event is created. Example: 2015-08-26 04:13:35 PM
eventType
Type of the event.
Value: TransactionalEvents
operationName
Virtual service operation which has been invoked.
Example: in calc API, the operations include add, sub, multi, and div. If add operation is invoked the operation name has add.
providerTime
Time interval in milliseconds from when Mediator forwards a request to the native provider until it receives the provider's response. This field includes the time it takes a provider to process the request plus any network latency to or from the provider. This field is a better indicator of the time it takes for a provider to process a request and return a response. Subtracting total time from provider time must give a rough indicator of the Mediator overhead.
Example: 120
request
CLOB with request data.
Example: <RequestPayload>
response
CLOB with response data.
Example: <ResponsePayload>
sessionId
Session token. This is the IS session token or a GUID if the token is missing from the message context.
Example: 779be3201e5f19b3b0e0ab264379ebd3
status
Formatted status based on resource message ID's.
0205.0033=SUCCESS
0205.0034=ERROR {0}
where '{0}'s is the fault reason.
Example: SUCCESS
targetName
Specifies the name of the Mediator instance from where the event is published.
Example: LOCAL-MED
totalDataSize
Combined request and response payload sizes.
Example: 100
totalTime
Time interval in milliseconds from when a request is received by the virtual service runtime until the response is returned to the caller. This field includes the overhead incurred while the message is passing through the Mediator runtime.
Example: 94
Copyright © 2015- 2017 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback