Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Service REST monitoring

Updated on April 6, 2022

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.

Caution: Monitoring is not recommended for production environments because it might affect performance. 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 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.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us