Release Readme

Explore the release highlights, usage notes, and known issues for End-to-End Monitoring.

Version 10.15 (Preview)

This section provides a high-level preview of the enhancements and changes for the upcoming v10.15 release and are subject to minor modifications when the release becomes generally available.

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 does not occur when REST APIs are called from a SOAP API or another REST API.

Version 10.12

Highlights

New features and enhancements Description
Transaction tracing enhancements support more products and use cases The Integration Server agent has now been updated to include SW6 correlation identifier across JMS messaging. Also, End-to-End Monitoring audit levels that are used to control the tracing of Integration Server transactions, can now be set at a global level using the Integration Server Extended Settings. This does not replace the existing service level settings, but will take precedence if both settings are used for a specific service.

Enhanced group creation Creating a group of transactions now has an improved user interface with new options in the Starts with and Products involved sections. Existing transaction names can now be selected from a drop-down list, instead of typing. The transaction names are queried from your past data based on the products that you have selected in the product list.

Custom transaction tracing for enhanced filtering You can now trace your own identifier such as an order ID or a customer ID to allow you to filter and identify the transaction more easily. The identifier does not need to be unique and in fact can be used to find all distinct transactions related to a common asset such as a customer or order.



Note: This feature requires that you invoke the service pub.flow:setCustomContextID in at least one of the services related to the transaction.

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 does not occur when REST APIs are called from a SOAP API or another REST API.

Version 10.11

Highlights

New features and enhancements Description
Custom domain support A custom domain is a unique name that identifies your website. There are scenarios where you do not want to expose the default domain. In such cases, you can customize the default tenant URL and access the tenant using your own domain.
End-to-End Monitoring now supports handling traces received from tenants with dissimilar customised subdomain names in different products.
End-to-End Monitoring also supports customization of domain name for End-to-End Monitoring URL.
Hybrid Monitoring support in Microsoft Azure Hybrid monitoring was previously supported only in Amazon Web Services (AWS). You can now view end-to-end business transactions from the cloud SaaS platform through to the on-premises Integration Servers and API Gateways.
The on-premises Integration Server and API Gateway agent generated traces are now transported to the End-to-End Monitoring collector instance in the cloud. This facilitates the display of data on the End-to-End Monitoring user interface along with the rest of the traces from the hybrid transaction.
Enhanced Tracing Capabilities End-to-End Monitoring now supports asynchronous and scheduled transactions in webMethods.io Integration.

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 does not occur when REST APIs are called from a SOAP API or another REST API.

Version 2.0.0

Highlights

New features and enhancements Description
Hybrid Monitoring You can now view an end-to-end business transaction from the cloud SaaS platform through to the on-premises webMethods Integration Servers and API Gateways.
The on-premises Integration Server agent generated traces are now transported to the End-to-End monitoring collector instance in the cloud. This facilitates the display of data on the End-to-End monitoring user interface along with the rest of the traces from the hybrid transaction.
Web application enhancements You can now access End-to-End Monitoring through a product’s own App Switcher if it is monitored by End-to-End Monitoring. In earlier releases, you can access End-to-End Monitoring from only the webMethods.io Integration and the webMethods Integration Cloud App Switchers.
For Microsoft Azure based tenants, you can access End-to-End Monitoring from the cloud tenant home page and will show transactions if they pass through one of the following Software AG products: webMethods.io B2B, webMethods API Gateway, and webMethods.io Integration. Further, for Microsoft Azure based tenants, you can access End-to-End Monitoring from the Software AG Cloud App Switcher.
Currently for AWS based tenants, you can access End-to-End Monitoring by using the App Switcher available in webMethods.io Integration.

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 does not occur when REST APIs are called from a SOAP API or another REST API.

Version 1.3.1

Highlights

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:
  • Child workflow support
  • REST API invocation

Usage Notes

This section provides any additional information that you need to work with End-to-End Monitoring.