r35157/com_r35157_nenjim-hubd-impl_ref
SHA256
0
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects Releases Wiki Activity

Implement severity in JupiterPerpsAlarm #4

New Issue
Closed
opened 2026-06-19 11:23:02 +02:00 by minimons · 1 comment
minimons commented 2026-06-19 11:23:02 +02:00
Owner
Copy Link
Copy Source

Then an alarm is triggered, and PushOver notification is enabled, then severity is always critical now.
In the configuration file for JupiterPerpsAlarm we can set the severity, but it is never actually used.

We used be able to use these 3 levels (instead of just '2'):
(THIS IS CHANGED - SEE COMMENTS)
CRITICAL (as now - very loud and require acknowledgement/resend (this is a feature of PushOver, not in out code) - this is the current behaiviour)
IMPORTANT (as now - but WITHOUT resend and ackowledment (this is a parameter to the rest call to PushOver)
INFO (just a normal popup)

Then an alarm is triggered, and PushOver notification is enabled, then severity is always critical now. In the configuration file for JupiterPerpsAlarm we can set the severity, but it is never actually used. We used be able to use these 3 levels (instead of just '2'): (THIS IS CHANGED - SEE COMMENTS) ~~CRITICAL (as now - very loud and require acknowledgement/resend (this is a feature of PushOver, not in out code) - this is the current behaiviour) IMPORTANT (as now - but WITHOUT resend and ackowledment (this is a parameter to the rest call to PushOver) INFO (just a normal popup)~~
minimons added the enhancement label 2026-06-19 11:23:02 +02:00
minimons self-assigned this 2026-06-19 11:23:02 +02:00
minimons added this to the AssetAZ project 2026-06-19 11:23:02 +02:00
minimons commented 2026-06-19 11:44:53 +02:00
Author
Owner
Copy Link
Copy Source

ChatGPT and I have agreed to the following severity levels:

  • EMERGENCY = repeated wake-up alarm
  • CRITICAL = one-shot wake-up alarm
  • WARN = audible warning respecting quiet hours
  • INFO = low-priority visible notification
  • SILENT = no user interruption
ChatGPT and I have agreed to the following severity levels: - EMERGENCY = repeated wake-up alarm - CRITICAL = one-shot wake-up alarm - WARN = audible warning respecting quiet hours - INFO = low-priority visible notification - SILENT = no user interruption
minimons moved this to Done in AssetAZ on 2026-06-23 08:06:39 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project AssetAZ
Assignees
Clear assignees
builder (CICD User) minimons (Morten Green Hermansen)
No Assignees minimons
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: r35157/com_r35157_nenjim-hubd-impl_ref#4
Delete Branch "%!s()"

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?