Skip to main content

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

Setting up agent notifications

Updated on August 25, 2021

You can enable notification on agent failure to receive emails on each occurrence of the PEGA0010 alert that is triggered when an exception occurs during agent processing.

The notification email contains information about the name of the agent that failed, the node ID on which the agent failed, and other information about the failure. Receiving notifications on agent failure allows you to immediately take the correct action to restart or fix the agent.

Note: The notification functionality does not eliminate the PEGA0010 alert.

For more information about the alert, see the PEGA0010 alert: Agent processing disabled article on Pega Community.

To access the Agent Management landing page and view the list of agents and the configuration of email notifications on agent failure, you must have the PegaRULES:SysOpsObserver role. To perform all available actions on agents, for example, to start or stop an agent, and configure email notifications on agent failure, you must also have the PegaRULES:SysOpsAdministrator role.

  1. In the navigation pane of Admin Studio, click ResourcesAgents.
  2. Click Notification settings.
  3. To enable notifications, click Enable to send mails on agent failure.
  4. In the Send to field, specify a list of email addresses to which to send notifications. To specify multiple email addresses, separate them with a semicolon and do not include spaces, for example, [email protected];[email protected].
  5. In the Email account field, specify an email account that is an instance of the Data-EmailAccount class.
  6. 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us