I tried to implement a generic webhook handler using HTTP(S) POST requests with a JSON payload.
I have seen an old discussion regarding the implementation of generic handlers and using third-party packages for more specific handlers, but believe this handler would be a good addition to the monolog core package.

• As mentioned here there are many plattforms like zapier and n8n (or building something yourself) that provide webhook endpoints to accept data in pretty much any format. Instead of creating more and more handlers for each of these plattforms or requiring third-party packages, this handler could be used for most of these plattforms.
• The handler currently extends the SocketHandler (adapted from the FleepHookHandler integration). Is this still the preferred way instead uf using curl?
• The only handler that would provide similar functionality would be the PSR-18 HTTP client integration, but requires another package and looks like maintenance lags behind.
• Didn't have the time to look into more features, like supporting secrets or other forms of authentication, but in that case it would probably be better to use PSR-18 clients directly. Is there a reason why this is a separate package but very specific integrations are part of the core?

My specific use-case would be to easily send logs to external webhooks - in my case inside a Laravel application, which allows for simple monolog configuration: e.g. https://github.com/laravel/laravel/blob/12.x/config/logging.php#L85
With this handler it could look like this:

'webhook' => [
    'driver' => 'monolog',
    'level' => env('LOG_LEVEL', 'warning'),
    'handler' => env('LOG_WEBHOOK_HANDLER', WebhookHandler::class),
    'handler_with' => [
        'url' => env('LOG_WEBHOOK_URL'),
    ],
],
// LOG_WEBHOOK_URL="https://example.com/webhook/abc123"

Just wanted to make a proposal. If you recommend another approach, let me know.