cancel
Showing results for 
Search instead for 
Did you mean: 

PEM not generating any alerts

The Postgres Enterprise Manager (PEM) tool is designed to help with managing and monitoring multiple Postgres servers. It provides status information that can be useful for any administrator, and comes with an alerting system to let you know when a server may be down or encountering some issues. However, when PEM is first installed, even though alerting looks like it’s already pre-configured, including a starting set of alerts that have been included as a template, the alerts don’t actually trigger. For example:

 

2018-06-18 09_42_59-Microsoft Edge.png

 

 

I have my default alerts enabled, but even though I have a server down, there are no alerts.

 

The issue is most likely because the default installation of PEM does not activate alerts. If you install PEM using the yum repository files, it provides you with the standard agents.cfg file, usually located in /usr/edb/pem/agent/etc/agent.cfg. In it, the field alerts_threads is set by default to 0, which keeps it disabled. Here, I change the value and then restart the pemagent service on the PEM server (I am on Centos 7, hence the systemctl command instead of service)

[root@35f801c581e1 /]# vi /usr/edb/pem/agent/etc/agent.cfg
alert_threads=1
[root@35f801c581e1 /]# systemctl start pemagent

Once this change is made, refresh the browser screen and it is now alerting properly, notifying me of a number of issues:

 

 

 

2018-06-18 10_08_06-Postgres Enterprise Manager ‎- Microsoft Edge.png

Version history
Revision #:
5 of 5
Last update:
‎09-05-2019 06:17 PM
Updated by:
 
Labels (3)
Contributors