The v0.17.0 release will provide multiple new bulk filtering options, but does not allow for chaining or logical ANDing all criteria together in order to explicitly exclude or include Triggered Alarms.
While bulk filtering is still useful (many use cases), it doesn't allow for example, selectively excluding memory usage alarms for a specific system name (or name substring).
This issue is intended to track word towards implementing this functionality in a future release.
Note: The goal is to retain bulk filtering functionality, but add new functionality. The current thinking is that filter settings applied using the selective filter will override any bulk filter functionality.
The
v0.17.0
release will provide multiple new bulk filtering options, but does not allow for chaining or logical ANDing all criteria together in order to explicitly exclude or include Triggered Alarms.While bulk filtering is still useful (many use cases), it doesn't allow for example, selectively excluding memory usage alarms for a specific system name (or name substring).
This issue is intended to track word towards implementing this functionality in a future release.