Is there *any* way to get pagination added to the edit setting pages? F/ex the "Sensors" page is unusable on a majority of my devices try waiting for load/render when you've got something like a fully loaded Juniper EX9214 so you can disable a sensor alert on one port ... ~300 ports - it's just pure pain assuming it finishes at all. And then you have to set PHP's limits so high to get the submit/save to work.
Another issue is I kind of need an ability to occasionally do a "reset all" on the limits page. Individually checking off hundreds of sensors is a completely unnecessary waste of time.
I realise I could go muck in the database for both of these in my particular but thats just not always an option and this just seems like something it should be doing when it hits a couple hundred records or some configurable limit.
On 2014-08-25 19:08, Michael Loftis wrote:
Is there *any* way to get pagination added to the edit setting pages? F/ex the "Sensors" page is unusable on a majority of my devices try waiting for load/render when you've got something like a fully loaded Juniper EX9214 so you can disable a sensor alert on one port ... ~300 ports - it's just pure pain assuming it finishes at all. And then you have to set PHP's limits so high to get the submit/save to work.
"Fully loaded" ASR9k with 500 sensors took ~10 seconds for the javascript to process on my system.
As this is an editing page and rarely needs to be loaded, I don't see the problem here. Certainly not enough problem to deal with the clusterfsck trying to paginate an editing page would cause.
Another issue is I kind of need an ability to occasionally do a "reset all" on the limits page. Individually checking off hundreds of sensors is a completely unnecessary waste of time.
This is actually pretty trivial in js. It's already done on the ports page.
It'll probably get done when someone gets around to it :)
adam.
participants (2)
-
Adam Armstrong -
Michael Loftis