Global Memory Swap Surge Alert

The Global Memory Swap Surge alert monitors the virtual machines of all your Aviatrix Gateways and triggers an alert when any gateway meets both of the following conditions:

  • Swap memory (mem_swapped) is more than 0B.

  • Total memory is more than 1GB.

This alert serves to avoid situations where gateways are not responding due to swap memory being largely used.

You can change the default trigger conditions for this alert.

When the alert triggers, the event is listed in the CoPilot > Monitor > Notifications > Alerts page. In the Alerts page, search on Global Memory Swap Surge to see the number of times by date the alert type was triggered.

You can configure this alert to send a notification message to the notification channel (email or webhook) of your choice when the alert is triggered. See Configuring the Global Memory Swap Surge Alert.

If the Global Memory Swap Surge alert is triggered often, you may need to increase the size of the virtual machine running affected gateways.

Configuring the Global Memory Swap Surge Alert

To configure the Global Memory Swap Surge Alert:

  1. Go to the CoPilot > Monitor > Notifications page and click on Alerts Configuration.

  2. In the Search box, type Global Memory Swap Surge to quickly locate the relevant row in the table list and click the pencil icon in the row.

  3. In the Edit Alert dialog, do any of the following:

    • Change the OR operator if needed. By default, the alert triggers when all conditions are met (Matches All Conditions (ALL)). If you want the alert to trigger when any individual condition is met, change the operator to Matches any condition (OR).

    • Change the condition thresholds of this alert for the Memory Swapped and Memory Total metrics.

    • Change the Evaluation Period CoPilot uses for triggering the alert. The period is the duration of time (in minutes) where CoPilot evaluates the average of the metric(s) specified to trigger the alert. When the average value is outside the ideal operating range of your conditions, CoPilot will trigger the alert. The higher the number, the more data points CoPilot includes in the average calculation.

    • Set or change the minimum number of gateways that must meet the alert conditions to trigger the alert in Minimum Count of Matching Entities.

    • Set or change the recipients (email or webhook channels) of notification messages for the alert.

    • (Reset to Defaults) Revert back to default configuration values if you decide not to customize the alert’s configuration.

  4. Click Save.

CoPilot automatically resolves this alert when the alert metric(s) no longer meets the condition to trigger the alert. CoPilot resolves this alert only if all metrics on the affected Controller and CoPilot virtual machines do not meet the conditions any longer.

You cannot delete the Global Memory Swap Surge alert configuration.