Skip to main content


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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Configuring systems for monitoring with Pega Autonomic Event Services 7.3

Updated on October 17, 2017

After you install Pega® Autonomic Event Services 7.3, configure the Pega Platform systems that you want the application to monitor. In addition to configuring the systems to push messages, you can set email scorecard subscriptions and enable Pega Autonomic Event Services to pull information from the monitored systems.

For each Pega Platform system, complete the following tasks:

Ensuring that each system has a unique name

Pega Autonomic Event Services refers to monitored systems by their names, which are configured on Pega Platform. For example, to view the scorecard for a specific system, select a system name from the monitored nodes list.

  1. Click Designer Studio > System > Settings > System Name.
  2. Enter the new name in the New Name field, and click Submit.
  3. Restart all nodes in the system to apply the new name.

Enabling Pega Autonomic Event Services integration on monitored systems

So that Pega Autonomic Event Services can receive alerts and exceptions from a system, update the system's configuration with the correct URL.

  1. Click Designer Studio > System > Settings > Predictive Diagnostic Cloud.
  2. In the ENDPOINT SOAP URL field, enter the endpoint SOAP URL that corresponds to the Pega Autonomic Event Services server's SOAP URL. Use the following format:

    http://[server name]:[port number]/prweb/PRSOAPServlet

  3. Click Update Configuration.

Configuring email scorecard subscriptions

As a Pega Autonomic Event Services operator, you can review the weekly scorecard on the system’s main screen or request a weekly scorecard to be sent by email so that you and the recipients stay informed about a system's health. You can subscribe to a scorecard and select a system for which you want a report to be sent. For more information about the scorecard, see Pega Predictive Diagnostic Cloud scorecard overview.

Managing scorecard subscriptions

You can filter the list of existing scorecard subscriptions by system and by type of scorecard. For more information, see Scorecard options in Pega Predictive Diagnostic Cloud scorecard overview.

  1. Click Autonomic Event Services > Scorecards > Manage Subscriptions.
  2. From the System list, select the system for which you want to view subscriptions.
  3. From the Scorecard list, select the type of scorecard for which you want to view subscriptions.
    For example, if you want to see who is subscribed to receive daily updates of new action items for a system named MyCo-Prod, select this system from the System list, and select New Items Daily Scorecard from the Scorecard list.
  4. To remove a subscription row, click the Remove icon in the rightmost column.
The subscription is removed without further confirmation, and the only way to restore it is to add it again.

Adding scorecard subscriptions

You can configure any email address to receive selected scorecards for any monitored system. The list of scorecard recipients is independent of the operator records, and is stored under the PegaAES-Data-EmailRecipient class.

  1. Click Autonomic Event Services > Scorecards > Manage Subscriptions.
  2. Click New Subscription.
  3. From the System list, select the name of the system for which you want to add scorecard subscriptions.
  4. From the Scorecard list, select the type of scorecard for which you want to add subscriptions.
  5. If you selected the Weekly Scorecard or the New Items Daily Scorecard, select which days of the week you want the scorecards to be sent.
  6. Enter the email address, first name, and last name of the scorecard's recipient.
  7. To add more recipients, click the Add Item icon, and repeat step 6.
  8. To remove a recipient, select the recipient's row, and then click the Delete icon.
  9. Click Submit.

Optional: Enabling Pega Autonomic Event Services to send requests to monitored nodes

Pega Autonomic Event Services can send pull requests for additional information to monitored systems. Pull requests provide agent management, quiesce management, requestor management, listener management, rule information, run time information, and JVM information. If you enable this feature for monitored Pega Platform systems earlier than 7.2, Pega Autonomic Event Services correctly retrieves and displays the production level value of the monitored system. To enable this feature, perform the following steps:

  • Configuring URL endpoints of monitored nodes
  • Enabling information collection
When you enable this feature, ensure that you restart the monitored systems.

Configuring URL endpoints of monitored nodes

Ensure that the correct URL is set for each monitored node so that the application can communicate with the nodes.

  1. Log in to Pega Autonomic Event Services as aesdeveloper by using the password that you used when you installed the application.
  2. From the Application Explorer, search for the PegaAES-Data-Nodes class.
  3. Right-click the PegaAES-Data-Nodes class, and select View > Instances.
  4. On the list of monitored nodes, click a node that you want to edit.
  5. In the New Connection String field, enter the node's URL. Request the correct URL from the application server administrator.
  6. Click Save.
  7. For each monitored node, repeat steps 4 through 6.

Enabling information collection

By default, Pega Autonomic Event Services does not send pull requests for information. To change this behavior, modify the appropriate system settings.

  1. In the Pega Autonomic Event Services Manager Portal, go to the Administration panel.
  2. In the Management section, click System Settings.
  3. Select the system for which you want to change the settings from the Current System is list.
  4. Clear all the check boxes.
  5. Click Save.

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