Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Rashi Chhabra (Rashi_Chhabra)
Chhabra

Chhabra
IN
Rashi_Chhabra Member since 2017 22 posts
Chhabra
Posted: Jan 10, 2019
Last activity: Jan 16, 2019
Posted: 10 Jan 2019 3:41 EST
Last activity: 16 Jan 2019 3:27 EST
Closed
Solved

Service-14 Alert from AES on Pega Platform

Hi Team,

We are trying to understand certain system generated alerts that we receive from the Pega Platform. Few of them are "Service-14", "Connect-45/Connect-82", alerts (I will attach the screenshot to the post). Please help us understand the relevance of such alerts and the impact and solution.

Thanks.

Regards,

Rashi.

***Edited by Moderator Marissa to update platform capability tags****

To see attachments, please log in.
Pega Autonomic Event Services
Dev/Designer Studio

Posted: 6 years ago
Posted: 10 Jan 2019 5:02 EST
Arvind Malav (malaa) Technical Manager
Pegasystems Inc.
IN

Hi Rashi,

Thank you for contacting Pega Support forum.

These alerts are alarming that certain components are performing poor, thus you need to review them, from screenshots you attached, below is specifics:

Service-14 tells that Email service sparesemail processing emails is slow
Connect-64 says that Rest-connector QueueDetails is performing poor.

 

 

To see attachments, please log in.
Posted: 6 years ago
Posted: 10 Jan 2019 6:43 EST
Rashi Chhabra (Rashi_Chhabra)
Chhabra

Chhabra
IN

Thanks a lot Arvind. Helps a lot. 

Could you also please give me some information on the following alerts:

BrowsInt-1032

Exception-14103 

Exception-1425

Connect-45 / Connect-82

Exception-1514

Exception-1589

Exception-1550

DBCommit-24

Exception-1640

 

Thanks again, this information has been really helpful.

To see attachments, please log in.
Posted: 5 years ago
Posted: 16 Jan 2019 3:27 EST
Andy Werden (WERDA)
PEGA
Senior Fellow Technology Architect
Pegasystems Inc.
US

AES creates a single case for all alerts or exceptions that are considered to have same root cause. Based on the nature of the alert or exception, an appropriate case type is created. AES uses a verbose / human readable prefix ... so DBCommit-24 is the 24th case AES has created having to do with performance in 'committing' work to the Database.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice