Determining monthly request volume for Gateway to Microgateway migration

Airlock Microgateway licensing is based on the number of HTTP requests processed per month. Therefore, organizations planning to migrate from Airlock Gateway to Airlock Microgateway must determine their expected monthly request volume.

Prerequisites

  • Log data must cover at least one full month.
  • If using an Airlock Gateway cluster (Active/Passive):
    • No failover must have occurred during the selected period.
    • If a failover did occur, combine the request counts from both cluster members to obtain the correct total.
  •  
    Info

    To determine the monthly request volume reliably, the combined uptime of both cluster members must span at least one full month. To verify this, perform the following steps for both cluster members:

    1. Go to:
      Log & Report >> System Monitor
    2. Click on the Uptime diagram for a more detailed view.
    3. Check the diagram for a green area that represents system uptime, and determine the number of uptime days based on it.
    4. If the total uptime of both cluster members amounts to 30 days or more, the cluster can be used to determine the request volume.

Determining the monthly request volume in Airlock Gateway

  1. Go to:
    Log & Report >> Reporting
  2. Kibana opens in Dashboards view.
  3. In the upper-right corner, set the range to a one-month period (e.g., Last one month).
  4. The number of requests during the specified period is displayed in the Requests Total tile.

Determining the monthly request volume in an external log management system (e.g., Splunk)

  1. Search for all log lines that contain WR-SG-SUMMARY.
  2. Limit the search to a one-month period.
  3. The number of matching log entries represents the total number of requests during the specified period.