Knowledge Base

Monitoring PostgreSQL with Monitoring Studio using a Configuration Template

KB1185 - Oct 25, 2016 - Last reviewed on Apr 30, 2020

Type: Configuration Template

Description: This article explains how to monitor a PostgreSQL database with Monitoring Studio v9.2 and higher.

Additional Keywords: Configuration Template, PostgreSQL

Related Topics

Download File
Important Note: This pre-built configuration template does not cover all the monitoring aspects of a PostgreSQL database running on Linux. It is provided as an example and can be used as a working base for advanced monitoring. No support will be provided for this pre-built configuration. Should you need further assistance to customize this template, please contact our Professional Services team.

Introduction

This article explains how to import the pre-built configuration developed by Sentry Software to monitor a PostgreSQL database running on Linux. This pre-built configuration is also available for Windows based on the monitors specific to Windows but it will not be described in this article.

Here is the list of collected metrics for the Linux configuration:

inline
  • AutoVacuum Launcher Process
    • CPU Usage
    • Memory Usage
  • Bgwriter Overwrites
  • Cache Usage Rate
  • Checkpoint
    • Minutes between Checkpoints
    • Total Checkpoints
  • Connections waiting for a lock
  • Pg_log Folder
  • Logger Process
    • CPU Usage
    • Memory Usage
  • Maximum transaction age
  • PostgreSQL Log file
  • PostgreSQL Status
  • Stats Collector Process
    • CPU Usage
    • Memory Usage
  • Total Locked Elements
  • Transactions Per Second
  • User Connections
  • Wal Writer Process
    • CPU Usage
    • Memory Usage
  • Write Activity
    • Inserts
    • Updates
    • Deletes
  • Writer Process
    • CPU Usage
    • Memory Usage

Importing the Pre-Built Configuration

Pre-requisites

Before using the pre-built configuration, make sure:

  • You have access:
    • to the server where the PostgreSQL is installed
    • to query the pg_catalog system tables
    • to the log files
  • PATROL Agent 9.6 or later is installed and properly configured
  • Monitoring Studio KM 9.2 or later is installed and loaded on the PATROL agent

Procedure

  1. Download the PostgreSQL-Linux-for-MSv9.x-<version>.cfg file and copy it on the server where the PATROL Agent and the Monitoring Studio KM are installed.
  2. Right-click the main Monitoring Studio icon > KM Commands > Configuration > Import Configuration
    Importing the PostgreSQL database pre-built configuration
  3. Enter the path to the folder containing the PostgreSQL-Linux-for-MSv9.x-<version>.cfg file and click Next.
    Selecting the Monitoring Studio template to import
  4. Select the PostgreSQL-Linux-for-MSv9.x-<version>.cfg configuration file and click Next.
    Setting the STANDBY_HOST and PG_LOG Group Constants
  5. Provide the Standby host name if available, the path to the pg_log directory where the PostgreSQL logs are stored and click Next.
    Setting the host where the PostgreSQL database is running
  6. Provide the name of the host where the PostgreSQL database is running and click Next.
    Setting the credentials to connect to the host where the PostgreSQL database is running
  7. Provide the user credentials. Click the “Currently Used by” button to know which monitoring functions require valid credentials and click Next.
    Verifying the import summary of the PostgreSQL pre-built configuration
  8. Verify the import summary and click Next.
    Success import of the PostgreSQL pre-built configuration
  9. Click Finish.

Learn More

To learn more about the monitor types used in this configuration template, please refer to the following sections of the user documentation:

Please refer to Professional Services page to learn more about the consulting services available.