Project

General

Profile

Actions

Feature #13416

open

Change gateway monitoring actions default to "disabled"

Added by Chris Linstruth over 1 year ago. Updated 12 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Multi-WAN
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default

Description

I posit that the expense of running gateway monitoring actions is too expensive and disruptive to be enabled on every gateway, including VPN interface gateways, by default. In almost all cases other than Multi-WAN there is no reason to run the actions, but the monitoring history can be valuable.

The default on a new gateway should be gateway monitoring enabled, gateway monitoring actions disabled.

Enabling gateway monitoring actions should be moved to the documentation on enabling Multi-WAN as a required step. Possibly to enabling a routing protocol on a VPN link as well. And whatever other edge cases appear.

This, of course, should not change existing gateway settings.

Actions #1

Updated by Steve Wheeler 12 months ago

This seems like a good idea. The cost of running the gateway alarm event on a single WAN system far outweighs any benefits.

Actions #2

Updated by Ryan Coleman 12 months ago

Definitely a positive move - limit 'automatic' monitoring to if there's a gateway group existing or maybe just a 'strong recommendation'.

More often than not new users with WAN issues are experiencing a "DoS" ping killing their gateways without actual alarm/concern.

Actions #3

Updated by Craig Coonrad 12 months ago

Good idea. In my testing, the gateway monitoring action will mark the gateway down, although it is still functional. This leads to confusion.

Actions #4

Updated by George Phillips 12 months ago

Yes plz! Gateway actions on a single WAN (most of our customers) is silly and only complicates things. Monitoring should remain on, but the default should be no action taken.

Actions

Also available in: Atom PDF