You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am monitoring a PSQL 11.5 Server with partitioning configured pg_partman, and I am seeing some problems with the stats collector since yesterday.
I guess, this has to do with the fact, that your Zabbix templates get every table (the partitioned tables too) over the Discovery Rule Discover PostgreSQL Databases.
See,
2019-11-23 17:01:13.648 CET [20651] LOG: using stale statistics instead of current ones because stats collector is not responding
2019-11-23 17:01:13.648 CET [20651] STATEMENT: SELECT n_tup_ins FROM pg_stat_all_tables WHERE relname = $1
2019-11-23 17:01:23.491 CET [2944] LOG: using stale statistics instead of current ones because stats collector is not responding
2019-11-23 17:01:23.764 CET [20688] LOG: using stale statistics instead of current ones because stats collector is not responding
2019-11-23 17:01:23.764 CET [20688] STATEMENT: SELECT n_tup_upd FROM pg_stat_all_tables WHERE relname = $1
Is there any way of filtering all the partitioned tables from the Discovery Rule results?
The text was updated successfully, but these errors were encountered:
Hi @cavaliercoder,
I am monitoring a PSQL 11.5 Server with partitioning configured pg_partman, and I am seeing some problems with the stats collector since yesterday.
I guess, this has to do with the fact, that your Zabbix templates get every table (the partitioned tables too) over the Discovery Rule Discover PostgreSQL Databases.
See,
Is there any way of filtering all the partitioned tables from the Discovery Rule results?
The text was updated successfully, but these errors were encountered: