Supported Metrics
The following tabs represent the Native Type of PostgreSQL Cluster
PostgreSql Node
| Metric Name | Display Name | Metric Category | Unit | Application Version | Description |
|---|---|---|---|---|---|
| postgresql_node_statiotables_Idx_Blks_Hit | Postgresql Statio Tables Idx Blks Hit | Performance | count | 1.0.0 | Number of buffer hits in all indexes on this table |
| postgresql_node_database_Temp_Bytes | Postgresql Database Temporary Bytes | Usage | 1.0.0 | Total amount of data written to temporary files by queries in this database. All temporary files are counted, regardless of why the temporary file was created, and regardless of the log_temp_files setting. | |
| postgresql_node_bgwriter_Checkpoints_Reqest | Postgresql Bgwriter Checkpoints Request | Performance | 1.0.0 | Number of requested checkpoints that have been performed | |
| postgresql_node_database_Size | Postgresql Database Size | Capacity | Giga Bytes (GB) | 1.0.0 | The size of the database |
| postgresql_node_stat_tables_Seq_Tup_Read | Postgresql Tables Row Sequential Scan | Performance | 1.0.0 | Number of live rows fetched by sequential scans | |
| postgresql_node_statiotables_Toast_Blks_Hit | Postgresql Statio Tables Toast Blks Hit | Performance | 1.0.0 | Number of buffer hits in this table's TOAST table (if any) | |
| postgresql_node_max_Connections | Postgresql Max Connections | Usage | 1.0.0 | The maximum number of client connections allowed to this database.shown as connection | |
| postgresql_node_statio_tables_Buffer_Hits | Postgresql Statio Tables Buffer Hits | Performance | 1.0.0 | Number of buffer hits in this table | |
| postgresql_node_database_Rows_Deleted | Postgresql Database Rows Deleted | Usage | 1.0.0 | Number of rows deleted by queries in this database | |
| postgresql_node_user_Table_Count | User Table Count | Usage | 1.0.0 | It monitors the number of user tables in current database. | |
| postgresql_node_Activity_Count | Postgresql Activity Count | Usage | 1.0.0 | This will tell you how close you are to hitting your max_connections limit, and show up any clients which are leaking database connections. | |
| postgresql_node_database_Conflict_Deadlocks | Postgresql Database Conflict Deadlocks | Performance | count | 1.0.0 | Number of conflicts in this database that have been canceled due to deadlocks |
| postgresql_node_Locks_Granted | Postgresql Locks Granted | Usage | 1.0.0 | True if lock is held, false if lock is awaite | |
| postgresql_node_statio_tables_Index_Buffer_Hit | Postgresql Statio Tables Index Buffer Hits | Performance | Hits per sec (hps) | 1.0.0 | Number of buffer hits in all indexes on this table |
| postgresql_node_database_Blks_Hit | Postgresql Database Blocks Hits | Performance | 1.0.0 | Number of times disk blocks were found already in the buffer cache, so that a read was not necessary (this only includes hits in the PostgreSQL buffer cache, not the operating system's file system cache) | |
| postgresql_node_database_Rows_Updated | Postgresql Database Rows Updated | Usage | 1.0.0 | Number of rows updated by queries in this database | |
| postgresql_node_database_Rows_Inserted | Postgresql Database Rows Inserted | Usage | 1.0.0 | Number of rows inserted by queries in this database | |
| postgresql_node_Class_Relpages | Postgresql Class Relpages | count | 1.0.0 | This query is used to display the tables and their respective indexes in descending order of relpages. | |
| postgresql_node_Locks_Count | Postgresql Locks Count | Capacity | 1.0.0 | The number of connections blocked waiting for a lock can be an indicator of a slow transaction with an exclusive lock. | |
| postgresql_node_Statioindexes_Bufferhits | Postgresql Statio Indexes Buffer Hits | Performance | 1.0.0 | Number of buffer hits in this index | |
| postgresql_node_bgwriter_Buffers_Backend | Postgresql Bgwriter Buffers Backend | 1.0.0 | Number of buffers written directly by a backend | ||
| postgresql_node_database_Deadlocks | Postgresql Database Deadlocks | Performance | count | 1.0.0 | Number of deadlocks detected in this database |
| postgresql_node_statio_tables_Index_Block_Read | Postgresql Statio Tables Index Block Read | Performance | 1.0.0 | Number of disk blocks read from all indexes on this table | |
| postgresql_node_database_Connections | Postgresql Database Connections | Usage | 1.0.0 | The number of active connections to postgres database. | |
| postgresql_node_settings_Connection | Postgresql Settings Connections | 1.0.0 | The number of connections to this database as a fraction of the maximum number of allowed connections. | ||
| postgresql_node_bgwriter_Buffers_Clean | Postgresql Bgwriter Buffers Clean | 1.0.0 | Number of buffers written by the background writer | ||
| postgresql_node_bgwriter_Checkpoints_Timed | Postgresql Bgwriter Checkpoints Timed | count | 1.0.0 | Number of scheduled checkpoints that have been performed | |
| postgresql_node_bgwriter_Buffers_Checkpoint | Postgresql Bgwriter Buffers Checkpoint | 1.0.0 | Number of buffers written during checkpoints | ||
| postgresql_node_database_Rows_Returned | Postgresql Database Rows Returned | 1.0.0 | Number of rows returned by queries in this database | ||
| postgresql_node_database_Rows_Fetched | Postgresql Database Rows Fetched | 1.0.0 | Number of rows fetched by queries in this database | ||
| postgresql_node_user_tables_Rows_Count | Postgresql User Tables Rows Count | count | 1.0.0 | number of rows scans | |
| postgresql_node_usertable_Rowsdead | Postgresql User Table Rows Dead | 1.0.0 | This query gives the number of dead rows (tuples) in the table. | ||
| postgresql_node_database_Transaction_Rollback | Postgresql Database Transactions RolledBack | 1.0.0 | Number of transactions in this database that have been rolled back | ||
| postgresql_node_database_IsInstanceStandby | Postgres Database Is Instance Standby | Availability | 1.0.0 | Check if Postgres database instance is standby or not 0 - Not Standby , 1 - Standby | |
| postgresql_node_hot_Standby_Feature_Status | PostgreSQL Hot Standby Feature Status | Availability | 1.0.0 | Show the Hot Standby mode is either on or off. 1 means "on" & 0 means "off" | |
| postgresql_node_activity_Long_Transactions | PostgreSQL Activity Long Transactions | Performance | Hours | 1.0.0 | Monitors PostgreSQL activity long transactions in hours |
| postgresql_node_database_Walsegment_Count | Postgres Database Walsegment Count | count | 1.0.0 | Postgres WAL segment count - compared to defined thresholds | |
| postgresql_node_database_Backend_Connections_Percentage | Postgres Database Backend Connections Percentage | Usage | % | 1.0.0 | Postgres backend connections - percent relative to max_connections database setting |
| postgresql_node_database_Transaction_Wraparound | Postgres Database Transaction Wraparound | Performance | 1.0.0 | Postgres value of txn_wraparound - compared to defined thresholds | |
| postgresql_node_database_Total_Backend_Connections_Percentage | Postgres Total Backend Connections Percentage | Usage | % | 1.0.0 | Postgres total backend connections - percent relative to max_connections database setting |
| postgresql_node_database_Wal_Sender_State | Postgres Database Wal Sender State | Availability | 1.0.0 | Postgres database current Wal Sender state – Possible States : startup - 1 catchup - 2 streaming - 3 backup - 4 stopping - 5 | |
| postgresql_node_database_Replication_Sendlag_Bytes | Postgres Database Replication Sending Lag In Bytes | Performance | Bytes | 1.0.0 | Postgres database replication – replication sending lag - bytes |
| postgresql_node_database_Replication_Lag_Sec | Postgres Database Replication Lag In Seconds | Performance | Sec | 1.0.0 | Postgres database replication – replication lag - seconds |
| postgresql_node_database_Replication_Replaylag_Bytes | Postgres Database Replication Replay Lag In Bytes | Performance | Bytes | 1.0.0 | Postgres database replication – replication replay lag - bytes |
| postgresql_node_database_Replication_Totallag_Bytes | Postgres Database Replication Total Lag In Bytes | Performance | Bytes | 1.0.0 | Postgres database replication – replication total lag - bytes |
| postgresql_node_database_Replication_Receivelag_Bytes | Postgres Database Replication Receiving Lag In Bytes | Performance | Bytes | 1.0.0 | Postgres database replication – replication receiving lag - bytes |
Default Monitoring Configurations
Postgresql application has default Global Device Management Policies, Global Templates, Global Monitors and Global Metrics in OpsRamp. You can customize these default monitoring configurations as per your business requirement by cloning respective Global Templates and Global Device Management Policies. It is recommended to clone them before installing the application to avoid noise alerts and data.
Default Global Device Management Policies
You can find the Device Management Policy for each Native Type at Setup > Resources > Device Management Policies. Search with suggested names in global scope:
{appName nativeType - version}Ex: postgresql-cluster PostgreSql Node - 1 (i.e, appName = postgresql-cluster, nativeType = PostgreSql Node, version = 1)
Default Global Templates
You can find the Global Templates for each Native Type at Setup > Monitoring > Templates. Search with suggested names in global scope. Each template adheres to the following naming convention:
{appName nativeType 'Template' - version}Ex: postgresql-cluster PostgreSql Node Template - 1 (i.e, appName = postgresql-cluster, nativeType = PostgreSql Node, version = 1)
Default Global Monitors
You can find the Global Monitors for each Native Type at Setup > Monitoring > Monitors. Search with suggested names in global scope. Each Monitors adheres to the following naming convention:
{monitorKey appName nativeType - version}Ex: PostgreSql Node Monitor postgresql-cluster PostgreSql Node 1 (i.e, monitorKey = PostgreSql Node Monitor, appName = postgresql-cluster, nativeType = PostgreSql Node, version = 1)