Explore the release highlights for End-to-End Monitoring.
|New features and enhancements||Description|
|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||
|Documentation enhancements||End-to-End Monitoring documentation is now independent of webMethods.io Integration documentation for better visibility and ease of access.|
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 FlowService 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 Software AG 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:
Software AG Cloud products are available in several geographical regions, operated by different infrastructure providers. Go to the Software AG Cloud 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.
This section lists the issues for this release that were known when this release readme was published.
In End-to-End Monitoring, API Gateway traces without a transactional event are not getting traced.
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.