GWME-7.2.1-05 Notification Log Retention

compared with
Current by Bren Eckles
on Sep 27, 2018 10:15.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (11)

View Page History
h5. Prerequisites

You need to be running GroundWork Monitor Core or Enterprise, version 7.2.1. This technical bulletin does not depend upon prior technical bulletins.
* You need to be running GroundWork Monitor Core or Enterprise, version 7.2.1
* This technical bulletin does not depend upon prior technical bulletins
* There is no need to schedule a downtime to apply this technical bulletin

There is no need to schedule a downtime to apply this technical bulletin.

h5. Installation Steps

cd TB7.2.1-05-notification-logs
{noformat}
# Run the installer script.:
{noformat}
./TB7.2.1-05_install.sh
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.
# Respond to the install-confirmation prompt when it appears.
# New files will be copied into place. A new cronjob will be added, to impose retention control on NoMa log data. Monitoring in general can continue while this patch is installed.

h5. Usage

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:{noformat}/usr/local/groundwork/config/noma_retention.conf {noformat} /usr/local/groundwork/config/noma_retention.conf {noformat} 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:
/usr/local/groundwork/tools/noma_retention --logs
{noformat}
To run a vacuum operation afterwards, also as the {{nagios}} user, type:
{noformat}
/usr/local/groundwork/postgresql/bin/psql -U noma -d noma -c 'vacuum (full, analyze) notification_logs'
{noformat}
The disk space will then be freed, and the table optimized.

h5. Uninstalling
Reversal of this patch will remove the new files, and remove the new cron job. Monitoring in general can continue while this happens.

# As the {{root}} user, navigate to the patch-unpack directory you created when installing the patch. (If patch, (if that directory no longer exists, first unpack the patch again.) again).
{noformat}
cd TB7.2.1-05-notification-logs