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 April 20, 2021

Pega Foundation for Financial Services

Production maintenance and monitoring includes the following procedures:

Business rule maintenance in the Production environment

As a manager, you can update Dialogs and Coaching Tips in a production environment by using the Tools Configuration option that is available in each process action of the case type. Managers can change these options without having to wait for a rule deployment, but must have the same privileges associated with the PegaFSIF:Manager role in order to maintain these rules.

Note: You must first create Skills instances before the Skills to be available in the selection of available Expert Skills.

You can give managers the ability to update rule types in a production environment. For example, managers can update the Goals and Deadline for a certain case type. You must delegate these rules in Dev Studio first. After you delegate a rule, you can access it in the Interaction Portal by clicking Profile My rules . For more information on rule delegation, see Delegating a rule or data type.

Application monitoring

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[MJ1] , 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 perform Layer 7 health checks. Layer 7 is the application layer of the OSI model. Examining the details of a connection can allow you to filter out unwanted traffic from entering your call center, for example, DDoS attacks. Viewing connection details can also help with load balancing and provide you with the information that you need to more intelligently route calls.
  • Regularly perform health checks on the CTI layer. Periodically check to ensure that the application can communicate with the switch. Periodically call the application to ensure that it can get through the entire process.
  • Monitor your company's social media accounts (for example, Facebook and Twitter) to ensure that they do not expire. You can also monitor the social agents that are the internal background processes operating on the server that runs activities on a periodic basis.
Identifying and 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:

  • Identify the operational staff who will be responsible for responding to issues reported in the production environment.
  • Establish procedures with those resources to triage, respond to, and escalate issues.
  • 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