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.
The configuration for specifying when to monitor a Service REST rule is hierarchical,
based on the service/EnableGlobalMonitoring
dynamic system setting, the
service package settings, and the individual Service REST rule setting.
The service/EnableGlobalMonitoring
dynamic system setting with owning
ruleset Pega-IntegrationEngine
, can be set to On,
Off, or Deferred (the default). When set to
On, all REST services in the system are monitored. When set to
Off, no REST services in the system are monitored. When set to
Deferred, you can configure monitoring on the service package or
individual service level. If the setting does not exist, the default behavior is the same as
if it is set to Deferred.
Monitoring at the service package and individual service level is configured on the rule forms. When monitoring is set to On at the service package level, all REST services in the package are monitored. When monitoring is set to Off at the service package level, no REST services in the package are monitored. When monitoring is set to As defined on the service rule, you can configure monitoring at the individual service level.
At the individual service level, monitoring can be set to either On or Off.
At the service package and service level, you can also configure whether to capture the state of the primary data page.