Categories

Access and Supported Products

Why don’t I see the End-To-End Monitoring option on the app switcher?

End-to-End Monitoring is currently enabled if you have an enterprise edition of webMethods.io Integration or a free trials version or the free forever edition.

Note: The free trials version is rate limited. It has limited time retention and limited number of transactions.

If you satisfy the mentioned criteria but still not able to access End-To-End Monitoring, contact Software AG Support and share the details such as tenant name, cloud provider, and region to enable the capability.

What products are currently supported by End-To-End Monitoring?

See Product Considerations for information on the products supported by End-to-End Monitoring.

How do I access the End-To-End Monitoring capability?

End-to-End Monitoring is available through the app switcher of your respective product, such as webMethods.io Integration, webMethods.io B2B or webMethods.io API.

Click Accessing End-to-End Monitoring for more details.

How is transaction duration calculated?

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.

Consider a cross-product transaction where webMethods.io API calls webMethods.io Integration WorkFlow service which in turn calls a hybrid integration call to a webMethods Integration Server service running on-premises.

The difference between the latest end time and the earliest start time captured from each of the products (API, WorkFlow, On-premises IS) constitutes the transaction duration.

If every call is synchronous, then webMethods.io API will have the latest end time and the earliest start time.

However, if there is an asynchronous call in the transaction, then the earliest start time is captured from webMethods.io API and the end time is selected from any of the products in the transaction having the latest value.