Service REST monitoring
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.
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 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 can purge service monitoring instances on demand on the service package rule form, or purge instances automatically by enabling the Pega-provided agent and by configuring a dynamic system setting.
- Configuring Service REST rule monitoring
To use monitoring, you must turn it on for the rules that you want to trace. You can configure monitoring to monitor all Service REST rules in the system, all rules in a service package, or individual Service REST rules. Monitoring is useful for debugging your application during development, for example, if a request is failing.
- Automatically purging invocation history
If you are monitoring Service REST rules, the invocation history can become large and take up space in the database. You can purge invocation history automatically to delete data that you no longer need from the database.
Previous topic URI template component requirements Next topic Configuring Service REST rule monitoring