What's New

End-to-End Monitoring dual channel support has been extended to on-premises End-to-End Monitoring hybrid integration agent v10.15 that provides simultaneous transaction monitoring for both hybrid integrations and self-hosted originating transactions. This support will soon be extended to hybrid integration agent v11.1 and v10.11, subject to the respective hybrid integration agent releases v11.1 fix 2 and v10.11 fix 13.

Click Dual channel support for more details.

Security enhancements are implemented in End-to-End Monitoring to address vulnerabilities found in multiple third-party software components.

End-to-End Monitoring documentation now provides details on configuring a proxy server for the on-premises End-to-End Monitoring agent and collector connectivity.

Click Configuring a proxy server for more details.

End-to-End Monitoring now supports improved identification of Develop Anywhere, Deploy Anywhere (DADA) runtimes through unique names. The transactions can now be filtered and grouped based on the runtime names.

Click Creating a Group of Transactions for more details.

End-to-End Monitoring previously only supported tracing of IBM® webMethods Integration Flow services that published messages to messaging targets. However, Flow services that are initiated by the subscriber that received the message were not traced.

End-to-End Monitoring now supports the capture of IBM webMethods Integration Flow service traces initiated through subscribers. The Flow service traces are now linked to the parent publisher Flow services to provide a single view of the transaction. This feature is subject to IBM webMethods Integration release v11.0.8.

Click IBM webMethods Integration and Flow services for more details.

End-to-End Monitoring on-premises agent has been enhanced to simultaneously support both on-premises only transactions and hybrid integration transactions that originate from the cloud. This support was previously limited to either on-premises only transactions or hybrid integration transactions originating from the cloud.

Click Dual channel support for more details.

End-to-End Monitoring OTLP-based tracing for on-premises only use cases is now certified to work with more APM targets such as IBM Instana® and AppDynamics.

Click Supported APM systems for more details.

Security enhancements have been implemented in End-to-End Monitoring to address vulnerabilities found in multiple third-party software components.

• End-to-End Monitoring now supports self-hosted transaction monitoring with APM targets that accept a trace_id of 16 characters or less.
• End-to-End Monitoring now supports self-hosted transaction monitoring for 10.11 and 10.15 through IBM webMethods Update Manager, and for 11.1.0 through IBM webMethods Installer.

Click Self-hosted Transaction Monitoring for more details.

End-to-End Monitoring now supports transferring Develop Anywhere, Deploy Anywhere (DADA) transactions to OTLP targets.

IBM webMethods Integration Flow service built-in services now have a new group E2E Monitoring that contains the functions setCustomTransactionId and setCustomTransactionIds. You can use these functions to set the custom transaction ID in End-to-End Monitoring as individual values or as an array of key value pairs.

Click Finer details on custom transaction IDs for more details.

You can now generate an End-to-End Monitoring deep link URL by using an SW key available in your transaction. This feature facilitates easier access to End-to-End Monitoring through deep link capability from other IBM webMethods iPaaS products.

Click Generating a deep link URL from SW key for more details.

webMethods.io End-to-End Monitoring has been renamed to IBM webMethods End-to-End Monitoring.

Security enhancements are implemented in End-to-End Monitoring to address vulnerabilities found in multiple third-party software components.

Performance enhancements have been implemented at the application level to reduce the load on the back-end system.