How to Reliably Test Internet Connection and Service Down Alerts

When testing an Internet Connection Check or other monitored service alert, the service should be observed as available before you simulate an outage.

If the service is already down when the alert is created or enabled, Auvik may not generate a new down alert because there has not been a new transition from an available state to an unavailable state.

Recommended test procedure

1. Confirm that the service is available

Before creating or enabling the alert, confirm that:

• The monitored service is reachable.
• The Internet Connection Check or cloud ping check is reporting successfully.
• The correct IP address, hostname, device, or service is selected.
• The service is included in the alert’s scope.

For Internet Connection Checks, confirm that the monitored public IP address responds to the required ICMP checks.

See:

• How do I monitor my internet connection status?
• Troubleshooting the internet connection check
   

2. Create or enable the alert

Create or enable the alert after confirming that the monitored service is available.

For Alerts v2:

1. Go to Manage Alerts > Alerts v2.
2. Create or open the service alert.
3. Confirm that the correct service is selected.
4. Review the trigger condition, clear condition, scope, and notification channels.
5. Save and enable the alert.

For Legacy alerts:

1. Go to Manage Alerts.
2. Open the applicable service alert.
3. Confirm that the correct service is selected.
4. Review the trigger condition, clear condition, scope, and notification channels.
5. Save and enable the alert.

3. Allow monitoring to confirm the available state

Wait for the service to be polled successfully after the alert is enabled.

The required time depends on the service’s monitoring interval, alert delay, and trigger condition. Allow enough time for Auvik to record the service as available before testing the outage.

4. Simulate the outage

During an approved maintenance window, simulate the service failure using a controlled method, such as:

• Disconnecting a test WAN or ISP link.
• Temporarily disabling a non-production service.
• Blocking the monitored traffic.
• Using a non-production test target.

Do not interrupt a production Internet connection or service unless the change has been approved and the expected impact is understood.

5. Wait for the alert to trigger

Allow time for:

• The service monitor to detect the failure.
• The trigger condition to be met.
• Any configured Alert Delay to expire.
• The notification channel to deliver the notification.

A short interruption may not trigger an alert if it does not meet the configured packet-loss threshold, failure count, or time delay.

See How to set Alert Delays with Alerts v2
 

6. Restore the service

Restore the connection or service and confirm that:

• The service returns to an available state.
• The alert clears according to its clear condition.
• A clear notification is sent if one is configured.
• The alert timeline reflects the expected detection and resolution times.

Verify the notification channel separately

The Send Test Alert function can confirm that a notification channel can deliver a test notification. It does not reproduce the monitored service’s trigger condition or validate the service alert’s detection timing.

To test a notification channel:

1. Go to Manage Alerts > Notification Channels.
2. Select the notification channel.
3. Click Send Test Alert.
4. Select the site where the test should originate.
5. Click Send.
6. Confirm that the destination receives the test notification.

See How to Use the Send Test Alert Function
 

If the alert does not trigger

Check the following:

• The service was confirmed available before the test.
• The alert is enabled.
• The correct device or service is selected.
• The alert scope includes the monitored service.
• The trigger threshold and evaluation period are correct.
• The Alert Delay is not longer than the test outage.
• A maintenance window is not suppressing the notification.
• Alert suppression or dependency rules are not preventing delivery.
• The correct notification channel is associated with the alert.
• The notification channel is active and configured for the intended recipients.

If the service was already down when the alert was created or enabled, restore it first, allow Auvik to observe the available state, and then repeat the test.

Related articles

• How to Alert on Packet Loss on Cloud Ping Checks
• Creating Alerts using Alerts v2
• Creating Alert Notifications using Alerts v2
• How do I start, stop, add, edit, or delete monitoring for services?