CloudStreams 10.5 | webMethods CloudStreams | Administering webMethods CloudStreams | Policies | The Policy Actions | The Policy Action Reference | Log Invocation
 
Log Invocation
Logs request/response payloads. You can log the payloads in the database and/or send the payloads in the form of email alerts. This action also logs other information about the request/response, including the service name, operation name, the Integration Server user, a timestamp, the response time, and more.
General Data Protection Regulation (GDPR) considerations
As part of this policy action, all request/response payloads are logged in the database or can be sent in the form of email alerts. Depending on the SaaS provider requirements, some of the logged data may be personal data or personally identifiable information. If for privacy concerns or to be in compliance with General Data Protection Regulation (GDPR), you want to delete the personal data of a user, you can manage the personally identifiable information by purging it from the database.
The database used by CloudStreams has the following tables which contain request/response payloads or such information of interest. To purge the data along with the table names, the following field/column names are provided using which the data can be cleaned up.
CLS_TXN_EVENT
*REQUEST
*RESPONSE
*CONSUMER_IP
CLS_ERR_EVENT
*CONSUMER_IP
CLS_PV_EVENT
*CONSUMER_IP
CLS_MON_EVENT
*CONSUMER_IP
For email alerts, data is stored in the Integration Server logs. The log data may contain account specific or user specific data, which may be considered as personal data or personally identifiable information. If for privacy concerns or to be in compliance with General Data Protection Regulation (GDPR), you want to delete the personal data of a user, you can manage the log files that contain the data from the file system. See the webMethods Integration Server Administrator’s Guide for information on how to manage these logs, their related files, and specific identifiers to look for in the logs.
Input Parameters
Log Generation Frequency
Specifies how frequently to log the payload.
*Always: Log all requests and/or responses.
*On Success: Log only the successful requests and/or responses.
*On Failure: Log only the failed requests and/or responses.
Log the Following Payloads
Specifies whether to log all request payloads, all response payloads, or both.
*Log Request: Log all request payloads.
*Log Response: Log all response payloads.
Send Data To
Specify where to log the payloads.
*Database: Default. Logs the payloads in the CloudStreams Analytics database.
Note:
Ensure that you also select the Database Publishing option in Integration Server Administrator (go to Solutions > wst > Administration > Database), as described in Setting the Database Options for Publishing Performance Metrics and Events.
*Server Log: Logs the payloads in the server log of the Integration Server on which CloudStreams is running.
Also choose a value in the Log Level field:
*Info: Logs error-level, warning-level, and informational-level alerts.
*Warn: Logs error-level and warning-level alerts.
*Error: Logs only error-level alerts.
Note:
The Integration Server Administrator's logging level for CloudStreams should match the logging level specified for this action (in the Integration Server Administrator go to Settings > Logging > Server Logger).
Alert Email
Right-click the action name and click Add Alert Email to send the payloads in an email alert to the email address you specify in the Email ID field. You can select Add Alert Email multiple times to add multiple email addresses.
Note:
Ensure that you set the email options in Integration Server Administrator (go to Solutions > CloudStreams > Administration > Email), as described in Setting the E-mail Options for Logging Payloads and Sending Performance Monitoring Alerts.