Project

General

Profile

Bug #18438

Allow adjusting notification checking period

Added by Thomas McKay almost 5 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Notifications
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Checking for notifications every 10 seconds seems excessive.

At a minimum I'd like a way to increase that period on a per-organization basis.

Another idea would be to have the time between checks increase with idle activity. Start at 10 seconds but if no user interaction with UI, begin to bump up the interval to some max (perhaps every one minute?). This should be configurable as well.


Related issues

Related to Foreman - Feature #19535: Silence notification Rails logsRejected
Has duplicate Foreman - Refactor #18961: Reduce frequency of notification pollingDuplicate2017-03-20

Associated revisions

Revision b8c9069d (diff)
Added by matan werbner over 4 years ago

Fixes #18438 - control notifications polling

History

#1 Updated by Gail Steiger almost 5 years ago

I think it would be more worthwhile to implement websockets sooner rather than setting up an interim configuration mechanism.

#2 Updated by Ohad Levy almost 5 years ago

Gail, websockets is probably not feasible in the near/immediate future

#3 Updated by Ohad Levy over 4 years ago

  • Has duplicate Refactor #18961: Reduce frequency of notification polling added

#4 Updated by The Foreman Bot over 4 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/4520 added

#5 Updated by matan werbner over 4 years ago

  • Status changed from Ready For Testing to New
  • Assignee set to matan werbner
  • Pull request deleted (https://github.com/theforeman/foreman/pull/4520)

#6 Updated by Dominic Cleal over 4 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/4520 added

#7 Updated by Lukas Zapletal over 4 years ago

#8 Updated by matan werbner over 4 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#9 Updated by Marek Hulán over 4 years ago

  • Legacy Backlogs Release (now unused) set to 240

Also available in: Atom PDF