Skip to main content

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

Production maintenance and monitoring

Updated on February 18, 2022
Pega Knowledge Implementation Guide Pega Knowledge Implementation Guide Pega Knowledge Implementation Guide

You need to understand business rule maintenance, application monitoring, and reporting issues.

Monitoring your application

Pega Autonomic Event Services is an application that automatically monitors, retrieves, and organizes the alert data from one or more clustered systems throughout the enterprise. Pega also provides the Pega Predictive Diagnostic Cloud, which allows you to benefit from Pega Autonomic Event Services without installing it locally. Pega Predictive Diagnostic Cloud is a Software as a Service offering of Pega Autonomic Event Services.

Implementing the following best practices in your application can help to ensure optimal response times and overall application health:

  • Segment your application's agent processing to a dedicated JVM (Java Virtual Machine). This configuration ensures that end users do not have to share resources with background processes.
  • Monitor integration response times. Over time, slow integration points can cause average handle times to increase. When queues start to grow, it becomes very difficult to recover, and might require the use of offline services or a backup application.
  • Regularly check the configuration of email accounts to help avoid unnecessary exceptions and errors. Ensure that all email accounts connect to a working email server, and that there are no unnecessary outbound email accounts configured.
  • Ensure that all Pega Platform operator accounts used by your Pega Knowledge application have a valid email address. This also applies to the accounts of managers, system administrators and application administrators.
  • Configure the System Management application with access to the nodes in the system. For more information, see Managing your system.

Reporting issues

As with any application, as your users begin to use the application they will encounter issues that they need to report. When deploying your application to a production environment, complete the following steps to help your users to identify and report the issues that they find:

  1. Identify the operational staff who will be responsible for responding to issues reported in the production environment.
  2. Establish procedures with those resources to triage, respond to, and escalate issues.
  3. Determine procedures for delivery of changes to the production environment.

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