Notification System 2: The Realerting #151
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
parasitepool/para!151
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "parabit/event-notifications"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Excellent callout, will prune
@ -35,0 +36,4 @@long,help = "The channel at ntfy.sh to use for block found notifications")]pub(crate) alerts_ntfy_channel: Option<String>,I plan to add additional alerts services in the future (email/text/carrier pigeon) and the aim was to reduce the potential future confusion. I am open to instead opening an issue against that plan and dropping the
ntfyif you feel that is more natural.The second one worked with simulated events, but has not been tested fully end-to-end.
It will actually require one additional para server and that they be linked via sync. I believe this can actually be implemented as a test as we have all the individual parts working now and they have test wrappers.