[dev.icinga.com #11445] Allow strings in state/type filters #4061
This issue has been migrated from Redmine: https://dev.icinga.com/issues/11445
Created by mfriedrich on 2016-03-24 09:58:01 +00:00
That way we can pass strings in JSON requests from the API or the configuration attributes.
Check where this might be necessary as well.
2016-06-21 15:40:48 +00:00 by mfriedrich 86699ec
2016-06-22 14:10:54 +00:00 by mfriedrich 729202d
2016-06-22 14:43:22 +00:00 by mfriedrich 7e3c9b2
2016-06-23 12:52:45 +00:00 by mfriedrich 14fdb79
2016-06-23 12:55:01 +00:00 by mfriedrich 091274e
2016-06-24 12:17:24 +00:00 by mfriedrich ab4ba18
The text was updated successfully, but these errors were encountered:
Updated by mfriedrich on 2016-06-21 15:39:21 +00:00
Possible changes for tests:
DB IDO User
-> there is a Bug in Icinga Web 2 which always adds "Downtime" to service notifications. So this is the backend.
Updated by mfriedrich on 2016-06-23 13:13:05 +00:00
Documentation updates are targeted with #12020.
Both methods for state/type filters (constants or string values) provide the correct "states" and "types" array values inside the REST API.
The NotificationFilterToString() method has been fixed. Furthermore I've tested various state and filter types with notifications and backend logging. This unveiled a bug in Web2, fix sent upstream.
Notification and User with Acknowledgement filter
User without Acknowledgement filter:
Updated by tobiasvdk on 2016-06-24 11:57:05 +00:00
For a service dependency I get the following:
I also tried
Updated by mfriedrich on 2016-06-24 12:19:07 +00:00
Fixed in git master.
Updated test config.