This update is for all GroundWork customers. The notification manager (NoMa) does not natively implement long-term retention control for the logging of outgoing notifications. Over time, that can cause the noma database to grow quite large at a site that makes extensive use of NoMa notifications. It might also slow down the processing of such notifications.
This Technical Bulletin provides a NoMa retention-control script along with a companion configuration file (/usr/local/groundwork/config/noma_retention.conf), and installs a cron job to run the script on a daily basis. The default setting in the config file will retain NoMa notification-log data for 90 days, which should be sufficient for typical operational usage.
tar xf TB7.2.1-05-notification-logs.tgz
The install script will test that you are on a 7.2.1 system (which is required), that you have not already installed this patch, and that you want to go ahead.
The retention will be adjusted at 12:50 am daily. If there are a lot of old notification records when you install this patch, the first run will take a minute or two, and there will be some inefficiency in the noma database even after the retention script runs.
You can optionally run the retention script by hand immediately if you want to get the performance benefit right away. You can also do a vacuum operation on the database to regain lost disk space and make things more efficient.
First consider adjusting the default setting in:
from 90 days to what you want to have the retention be. Just edit the file and adjust the number as necessary.
To run the script by hand, log in and become the nagios user, then type:
To run a vacuum operation afterwards, also as the nagios user, type:
/usr/local/groundwork/postgresql/bin/psql -U noma -d noma -c 'vacuum (full, analyze) notification_logs'
The disk space will then be freed, and the table optimized.
Reversal of this patch will remove the new files, and remove the new cron job. Monitoring in general can continue while this happens.