1 Title: mk_postgres, postgres_instances, postgres_bloat, postgres_conn_time, postgres_connections, postgres_locks, postgres_query_duration, postgres_sessions, postgres_stat_database, postgres_stats, postgres_version: plugin and checks are now instance aware
9 Now the {{mk_postgres}} agent plugin is instance aware. Moreover the new check
10 {{postgres_instances}} reports if instance is running or not. All other checks
11 go PEND if instance is not running.
13 The following lines describe the agent plugin configuration.
14 If you have default postgres installation it's not necessary to give a
15 configuration file, ie. if
16 - user is 'postgres' or 'pgsql' and
17 - PGDATABASE is 'postgres'
19 Configuration of the plugin is needed if you want to monitor multiple instances.
20 Then you have to determine
22 - path to instance env file
23 - user name for this instance
24 - path to .pgpass file where password is stored
26 This can be done via postgres.cfg file with following syntax:
28 INSTANCE=/home/postgres/INSTANCE1.env:USER_NAME:/PATH/TO/.pgpass
29 INSTANCE=/home/postgres/INSTANCE2.env:USER_NAME:/PATH/TO/.pgpass
31 It's incompatible because now the following checks need an item. Thus
32 the service descriptions will change.
37 Another reason is that {{postgres_sessions}} needs a new rule set
38 {{PostgreSQL Sessions}} which can handle items. The older one is
39 marked as {{deprecated}}. It is located below
40 {{WATO > Host & Service Parameters > Deprecated Rulesets}}.
41 You have to transfer these old rulesets to new ones which can be found below
42 {{WATO > Host & Service Parameters > Parameters for discovered services > PostgreSQL Sessions}}.