This PR implements traffic drop notifications, similar to already implemented spike notifications.
Postgres migration included that extends the spike_notifications table with a type field indicating whether the notification is tracking drops or spikes. Table name should be probably left intact - since we don't have a way to run a migration renaming it.
[ ] Extract migration to a separate PR once review is concluded
It's important we don't send out drop notifications if e.g. traffic is barred via payment issues, hence the worker looks owner's accept_traffic_until up.
BTW the PR makes it no longer possible to set a negative threshold.
Changes
This PR implements traffic drop notifications, similar to already implemented spike notifications.
Postgres migration included that extends the
spike_notifications
table with atype
field indicating whether the notification is tracking drops or spikes. Table name should be probably left intact - since we don't have a way to run a migration renaming it.It's important we don't send out drop notifications if e.g. traffic is barred via payment issues, hence the worker looks owner's
accept_traffic_until
up.BTW the PR makes it no longer possible to set a negative threshold.
Tests
Changelog
Documentation
Dark mode