This technical bulletin is for all GroundWork customers. It provides an update to the SLA processing and dashboards (for enterprise customers) and the downtime scheduler "slareport" database. It is applicable to GroundWork Monitor 7.2.1 only, and requires the application of the GWME-7.2.1-00 Rollup Patch Installer.
This patch will add a cron job to remove historical expired downtimes from the database. By default only downtimes expired for more than 60 days will be removed, but you have to enable this. See install steps below.
This technical bulletin does not depend upon prior technical bulletins. There is no need to schedule a downtime to apply this technical bulletin.
- You need to be running GroundWork Monitor Core or Enterprise, version 7.2.1.
- You must have already installed any version of the GWME-7.2.1-00 Rollup Patch Installer.
- As root user, copy the attached tgz to the /tmp directory on the GroundWork server.
- Unpack the tar using the command:
- Change into the directory created by untarring:
- Run the installer script, and respond to the prompt:
The install script will test that you are on a 7.2.1 system (which is required), that you have installed the 7.2.1 Rollup Patch, that you have not already installed this patch, and that you want to go ahead.
A backup will be created for rollback in case the install is interrupted. A new maintenance script and configuration file will be copied into place. The related cron job will be modified so it doesn't run if a previous execution is still running. A new cronjob will be added, to impose retention control on SLA downtime and audit-trail data. Only the cron job will be affected.
There are no special usage instructions, but if you want to get the benefit of the trimmed database right away, you can follow these steps:
- (Optional) Edit the file:
and change the days value from the default of 90 to the desired number of days to retain expired downtime and audit trail information.
- As the nagios user, run:
This may take a minute or two.
- (Optional) Clean up the database after deleting records by:
- Logging in as the root (or superuser).
and supply the postgres user password.
- Enter at the sql prompt:
Reversal of this patch will remove the new files, and it's best to put back the original cron job setup. Monitoring in general can continue while this happens. If you had previously modified the frequency of the yiic downtime process cronjob, you will want to edit that again after uninstalling this patch.
- As the root user, navigate to the patch-unpack directory you created when installing the patch, (if that directory no longer exists, first unpack the patch again):
- Run the uninstall command:
- If you added the optional crontab mentioned above, you should remove it.