Обсуждение: check_postgres_bloat
Thanks everyone for the responses.
It seems like the problem is actually that the check_postgres_bloat does not check for index bloat, just table bloat, even though it says it checks for both.
Below is my proof. Notice how this first check finds the indexes with idx in their name, but the second one doesn't.
check_postgres.pl version 2.14.3
postgresq version is 8.3.9
The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail. Get busy.
It seems like the problem is actually that the check_postgres_bloat does not check for index bloat, just table bloat, even though it says it checks for both.
Below is my proof. Notice how this first check finds the indexes with idx in their name, but the second one doesn't.
check_postgres.pl version 2.14.3
postgresq version is 8.3.9
/usr/local/nagios/libexec # ./check_postgres_index_size --dbservice=thing -w 50 --include=~idx -c 100
POSTGRES_INDEX_SIZE CRITICAL: service=thing largest index is "thing1_idx": 288 kB | time=1.00
/usr/local/nagios/libexec # ./check_postgres_bloat --dbservice=thing -w 50 --include=~idx -c 100 POSTGRES_BLOAT UNKNOWN: service=thing No matching relations found due to exclusion/inclusion options | time=0.18
The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail. Get busy.