Considerations

GDPR Considerations

From a General Data Protection Regulation (GDPR) perspective, note the following considerations:

• As part of the rule creation and group creation, the application collects and stores the user ID and email address of the user in the Elastic Search database. The user ID is the ID using which the user logs into webMethods.io Integration.

• The user does not have an option to delete personal data from the Elastic Search database. However, if a tenant is deleted, then the user related data is also deleted.

• End-to-End Monitoring does not store any log information in the database.

Product Considerations

End-to-End Monitoring has the following considerations with respect to the various supported products.

webMethods Integration Cloud

Following is the current status of monitoring support in End-To-End Monitoring for HTTP-based Integration Cloud transactions:

webMethods API Gateway

Following is the current status of monitoring support in End-To-End Monitoring for HTTP-based webMethods.io API transactions:

webMethods.io B2B

Following is the current status of monitoring support in End-To-End Monitoring for webMethods.io B2B transactions:

Important:

• For End-to-End Monitoring to trace the webMethods.io B2B transactions, add the following B2B attribute of type String: e2e:ot-tracer-traceid.
  
  
  

Note:

• The document IDs of the involved documents are considered as the custom Transaction ID for webMethods.io B2B transaction traces. However for AS2 channel protocol, both document ID and message ID are considered as custom Transaction ID.
• Custom Transaction ID for B2B node in the transaction is the document ID submitted. However, custom Transaction ID for the whole transaction captures all the document IDs involved in webMethods.io B2B.
• Transaction name format is now SenderName:ChannelName instead of SenderName(Organization Unit):ChannelName.
• The following document submission types are traced from webMethods.io B2B only when cloud container tracing is enabled:
  • wm.tn:submit
  • wm.tn:submitWithAttachments
  • wm.tn.route:routeBizdoc

webMethods.io Integration and Flow services

Following is the current status of monitoring support in End-To-End Monitoring for HTTP-based webMethods.io Integration transactions:

Connectors

Following is the current status of monitoring support for webMethods.io Integration Flow service connectors and Workflow connectors in End-To-End Monitoring:

Note:

• Support for connector tracing of Flow services functionality is subject to webMethods.io Integration release v10.16.5.
• Support for connector tracing of Workflows functionality is subject to webMethods.io Integration release v11.0.3.

Multi-Hop

Following is the current status of monitoring support in End-To-End Monitoring for a transaction when it moves from one component to another:

webMethods Integration Server and Microservices Runtime

Following is the current status of monitoring support in End-To-End Monitoring for Integration Server and Microservices Runtime transactions:

webMethods Cloud Container

Following is the current status of monitoring support in End-To-End Monitoring for webMethods Cloud Container transactions:

End-to-End Monitoring support for the above listed Cloud Container use cases, is currently only available on demand for this initial release version 10.15.2. Click here to enable support for webMethods Cloud Container use cases.

Click Hybrid monitoring with Integration Server through Cloud Container services for more details.