Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #7899] Reload times of Status Cronk not configurable #1340

Closed
icinga-migration opened this issue Dec 1, 2014 · 4 comments
Closed

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/7899

Created by mhein on 2014-12-01 09:52:58 +00:00

Assignee: (none)
Status: New
Target Version: Backlog
Last Update: 2015-10-26 08:56:17 +00:00 (in Redmine)


Hi,

default reload time of the status cronk is about 10 seconds. In environments with 500 user this produces heavy load.

--- icinga-web/app/modules/Cronks/lib/js/Cronk/menu/ReloadStatus.js.orig
2014-11-26 14:48:37.000000000 +0100
+++ icinga-web/app/modules/Cronks/lib/js/Cronk/menu/ReloadStatus.js
2014-11-26 14:48:55.000000000 +0100
@@ -40,7 +40,7 @@

this.updateTask = {
run: this.updateDisplay,
- interval: 10000,
+ interval: 60000,
scope:this
};

@@ -92,4 +92,4 @@
AppKit.getTr().start(this.updateTask);
}
}
-});
\ No newline at end of file
+});

This interval must be configurable for convenience reasons that users don't need to patch the code.

@icinga-migration
Copy link
Author

Updated by mfrosch on 2015-03-12 10:58:12 +00:00

  • Status changed from New to Feedback

Marius, are you planning to implement this? :)

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-03-12 19:43:44 +00:00

  • Status changed from Feedback to New

@icinga-migration
Copy link
Author

Updated by berk on 2015-05-18 12:18:14 +00:00

  • Target Version set to Backlog

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-10-26 08:56:17 +00:00

  • Tracker changed from Bug to Feature
  • Category set to Framework

@icinga-migration icinga-migration added this to the Backlog milestone Jan 17, 2017
@dnsmichi dnsmichi removed this from the Backlog milestone Dec 19, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants