Use IDERA Uptime Cloud Monitor (UCM) to monitor your PostgreSQL database for availability and performance.
Uptime Cloud Monitor from IDERA offers a SAAS based out-of-the-box solution for monitoring PostgreSQL for performance and availability. If you are not familiar with the concept of custom metrics as used in Uptime Cloud Monitor, please go through Custom Metrics information once before continuing with this document.
There are three steps that you need to do to start monitoring a PostgreSQL service:
Figure 1: In your Uptime Cloud Monitor Account, navigate to Custom>Getting Started
Login to your Uptime Cloud Monitor account and navigate to Custom tab -> Getting Started. Click on PostgreSQL icon.
Figure 2: The PostgreSQL agent installation script
Click on icon to copy the installer script to your clipboard. Paste the command into the terminal window on the server where you want to install the agent. Script can be run on the server running PostgreSQL, or it can be a different server, but this server will need to be continually running in order to monitor PostgreSQL.
As soon as the script is run on a terminal with root access, it starts downloading the required PostgreSQL monitoring agent on your server. You will need to configure the following items in the agent installation process. Item specified in square brackets ( [ ] ) are the default.
Figure 3: Executing the PostgreSQL agent installation script with user as copperegg, Group as copperegg and monitoring frequency as 60 seconds
Figure 4: Executing the PostgreSQL agent installation script with group name as “PostgreSQL”, group label as “PostgreSQL metrics” and Dashboard as “PostgreSQL”
3. Group label, group name and dashboard name for custom metrics [PostgreSQL][PostgreSQL Metrics][PostgreSQL]
Figure 5: Executing the PostgreSQL agent installation script with unique id , server URL, port, ssl mode, database name, username and password. Only one PostgreSQL database is added for monitoring.
4. Unique name for this db server. [<user>-PostgreSQL]
5. Server details : URL and Port for service. [localhost]
6. Database Name : [postgres]
7. Username and Password to login to database.
8. After configuring one node, you’ll get an option to add more PostgreSQL databases and servers.
Figure 6: Executing the PostgreSQL agent installation script with an upstart init file and the default value for log file name. The installation completes successfully!
9. Configure log file name and upstart job name (defaults present) [/usr/local/copperegg/log/PostgreSQL_metrics.log][/etc/init/revealmetrics_PostgreSQL.conf]
Navigate to Dashboard and you will see a new PostgreSQL Dashboards have been added automatically by the installer.
Figure 7: A new Dashboard for PostgreSQL and PostgreSQL has been added
As the installed script executes, you will notice data samples appearing on the widgets for this Dashboard.
Figure 8: Widget inside PostgreSQL Dashboard displaying count of commits.
Figure 9: Widget inside PostgreSQL Dashboard displaying count of Rollbacks.
Figure 10: Widget inside PostgreSQL Dashboard displaying count of Rows Fetched.
Uptime Cloud Monitor currently monitors 42 metrics which cover most of the important metrics for PostgreSQL from a performance and stability perspective. You can see these 42 metrics by navigating to the Custom Tab > Custom Objects and selecting Details on the Custom Metrics Group Label [PostgreSQL Metrics] that was given as installation input. For some of these metrics, alerts have been automatically created (see section 3 below). To create new alerts see section: Configuring your own Alerts for the PostgreSQL Database.
The metrics are:
As soon as your PostgreSQL Database Monitoring Dashboard comes up, you will notice that some alert configurations have been automatically created by our Installation Script (under Alerts > Configure Alerts). These pre-configured alerts for PostgreSQL Database include:
The number of deadlocks detected in this database
Alert will be triggered for each deadlock situation.
The disk space used by this database
Percent Used Connections
The number of connections to this database as a fraction of the maximum number of allowed connections
Alert will be triggered when used connections reach to 80%.
If the alerting condition is met for these pre-configured alerts, some alert notifications may also be triggered.
Figure 11: A new alert being added that will be triggered when Connections metric exceeds a threshold of 2000 within a time period of 1 min
Alerts can also be configured against any of these 42 monitored metrics for PostgreSQL.
You can configure new alerts that will be triggered when performance issues with PostgreSQL arise. You can also configure the notification mechanisms for a triggered alert.
Uptime Cloud Monitor supports notifying different sets of users with differing notification mechanisms for each alert type.
Notification mechanisms include:
Webhooks are also exposed for clients to configure custom notification mechanisms. More about setting up website probe alerts can be found here.
Sign up for a 14 day FREE TRIAL of Uptime Cloud Monitor (no Credit Card required).
You can find more information about Uptime Cloud Monitor pricing options here.
We charge only $0.08 per month per metric!
Sign up today!
Jeff please email me your email address so we can assist you with your issue.
Email me at email@example.com
/usr/local/share/gems/gems/pg-0.15.1/lib/pg.rb:4:in `require': cannot load such file -- pg_ext (LoadError) from /usr/local/share/gems/gems/pg-0.15.1/lib/pg.rb:4:in `<top (required)>' from /usr/local/copperegg/ucm-metrics/postgresql/postgresql.rb:20:in `require' from /usr/local/copperegg/ucm-metrics/postgresql/postgresql.rb:20:in `<main>'
Also noted that yum installed the postgresql-9.2 devel even though the 9.5 and 9.6 versions are already installed on the server.
I did add the rubygem-pg from yum but when I try to locate pg_ext all I find are the versions previously installed as a part of docker.
Getting the following error when trying to start the revealmetrics_postgresql: