Release 10.15.0

Explore the release highlights for End-to-End Monitoring.

Highlights

New features and enhancements	Description
Release 10.15.2
Security enhancements	Security enhancements are made to address vulnerabilities in numerous third-party software components of End-to-End Monitoring.
Transaction duration calculation enhancement	Enhancements are made to total transaction duration calculation to highlight bottlenecks in cross-product transactions. Refer FAQs for more details.
Network diagram enhancements	Enhancements are made to the network diagram of the End-to-End Monitoring user-interface dashboard to display product nodes better. This enhancement is applicable even when all products supported by End-to-End Monitoring are being used by the tenant.
Access control improvements	Currently, if a tenant is eligible to have End-to-End Monitoring capability then all users within that tenant get access to it. The limitation with this implementation is that a IBM webMethods iPaaS user with no access to any product, could still access End-to-End Monitoring. This has now been addressed with user level access control. A IBM webMethods iPaaS user can now access End-to-End Monitoring only if assigned a role that provides access to IBM webMethods Integration product, which is usually a key product with relevance to End-to-End Monitoring.
Fixes included in the 10.15.2 release	See the Fixes section for information on the 10.15.2 fixes.
Release 10.15.1
Hybrid Integration monitoring enhancements	Collector end-point is now fetched dynamically during Integration Server start-up. Hence, you will no more be required to manually configure the collector end-point for hybrid monitoring in Integration Server.
Reliability enhancements for improved monitoring	A Redis based intermediate storage has been introduced to store the incoming transaction traces from End-to-End Monitoring agents. This minimizes the transaction trace losses when the primary data store is temporarily unavailable. There is also a more robust retry mechanism in place for the transaction traces rejected by the data store due to the temporary unavailability. Reliability improvements in the Agent-Collector communication. Foundational work to support capabilities for upcoming releases. These include Enterprise Disaster Recovery, and dedicated storage to enable cross-product transaction traces beyond the current period of 7 days.
Documentation enhancements	End-to-End Monitoring documentation is now independent of IBM webMethods Integration documentation for better visibility and ease of access.

Usage Notes

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

Additional headers are noticed when running a REST application.
When a REST application Flow service is run with changed header attributes, sw6 headers are observed in the pipeline output result. sw6 is a valid request header used by End-to-End Monitoring for monitoring IBM product runtimes. This has no impact on feature functionalities.
End-to-End Monitoring is supported on the latest version of Google Chrome web browser (v105 or later).
After End-to-End Monitoring is upgraded, the older version browser’s cache and cookies are not cleared automatically. This may lead to incorrect display of page content. Ensure that you clear the browser’s cache manually after every upgrade, and then access End-to-End Monitoring.
End-to-End Monitoring is best experienced when the scale and layout are adjusted to the following settings:
IBM webMethods iPaaS products are available in several geographical regions, operated by different infrastructure providers. Go to the IBM webMethods iPaaS Regions website for more information.
Information on major releases, hotfixes, and patch releases including the latest statistics on the availability of cloud environments, incident history, and planned maintenance events are available on the webMethods.io iPaaS Service Status page.

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.

Fixes

This section provides information on the fixes for End-to-End Monitoring.

Version	Issue ID	Release Date	Region/Customer	Description
10.15.2	UHM-3148 UHM-3147 UHM-3146 UHM-3145 UHM-3179 UHM-3190	December 9, 2022 December 9, 2022 December 10, 2022 December 10, 2022 December 10, 2022 December 10, 2022	AU1 Australia East Azure AU2 Sydney AWS EU2 Frankfurt AWS US1 Oregon AWS EU3 West Azure US2 East Azure	Security enhancements.
10.15.2	UHM-3169	December 9, 2022 December 9, 2022 December 10, 2022 December 10, 2022 December 10, 2022 December 10, 2022	AU1 Australia East Azure AU2 Sydney AWS EU2 Frankfurt AWS US1 Oregon AWS EU3 West Azure US2 East Azure	Transaction duration calculation enhancements.
10.15.2	UHM-3060	December 9, 2022 December 9, 2022 December 10, 2022 December 10, 2022 December 10, 2022 December 10, 2022	AU1 Australia East Azure AU2 Sydney AWS EU2 Frankfurt AWS US1 Oregon AWS EU3 West Azure US2 East Azure	Network diagram enhancements.
10.15.2	UHM-3229	December 9, 2022 December 9, 2022 December 10, 2022 December 10, 2022 December 10, 2022 December 10, 2022	AU1 Australia East Azure AU2 Sydney AWS EU2 Frankfurt AWS US1 Oregon AWS EU3 West Azure US2 East Azure	Access control improvements