Release 11.1.0
Explore the release highlights, usage notes, known issues, and fixes for IBM webMethods End-to-End Monitoring.
Explore the release highlights, usage notes, known issues, and fixes for IBM webMethods End-to-End Monitoring.
End-to-End Monitoring now supports improved identification of Develop Anywhere, Deploy Anywhere (DADA) runtimes using unique names. The transactions can now be filtered and grouped based on the runtime names.
End-to-End Monitoring previously only supported tracing of Integration Flow services that published messages to messaging targets. However, Flow services 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. Note that this functionality is subject to IBM webMethods Integration release v11.0.8.
End-to-End Monitoring on-premises agent has now been enhanced to simultaneously support both on-premises only transactions and hybrid integration transactions originating from the cloud. This support was previously limited to either on-premises only transactions or hybrid integration transactions originating from the cloud.
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.
Security enhancements have been implemented in End-to-End Monitoring to address vulnerabilities found in multiple third-party software components.
trace_id
of 16 characters or less.End-to-End Monitoring now supports transferring Develop Anywhere, Deploy Anywhere (DADA) transactions to OTLP targets.
setCustomTransactionId
and setCustomTransactionIds
IBM webMethods Integration Flow service built-in services now has 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.
For more details about the IBM webMethods Integration functions click here.
You can now generate an End-to-End Monitoring deep link URL using a 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.
webMethods.io End-to-End Monitoring has been renamed to IBM webMethods End-to-End Monitoring.
Security enhancements have been 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.
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.
Mapping of End-to-End Monitoring production URLs with the IBM webMethods iPaaS Regions is as follows:
IBM webMethods iPaaS 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/ |
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.