Customizing events

There are two types of events:

  • Airlock Gateway defines internal events. The administrator can't change those events. They may be changed with product updates in the future.
  • Customizable events cover events highly dependent on the Airlock Gateway usage scenario, i.e., the number of requests per second.

This article describes how to customize events configured in the event rule file /opt/airlock/custom-settings/logsurfer.

 
Notice

Do not use event customization to suppress event messages, i.e., to cover a misconfiguration, system or network problems, etc.

Best practice:

  • Thoroughly check overall Airlock Gateway and system configuration when events occur frequently or at an unusual pace.
  • Fix the cause of event warnings rather than adjust the event configuration.
  • Before changing the file, create a copy of it for backup reasons.

Customization example

  1. Backup the file /opt/airlock/custom-settings/logsurfer.
  2.  
    Terminal box
    cd /opt/airlock/custom-settings/logsurfer 
cp logsurfer.conf.user.custom logsurfer.conf.user.custom.orig 
vi logsurfer.conf.user.custom
  3. Adjust the event settings in the file logsurfer.conf.user.custom to your needs. The file contains comments that describe the default values – you may use them for orientation and information purposes.
  4.  
    Terminal box
    vi logsurfer.conf.user.custom

  5. Example:

  6.  
    Example
    # responsetime is higher than 3 seconds 5 or more times in 2 minutes 
WR_SG_SUMMARY_BackendResponseTime_enable=true 
WR_SG_SUMMARY_BackendResponseTime_num=5 
WR_SG_SUMMARY_BackendResponseTime_range=120
  7. After changing the file logsurfer.conf.user.custom, the service airlock-logsurfer has to be restarted with:
  8.  
    Terminal box
    systemctl restart airlock-logsurfer.service

Further information and links

Internal links: