Skip to main content


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

Modify Service Level Agreement settings for the Container service

Updated on October 19, 2020

The Container REST service triggers real-time container processing. You can modify the default Service Level Agreement settings for the Container service, for example, to change the maximum number of consecutive violations which the Service allows before it invokes a fallback service activity.

  1. Save the Container service into your implementation ruleset.
  2. In the Processing options section, edit the following settings as required:
    • Maximum duration for service activity (milliseconds) - The maximum time for a service activity to run. If a service exceeds the specified value, it logs a Service Level Agreement violation alert. The default value for this setting is 500.
    • Maximum consecutive violations - The maximum number of consecutive Service Level Agreement violations for the Container service. If the number is exceeded, the interval service returns the default set of actions for the Container service for a length of time defined in the Retry interval (Seconds) setting. The default value for this setting is 3.
    • Retry interval (seconds) - The time during which the interval service returns the default set of actions for the Container service. After the retry interval ends, the interval service tries to invoke the actual service activity. The default value for this setting is 10.
  • Previous topic Returning properties of an alternate SR class in a real-time container response
  • Next topic Optional: Configuring repository storage for marketing images

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us