Limit number of alarms returned by the FM DS
Description
Lucidchart Diagrams
Activity
Benjamin Reed December 12, 2018 at 3:00 PM
Merged to develop.
Benjamin Reed December 5, 2018 at 9:55 PM
Because OpenNMS.js strips the totalCount property from alarm results it turns out to be difficult to put a warning in the alarm browser, but it's easy to note it in the editor where you set the limit. I made it show a warning if you've set the limit to anything other than 0.
Benjamin Reed December 5, 2018 at 9:51 PM
The frontend changes are part of the ranger/helm-3-improvements branch that will include a few other HELM-* issues as well. WIP here: https://github.com/OpenNMS/opennms-helm/tree/ranger/helm-3-improvements
Jesse White November 28, 2018 at 7:02 PM
One point that was brought up here is that sorting won't work as expected when the result set is limited, since the sorting is done on the client side.
To help make this clear to the user, we could add some icon/label on the alarm table panel to help indicate that they are only working on a subset of the results.
Details
Details
Assignee
Reporter
Labels
Components
Sprint
Fix versions
Priority
MajorPagerDuty
PagerDuty Incident
PagerDuty
The alarm table panel can get quite slow when handling large result sets returned by the FM DS, particularly when the system has hundreds, or thousands of alarms present.
We should add the option to limit the number of alarms returned by the FM DS. This limit should be configurable from the query editor.