Business Transaction Details Page
The business transaction details page provides the following information about the transaction:
Parameter | Description |
Name | Transaction name. |
Trace ID | Distinct identifier for the transaction generated internally by the application. |
Status | Status of the transaction. |
Start period | Time at which the transaction started. |
End period | Time at which the transaction ended. |
Duration (ms) | Total time taken by the transaction to execute. This includes the time taken by the transaction to process within each component and any network latency to or from the client. For more information, see
Duration |
Duration
Duration is the total time taken by a transaction from the time a client initiates a request to the time a response is received by the client.
Let us consider the following scenario where the duration for a transaction to complete is 200ms. In the following image, 200ms is the time difference between INT22 and INT11. The time taken by the transaction within the API component which is 50ms is already taken into account as part of this 200ms value. End-to-End Monitoring records the duration only from the time a client request enters the first component of the cloud platform (INT11) and the time the response exits the last component of the cloud platform (INT22).
Note:
The application does not note the time the client sends the request (T1) and the time the client receives the response (T2), as this happens outside the Software AG environment.
Business Flow Map
This provides a logical representation of the business flow showing the path taken by the transaction through the various cloud components. Also, the processing time for the transaction within each component is visible.
A legend is available to identify the status of a transaction. An example of a business flow is as follows:
The Business Flow Map also shows details when there is a cross-domain transaction. A cross-domain transaction is one where the client makes a call to a supported component in one tenant and then the call moves to a component in another tenant. For example, let us consider the following image. Here, a client calls an Integration Cloud instance in one tenant and then the transaction moves to call another Integration Cloud instance in a different tenant. When you select the component, you can view the corresponding tenant name in the component details pane. In the following example, the second Integration Cloud instance is highlighted along with its tenant name.
