Project

General

Profile

Bug #8593

Extend maximum gateway monitoring ping interval

Added by Justin Coffman 11 months ago. Updated 11 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Gateway monitoring
Target version:
Start date:
06/22/2018
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.4.x
Affected Architecture:
All

Description

The existing maximum gateway monitoring ping interval is 86,400 ms, or about a minute and a half. Over strictly metered connections, such as cellular backups, this can add up to significant costs over time. Recommend increasing the maximum monitoring interval to 86,400,000 ms (24 hours). PR to follow.

History

#2 Updated by Jim Pingle 11 months ago

The 86400 limit is likely a holdover from when it used to be seconds, but letting it go up to a full day seems like it wouldn't be very useful in practice. I'd say the highest it should go should maybe be around 30-60 minutes.

Beyond that, the check can be disabled so the gateway is assumed to be up, which is better for backup cellular WANs since it wouldn't send any checks. If it's a PPP device on the firewall you can see the up/down status in the interfaces widget/status since it would show the login uptime. If it's a device that exposes the connection as Ethernet that's trickier.

#3 Updated by Justin Coffman 11 months ago

I can modify it down to 3,600,000 ms (60 minutes) in the PR, if that works.

#4 Updated by Jim Pingle 11 months ago

  • Category set to Gateway monitoring
  • Target version set to 2.4.4
  • Affected Version set to 2.4.x
  • Affected Architecture set to All

I'd prefer that, but it's open for debate if there is a valid use case I'm not thinking of.

#5 Updated by Justin Coffman 11 months ago

I'll be honest, I didn't really have a maximum value in mind. I saw the existing value and thought "oh, they must have meant 86400 seconds, because that's a full day," and tacked on three zeroes. I do agree that a monitoring interval that long would have limited real world value. I'll bring the value down to 60 minutes.

#6 Updated by Justin Coffman 11 months ago

Change committed to the PR branch.

#7 Updated by Jim Pingle 11 months ago

  • Assignee set to Jim Pingle

#8 Updated by Jim Pingle 11 months ago

  • Status changed from New to Feedback

PR merged

#9 Updated by James Dekker 11 months ago

On 2.4.4.a.20180705.0032 you're able to set the probe interval to a max value of 36000000 as expected.

#10 Updated by Jim Pingle 11 months ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF