Table of Contents

Evaluating system performance after a change or upgrade with Pega Predictive Diagnostic Cloud

Monitor your system's performance to ensure that it functions correctly after a change or upgrade and to detect potential issues. Use the Changes Summary and System Assessment landing pages in Pega Predictive Diagnostic Cloud™ (PDC) to identify recent changes and evaluate your system's performance.

Use case

uPlusTelco runs a production system with Pega Platform™ applications installed. Recently, uPlusTelco system administrators completed a major upgrade to the system. However, you were not informed exactly when the upgrade was completed. As an operations manager, you are responsible for monitoring the health of this system and ensuring that your team is aware of any problems with the system's performance. According to uPlusTelco system administrators, user experience is acceptable if fewer than 1% of server interactions take longer than one second.

Before you begin

Evaluating your system's performance after a change or upgrade

  1. Log in to PDC.
  2. In the header of PDC, in the System list, select the system that has been upgraded, for example, upt-prod1.

Analyzing recently imported files

  1. In the navigation pane, click Changes Summary.
    This landing page contains a list of recent changes in your system. For more information, see Changes Summary landing page overview in Pega Predictive Diagnostic Cloud.
  2. In the Platform imports section, find an import that you want to investigate further, and note the date and time of the operation.
    Upgrades to the uPlusTelco systems are usually saved as .zip files with upt-upgrade in the name. In the following example, the upgrade is divided into several files that were imported consecutively:
    Analyzing recently imported files
    "Analyzing recently imported files"
    Analyzing recently imported files
  3. In the Rule updates section, find the first snapshot that was created immediately after the date and time of the import operation that you found in step 2.
    An upgrade typically involves a large number of rule updates, as shown in the following example:
    Analyzing the number of rule updates
    "Analyzing the number of rule updates"
    Analyzing the number of rule updates

Evaluating your system's performance

  1. In the navigation pane, click System Assessment.
    On the System Assessment landing page, you can analyze response times and interaction volume statistics for your systems.
  2. In the Interval list, select Custom time, and then, in the Date from and Date to fields, select a time period around the upgrade that you identified in step 2.
    For the uPlusTelco system, select a time period that starts at 17:00 on February 7 and ends at 19:00 on February 8.
  3. On the Distribution of healthy and slow interactions chart, compare the percentage of healthy interactions (green) with the percentage of slow interactions (red).
    The performance of the upt-prod1 system is not satisfactory after the upgrade because significantly more than 1% of interactions were unhealthy (that is, they took more than one second), as shown in the following example:
    Distribution of healthy and slow interactions
    "Distribution of healthy and slow interactions"
    Distribution of healthy and slow interactions
    Data from the hour of the upgrade is missing, which might indicate that the system did not send data to PDC, for example, because the system was down or because agents that send the data did not function correctly. To ensure that the diagnostic information in PDC is reliable, the status of the system during this time might require further investigation.
  4. On the Average time of healthy and slow interactions chart, for each hour in the set time period, compare the average time that healthy interactions took (green bar) with the average time that slow interactions took (red bar).
    For the uPlusTelco application, during the hour when the upgrade took place and immediately afterwards, the average time for an interaction was unusually long for both healthy and slow interactions. This result is consistent with the findings in step 3, and provides another reason why your system's performance might require further investigation.

Conclusions

You identified the exact time of a major system upgrade and assessed the performance of your system after this operation. You detected a period of decreased performance that occurred immediately after the upgrade, but also found a possible problem with the upgrade process that might require further investigation and improvements to ensure that the system's performance is satisfactory.

What to do next

Identify the most urgent performance problems in your system. For more information, see Issue identification and research with Pega Predictive Diagnostic Cloud.

Suggest Edit

Have a question? Get answers now.

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