Explore the release highlights, usage notes, and known issues for webMethods.io End-to-End Monitoring.
|New features and enhancements||Description|
|Environment groups and stages||You can now get a granular view of the transaction data by filtering the transactions based on the environment group and the related stages. Customers implement their solutions with Software AG Cloud products spanning multiple environments (one product installed in each environment) as well as each environment having stages like Development, Test, and Production.
This feature helps in providing a more granular view of the transaction data by allowing you to filter the transactions based on the environment group and the related stages. Using the environment group, you can view the transactions that span across more than one environment. Using the stages filter, you can further filter the transaction data based on different stages the environments of the selected environment group are mapped with.
|Tracing enhancements for webMethods.io Integration||Tracing enhancements have been made to End-to-End monitoring capabilities. You will now find it easier to analyze the various cross-product transactions. These additional tracing enhacements are now supported in webMethods.io Integration:
This section lists the issues for this release that were known when this release readme was published.
In webmethods.io End-to-End Monitoring, API Gateway traces without a transactional event are not getting traced.
In webmethods.io 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 does not occur when REST APIs are called from a SOAP API or another REST API.
Extra loop is observed in Network view when a workflow is invoked using a REST API.
An additional loop is noticed in the webMethods.io End-to-End monitoring Network view widget, when a workflow is called through the execution of a REST API in webMethods.io Integration.
Additional headers are noticed when executing a REST application.
When a REST application flow is run with changed header attributes, sw6 extra headers are observed in the pipeline output result as shown in the following examples:
This user interface based issue has no impact on the feature functionality.