Hanne Moa
Hanne Moa
> Blocked by Uninett/Argus-frontend#70. Modelling of severity values is needed. We don't need to wait on severity to add support for openness/ackedness. We can do things in small, incremental steps.
Notes from design day: - Store tags in a json blob on incident - Still have an endpoint of tags, for typeahead in frontend - get rid of "filter string...
Plan: - [ ] implement open, ack, stateful as fields on the Filter-model - [ ] implement source type as field on the Filter-model - [ ] implement severity as...
Django has views for it, we just need to add them to urls.py and style them.
This will mean it won't be possible to have shorter than one hour intervals of (not) sending notifications. Proddata: ``` count | start -------+---------- 1 | 10:00:00 1 | 15:00:00...
The end time == 14:30 is mine, as a test. I will ask the owner of start time == 07:20 how important that level of precision is.
Owner of the 0720 start time won't mind whole hours precision.
While making the statistics I discovered that "end" is magic in postgres. (It is not possible to write `SELECT end FROM argus_notificationprofile_timerecurrence;`, you get a syntax error. `SELECT start FROM...
This is probably why: https://www.postgresql.org/docs/current/sql-end.html
NEW FRONTEND BELOW!