Release 10.15

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

Highlights

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
  • 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 webMethods.io 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.

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.