3.1.0

Mamonsu 3.1.0:

• fixed unknown options check in mamonsu tools;
• fixed item units with Speed Per Second delta;
• fixed #166 (1): Walreceiver Lag items name generation;
• fixed #166 (2): item Total Replication Lag delta evaluation;
• fixed #107: slave replication lag evaluation;
• #172: set 'dbname' bootstrap parameter required, added default value read from config file;
• fixed extension functions calling without special mamonsu user and schema;
• refactoring;

---

bootstrap update
Added new -c/--config option to bootstrap tool. Usage:

mamonsu bootstrap [-M mamonsu_user] [-x | --create-extensions] [-c | --config] [connection_options]

This option is needed for automatic dbname parameter detection. Now if you have not set the dbname explicitly, parameter will be set as database defined in [postgres] section in mamonsu config file.

3.0.2

Mamonsu 3.0.2:

• fixed #163: Archive Command bootstrap functions;
• fixed #168: Archive Command plugin compability with PostgreSQL 9.6 and lower;
• added GitHub Actions CI/CD scripts - now you can build and test Mamonsu by yourself without special instruments;
• fixed PostgreSQL 14 metrics delta;

3.0.1

Mamonsu 3.0.1:

• fixed 'PostgreSQL: Archive Command archive status' graph y axis;
• fixed bootstrap -x option: now it checks installed extensions;
• fixed 'pgsql.count_files_to_archive' and 'pgsql.size_files_to_archive' items: now their evaluation depending on type of server (master or replica);

3.0.0

mamonsu 3.0.0

NOTE: Mamonsu 3.0.0 is incompatible with previous versions.

Compatibility Considerations

If you want to upgrade mamonsu to a version that is not compatible with the previous one, what you must do to continue using the application depends on whether you need to retain the metrics data collected.

If you need to retain the collected data, do the following:

1. Install the new version of mamonsu.
2. Generate a new template for the Zabbix server.
3. If you performed a bootstrap using the previous version of mamonsu, run the bootstrap command again.
4. Upload the new template to the Zabbix server.
5. Rename the host for which you want to retain the collected data and leave the old template linked to that host.
6. Create a new host for the same system and link the new template to it.
7. Restart mamonsu. It will collect data for the new host. The old host will no longer be used, but the data collected will be available.

If you do not need to retain the collected data, do the following:

1. Install the new version of mamonsu.
2. Generate a new template for the Zabbix server.
3. If you performed a bootstrap using the previous version of mamonsu, run the bootstrap command again.
4. Upload the new template to the Zabbix server.
5. In the settings of the Zabbix host, link the new template to the host instead of the old one.
6. Restart mamonsu. It will start collecting data. All the data collected earlier will be lost.

Changelog

• Template name changed from PostgresPro-[PLATFORM] to Mamonsu PostgreSQL [PLATFORM];
• Changed PostgreSQL uptime metric type to unixtime (date and time of service start);
• Changed Cache Hit Ratio metric calculation: now it evaluates via Zabbix calculated item;
• Changed Archive Command plugin metrics: now they evaluate without accessing the FS;
• Metric name pgsql.transactions [total] changed to pgsql.transactions [committed];
• Added new PG14 metrics based on pg_stat_wal and pg_stat_statements_info:
  • pgsql.wal.records.count;
  • pgsql.wal.fpi.count;
  • pgsql.wal.buffers_full;
  • pgsql.wal.write_time;
  • pgsql.wal.sync_time;
  • pgsql.wal.sync_duty;
  • pgsql.stat_info[dealloc];
  • pgsql.stat_info[stats_reset];
• Removed graphs representing only one metric (since this duplicates the functionality of Zabbix simple graphs);
• Added new graphs:
  • PostgreSQL bgwriter buffers;
  • PostgreSQL bgwriter write/sync;
  • PostgreSQL checkpoint count;
  • PostgreSQL checkpoint write/sync;
• Added screens: Overview, PostgreSQL Instance, PostgreSQL WAL, PostgreSQL Locks, PostgreSQL Transactions, System;
• Fixed support for different Zabbix versions (3.0-5.4):
• Added new bootstrap flag x/--create-extensions to optionally create extensions;
• Added default mamonsu user creation to bootstrap tool;
• Added mamonsu own schema creation to bootrtap tool;
• Changed mamonsu plugin structure: added new parameter for Zabbix screens;
• Fixed #159;

2.7.1

• rm pgsql.count_all_pids metric

2.7.0

• update bootstrap command
• fix ArchiveCommand plugin (add handling of archive_mode = 'always' )
• add metric and trigger to count non-active replication slots
• add a metric to count children of PostgreSQL parent PID
• add re-transmission of metrics one by one to track down metrics which Zabbix server does not accept.
• add command to get the version of the Zabbix server to which mamonsu is connected.

2.6.2

• update xlog plugin
• add support for PostgreSQL 13
• add plugin memory_leak_diagnostic
• add plugin relations_size
• update packaging for Windows

2.5.1

• update pg8000 driver
• redirect log messages for mamonsu agent to log fle
• drop python2 support
• add old templates for mamonsu and zabbix-agent
• add new plugin: pg_probackup
• add new plugin: prepared_transactions

2.4.5

• added checksum_failures metric in Instance plugin for Postgresql 12
• changed PG version support in commands:
  mamonsu export zabbix-parameters
  mamonsu export zabbix-template
  mamonsu export template
  mamonsu export zabbix-template
• update help message for 'mamonsu export'

2.4.4

• change command name for uploading metrics from the file (written by mamonsu /var/log/mamonsu/localhost.log, [metric_log] parameter in agent.conf file) to Zabbix Server
• update help message