Release 10.16 (Preview)

This section provides a high-level preview of the enhancements and changes for the upcoming release and are subject to modifications when the release becomes generally available.

What's New

Security enhancements

Reliability and Performance enhancements

Tracing enhancements

The following products and use cases are now supported by End-to-End Monitoring:

End-to-End Monitoring tracing capabilities for webMethods Cloud Container

Asset migration support

Usage Notes

This section provides any additional information that you need to work with End-to-End Monitoring.

Software AG Cloud Region Sample URL
US1 Oregon AWS https://tenantname.e2em-aw-us.webmethods.io/e2emonitoring/
US2 East Azure https://tenantname.e2em-az-us.webmethods.io/e2emonitoring/
EU2 Frankfurt AWS https://tenantname.e2em-aw-eu.webmethods.io/e2emonitoring/
EU3 West Azure https://tenantname.e2em-az-eu.webmethods.io/e2emonitoring/
AU1 Australia East Azure https://tenantname.e2em-az-au.webmethods.io/e2emonitoring/

Known Issues

This section lists the issues for this release that were known when this release readme was published.

UHM-970
In End-to-End Monitoring, API Gateway traces without a transactional event are not getting traced.

UHM-973
In End-to-End Monitoring, for a complex integration, where one SOAP API or REST API calls another SOAP API, only the starting point of the trace is captured. For the same complex integration, both the traces appear as part of its monitoring feature. The same limitation is not observed when REST APIs are called from a SOAP API or another REST API.