Windows: Upload dump files from the S-TAP to the collector and central manager

You can configure the S-TAP® to automatically upload dump files upon restart, to the collector and the central manager, or only the collector.

The guard_tap.ini parameter upload_feature controls this upload feature:
  • 0: No automatic upload.
  • 1: Upload files to the collector and the central manager.
  • 2: Upload files only to the collector, even if there is a central manager.
If enabled, when the S-TAP restarts, and it detects a new dump file in one of the monitored folders, it:
  1. Collects all of the information (dump file, log files, etc.) from Program Files\IBM\Windows S-TAP\Logs.
  2. Compresses the files.
  3. Uploads the .zip file to the collector and/or central manager, to the folder /var/IBM/Guardium/log/stap_diagnostic.

The .zip file name is in the format: WSTAP_<computer name>_<ISO time of file creation>.zip

The files on the collector are purged to prevent excessive disk space usage. If the total space used is greater than 10 GB, the oldest files are purged to bring the size down to less than 10 GB. Files older than one month are purged, irrelevant of the disk space used. Only the files in /var/IBM/Guardium/log/stap_diagnostic are purged.

If the upload of a .zip file would result in /var going over 70%, then the .zip file is not uploaded.

For an S-TAP that was installed with GIM, the GIM server uses the threshold2 value defined in Utilization_Threshold for System Var Disk Usage, which is 70% by default. If the file to upload would result in system var disk usage over the threshold2 value, the upload is rejected. You can modify this value. See update_utilization_thresholds.