mirror of
https://github.com/Seldaek/monolog.git
synced 2026-04-26 08:05:53 +03:00
[GH-ISSUE #187] Pushover Handler should send Priority #61
Labels
No labels
Bug
Documentation
Feature
Needs Work
Support
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/monolog#61
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @SteveEdson on GitHub (May 1, 2013).
Original GitHub issue: https://github.com/Seldaek/monolog/issues/187
The Pushover API is able to accept a priority for each message. On Android devices, high priority alerts in Pushover, are able to play through the devices alarm channel.
Monolog alerts such as critical, alert and emergency should be sent to Pushover as a high priority alert.
Example, Website goes offline in middle of night, a Monolog alert is triggered. This high priority pushover alert would be able to wake up a user, even if their device is set to silent.
@Seldaek commented on GitHub (Jun 26, 2013):
After looking at pushover docs in more details I guess we should add $emergencyLevel and $highPriorityLevel args with defaults to Logger::EMERGENCY and Logger::CRITICAL I'd say.
high priority records should have priority=1, and emergency ones priority=2, others can have priority=0 or unset.
@ArturMoczulski commented on GitHub (Jul 8, 2013):
also, this has been implemented with the defaults mentioned by Seldaek in the post above
@Seldaek commented on GitHub (Jul 11, 2013):
This is now available in master
@SteveEdson commented on GitHub (Jul 12, 2013):
Brilliant, thank you.