Hi Milan! Am 04.03.2016 um 15:03 schrieb Milan Koudelka: > thank you for your response. We use icingaweb2. However I think that > increasing this limit isn't good approach even in classic-ui, as it will > create big load on your browser. Better is to say something like "do the > action on this filter query".
We have concrete implementation plans for: a) "do the action on this filter query". We discussed this, we want to have this, I have no idea whether we have a related feature request so far. Please open one as a reminder for us. The worst thing that could happen is that someone closes it as a duplicate ;) Not sure whether Web2 will then fire a few thousand single requests or a DSL-crafted filter to the core, but both wouldn't really hurt. The latter is obviously faster to send. b) multiselect in the UI should work with thousands of elements. limit=500 is the maximum you can currently select in the frontend, but no one hinders you from afterwards changing the limit in the URL. Multiselect is a GET request per design, as we want the user to be able to copy & share most if not every link just from the browser location bar. As you correctly pointed out, the URL then get's too long, even before reaching 500 items. We want to solve this as explained in https://dev.icinga.org/issues/7360 Please leave a comment in case you want to push it ;) Cheers, Thomas -- Thomas Gelf Principal Consultant NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg Tel: +49 911 92885-0 | Fax: +49 911 92885-77 CEO: Julian Hein, Bernd Erk | AG Nuernberg HRB18461 http://www.netways.de | thomas.g...@netways.de ** OSDC 2016 - April - netways.de/osdc ** ** OSBConf 2016 - September - osbconf.org ** _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
