Closed tdavis6 closed 9 months ago
So sorry, just read the ntfy.js file and this appears to be the intended behavior. This is based on lines 44-45.
The behaviour is this way since https://github.com/louislam/uptime-kuma/pull/2863
=> down monitors have n+1 priority
Thank you so much for the quick reply!
appears to be the intended behavior
Missing documentation / confusing UX is a bug too (!). I think this should have a help text in the frontend
@tdavis6
What do you think about such a helptext ?
I am struggling to find a formulation which does not include max(5, priority + 1)
. Do you have any good ideas?
Okay. I think I found a way which does not include a formula. Oppinions?
I think that looks good! However, if the set priority is 3 and it bumps it to 4 that might not be clear. I'm trying to think of something that would make that behavior clear, without being too long to put there.
Perhaps "All events are sent with this priority, except DOWN-events, which have a priority one above this, with a maximum of 5". Although this might be too long.
Thank you so much for helping me!
I wasn't aware of this functionality. Would it be too much to have a separate priority for down alerts?
β οΈ Please verify that this bug has NOT been raised before.
π‘οΈ Security Policy
Description
When a notification is triggered, it sends to ntfy with a priority of 5. This is the incorrect behavior because it is set to send with a priority of 4. The double chevron indicates a priority of 4, while the triple chevron indicates a priority of 5.
Thank you so much for such an awesome app!
π Reproduction steps
This is triggered by setting a notification to use ntfy, with a priority of 4. Then, if a monitor goes down, the notification is sent with a priority of 5.
π Expected behavior
It would be expected that the notification is sent with a priority of 4.
π Actual Behavior
The notification was sent with a priority of 5.
π» Uptime-Kuma Version
1.23.8
π» Operating System and Arch
Synology DSM 7.2.1-69057 Update 3
π Browser
Firefox 120.0.1
π Docker Version
20.10.23
π© NodeJS Version
No response
π Relevant log output
No response