[GH-ISSUE #920] SlackWebhookHandler can't prevent RuntimeException [proposal] #367

Closed
opened 2026-03-04 02:14:28 +03:00 by kerem · 3 comments
Owner

Originally created by @vrubiella on GitHub (Feb 7, 2017).
Original GitHub issue: https://github.com/Seldaek/monolog/issues/920

If slack sevice is down (or inactivated webhook), slow, or url is malformed, a Fatal RuntimeException raised.

I propose add configure options on the handler to ignore this errors or define timeout requests.

In other case we are "hard-coupling" our service to slack service.

Originally created by @vrubiella on GitHub (Feb 7, 2017). Original GitHub issue: https://github.com/Seldaek/monolog/issues/920 If slack sevice is down (or inactivated webhook), slow, or url is malformed, a Fatal RuntimeException raised. I propose add configure options on the handler to ignore this errors or define timeout requests. In other case we are "hard-coupling" our service to slack service.
kerem closed this issue 2026-03-04 02:14:29 +03:00
Author
Owner

@mintobit commented on GitHub (Feb 24, 2017):

@vrubiella Have you tried WhatFailureGroupHandler?

<!-- gh-comment-id:282289149 --> @mintobit commented on GitHub (Feb 24, 2017): @vrubiella Have you tried WhatFailureGroupHandler?
Author
Owner

@Seldaek commented on GitHub (Mar 12, 2017):

We offer the WhatFailureGroupHandler that lets you ignore failures from any handler. It's the recommended way to go because it lets you configure everything without hiding errors, and once you know everything work, if you think the logging is non-essential then you can wrap it with that and make sure a log failure does not bring down the application with it.

<!-- gh-comment-id:285957703 --> @Seldaek commented on GitHub (Mar 12, 2017): We offer the WhatFailureGroupHandler that lets you ignore failures from any handler. It's the recommended way to go because it lets you configure everything without hiding errors, and once you know everything work, if you think the logging is non-essential then you can wrap it with that and make sure a log failure does not bring down the application with it.
Author
Owner

@vrubiella commented on GitHub (Oct 4, 2017):

@Seldaek I didn't read you. Thanks!

<!-- gh-comment-id:334105247 --> @vrubiella commented on GitHub (Oct 4, 2017): @Seldaek I didn't read you. Thanks!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/monolog#367
No description provided.