Skip to content

Releases: postgrespro/mamonsu

3.5.9

19 Aug 15:18
3.5.9
fd75eb0
Compare
Choose a tag to compare

Changelog

  • run on systems with latest setuptools installed (>67.7.2)
  • drop using dotted user:group specification in RPM pre-install stage

3.5.8

18 Apr 19:35
3.5.8
31a5981
Compare
Choose a tag to compare

Changelog

  • prepare for python 3.12: remove deprecated distutils imports

3.5.7

05 Apr 13:10
3.5.7
0656479
Compare
Choose a tag to compare

Changelog

  • added support for Zabbix 6.4 API: handle deprecated parameters for auth request
  • removed caching of pgsql.connections[max_connections] metric
  • update default logrotate rules

3.5.6

11 Jan 10:22
3.5.6
41144d1
Compare
Choose a tag to compare

Changelog

  • changed pg_locks plugin metrics names. Warning: custom user-defined triggers and processing functions may be broken if they use item.name parameter.

3.5.5

16 Jun 07:13
3.5.5
dd372df
Compare
Choose a tag to compare

Changelog

  • fixed types mismatch for pgpro_stats and pg_wait_sampling

3.5.4

17 May 10:53
3.5.4
c402a4f
Compare
Choose a tag to compare

Changelog

  • fixed privileges for mamonsu role created by bootstrap

3.5.3

16 Mar 10:47
f4cc989
Compare
Choose a tag to compare

Changelog

  • removed the owner check for the mamonsu agent.conf file (previously this was not flexible and only required the user "mamonsu")
  • removed metrics that conflict with the native Zabbix agent metrics (only in agent mode, in regular mode it works as usual)
  • added pg_stat_wal queries for native Zabbix agent
  • fixed native Zabbix agent queries

3.5.2

09 Sep 11:42
Compare
Choose a tag to compare

Changelog

  • fixed Statements plugin list of metrics creation
  • fixed Zabbix API requests to fit new Dashboard Template section rules
  • fixed Replication plugin metrics - null values are now taken into account
  • added new autovacuum utilization metrics: instant and average per 5, 15 and 30 minutes
  • moved plugin custom parameters to Zabbix Macros

Zabbix Macros

Now you can set up mamonsu plugins dynamically using Zabbix Macros. List of available macros:

  • {$ARCHIVE_QUEUE_FILES}
  • {$CACHE_HIT_RATIO_PERCENT}
  • {$CONNECTIONS_PERCENT}
  • {$CRITICAL_LAG_SECONDS}
  • {$MAMONSU_MAX_MEMORY_USAGE}
  • {$MAX_CHECKPOINT_BY_WAL_IN_HOUR}
  • {$MAX_TRANSACTION_TIME}
  • {$MAX_PREPARED_TRANSACTION_TIME}
  • {$MAX_XID_AGE}
  • {$PG_UPTIME}
  • {$SYSTEM_UPTIME}
  • {$VFS_INODE_PERCENT_FREE}
  • {$VFS_PERCENT_FREE}

autovacuum utilization

Added new metrics: instant autovacuum utilization and average autovacuum utilization per 5, 15 and 30 minutes

Name PostgreSQL Autovacuum: Utilization per [MAMONSU_INTERVAL] seconds
Key pgsql.autovacumm.utilization[]
Type Numeric (float)
Units
Delta As Is
Supported Version 9.5+
Name PostgreSQL Autovacuum: Utilization per 5 minutes
Key pgsql.autovacumm.utilization.avg5[]
Type Numeric (float)
Units
Delta As Is
Supported Version 9.5+
Name PostgreSQL Autovacuum: Utilization per 15 minutes
Key pgsql.autovacumm.utilization.avg15[]
Type Numeric (float)
Units
Delta As Is
Supported Version 9.5+
Name PostgreSQL Autovacuum: Utilization per 30 minutes
Key pgsql.autovacumm.utilization.avg30[]
Type Numeric (float)
Units
Delta As Is
Supported Version 9.5+

3.5.1

29 Jul 06:57
Compare
Choose a tag to compare

Changelog

3.5.0

13 Jul 13:04
Compare
Choose a tag to compare

Changelog

  • divided Instance Rate graph into two graphs - Blocks Rate, Transactions Rate
  • divided XLOG plugin into two plugins - WAL, Replication
  • changed pg_wait_sampling plugin name to Wait Sampling
  • changed pg_stat_statements plugin name to Statements
  • changed default agent.conf file permissions: now it read/write only for mamonsu user
  • added new Replication plugin metrics: Send Lag, Receive Lag
  • added pgpro_stats support to PostgresPro cluster (automatic switch from pg_stat_statements and pg_wait_sampling)
  • added new bootstrap features: now the '-x' option also configures pg_stat_statements, pg_wait_sampling and pgpro_stats extensions
  • added custom schema check for pg_stat_statements, pg_wait_sampling and pgpro_stats extensions
  • added new lock types to the Wait Sampling plugin to fit PostgreSQL 10+: Extension Locks, Client Locks, Other Locks (e.g. IPC Timeout IO), Autovacuum Locks, Logical Replication Locks
  • added new System Free/Used Memory graph
  • added new active locking queries feature to the report tool
  • replaced System Memory Overview graph with System Free/Used Memory in dashboards
  • fixed Statements plugin items generation for native zabbix agent
  • fixed Rollbacks item delta type
  • fixed WAL metrics delta types
  • fixed PostgreSQL Uptime trigger
  • improved Replication metrics evaluation algorithm
  • unified Zabbix objects names
  • unified config file sections and parameters names
  • set new color scheme

pgpro_stats support

By default mamonsu uses pg_stat_statements and pg_wait_samplings in plugins Statements and Wait Sampling. These extensions need to be installed additionally via shared_preload_libraries. But if mamonsu detects PostgresPro instead of vanilla PostgreSQL, it switched automatically to pgpro_stats for both plugins. This is more convenient because pgpro_stats is going by default with PostgresPro.

agent.conf permissions

Now by default mamonsu sets for agent.conf the following permissions:

permissions  user    group
-rw-------   mamonsu mamonsu  jun 16 12:21 agent.conf

new report feature

With other PostgreSQL stats, report now evaluates information about current locks:

$ mamonsu report --run-system --run-postgres -U mamonsu
<...>
# CURRENT LOCKS ##################################
blocked_pid     database          blocked_user  blocking_pid    blocking_user   blocked_statement                                     duration
49934           mamonsu_test_db   postgres      91741           postgres        update mamonsu_logs set value = 0 where value = 3;    0:00:35.199513

NOTE: objects new names

Pay attention to new Zabbix template object names. All mamonsu objects have been unified in template representation, so you should update the template carefully. For example, PostgreSQL: number of user total connections switched to PostgreSQL Connections: Number of Total User Connections. All changes are shown in documentation.