You can monitor Service REST request and response data and view the results of rule invocation by using a combination of Dynamic System Settings and options on the Service Package and Service REST rule forms. Monitoring is useful for debugging your application during development, for example, if a request is failing.
Monitoring is not recommended for production environments because it might affect performance and depending on the number of incoming service requests, there is a chance that over a period of time, the invocation history might get large enough so that you run out of database space.
To use monitoring, you must turn it on for the rules that you want to monitor. You can configure monitoring to monitor all REST service rules in the system, all rules in a service package, or individual rules. You configure monitoring by using a combination of a Dynamic System Setting and settings on the Service Package and Service Rest rule forms.
You can view the monitoring results on the service package rule in the invocation history section. From there, you can click a particular invocation and view the actual request, response, and if configured, the clipboard state at the time the rule was invoked. You must have the prDeveloperForm privilege to view invocation history.
You can purge invocation history on demand or automatically to delete data that you no longer need from the database. You can purge service monitoring instances on demand on the service package rule form. You can purge automatically by enabling the agent that is shipped with the product and by configuring a Dynamic System Setting.