Release 1.3.1
Explore the release highlights for End-to-End Monitoring.
Highlights
No subtopics in thissection
| 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 IBM webMethods iPaaS products spanning multiple environments (one product installed in each environment) as well as each environment having stages like Development, Test, and Production. This feature provides 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 IBM webMethods 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 enhancements are now supported in IBM webMethods Integration:
|
Usage Notes
No subtopics in thissection
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.
