What's Stored in End-To-End Monitoring?

Knowledge base Blog
, , ,
1

integration

End-to-End Monitoring provides users of webMethods.io visibility to their transactions across webMethods.io Integration, API, and B2B as well as self-hosted Integration Server instances in Hybrid scenarios. This article will review the various fields that are stored in End-to-End Monitoring to support centralized visibility across the solution set.

As of the time of writing, the following fields are tracked for each transaction being captured at the top level as well as the component level, in each product.

Transaction Details (Top-Level)

Transaction name

The transaction name relates to an asset that produces transactions as defined by the chosen product types. For example, webMethods.io Integration generates transactions based on the name of services being run, whereas API Gateway generates transactions based on the name of the associated API.

Transaction ID

This is a custom transaction ID set by you for better traceability and usability. This field section also contains the internal Trace ID, in brackets. Trace ID is a distinct identifier for the transaction generated internally by the application.

Start period

Start time for the transaction. Time will be expressed in the User’s Time zone as specified in Software AG Cloud.

Duration

Total transaction duration is the overall time taken by a cross-product transaction to complete which includes the transit and the processing time of each service in the transaction. It is calculated as the difference of the latest end time and the earliest start time of processing amongst all the services involved in the cross-product transaction.

There can be differences between total transaction duration and the sum of the processing times of each service (shown in the business flow graph) in the cross-product transaction. These can be attributed to transit time between services due to network latency and infrastructural overheads and also due to time spent on asynchronous service calls.

Status

Status of the transaction. Currently, we have the following states:

Transaction successful.
Transaction failed.

Transaction Component Details

Application Name

Specifies which application component the transaction is executed (webMethods.io Integration, API, B2B, Integration Server, etc).

Transaction ID

This is a custom transaction ID. The value depends on the application where the component is executed.

Start period

Start time for the transaction. Time will be expressed in the user’s time zone as specified in Software AG Cloud.

Duration

Total time taken by the transaction to complete within the component. It does not include the transit time, infrastructural overheads and wait times before the service started executing in the case of asynchronous services.

Status

Status of the transaction. Currently, we have the following states:

Transaction successful.
Transaction failed.

Cause of failure

In the case of failure, this field provides the reason for the error to occur.

Tenant

Provides the tenant’s name of where the transaction is executed.

Stage

Phase at which the failure has occurred during the execution of a transaction (Development, Test, Production, etc).

Environment group

The mapped environment group where the failure has occurred during the execution of the transaction.

1 Like
2

@Ravi.Syamala_emp Thanks for this write up , Can this fields be customized and sorted based on the user preference ?

3

@DINESH_J Most welcome! The list view for transactions has a customization on viewable fields (a subset of the fields covered in this post). Additionally, the list view also has the ability to sort on Duration and Started on fields.

The rest of the fields covered in the post are available in the order presented above in the details of each transaction in End-to-End Monitoring.

4

Hi @Ravi.Syamala_emp,

Nice post.
Any plan to get this End to End Monitoring tool as On-prim version in the upcoming releases?

Now i can see only plugin available in 10.15 installer.