Improve webhook error visibility by logging webhook response errors in Dashboard #1540
Description
What would you like to be added:
When the webhook server returns an invalid response (e.g. malformed JSON), users have difficulty debugging the issue.
PR #1539 attempted to send the webhook server’s error response back to clients, but this approach poses potential security risks (e.g. leaking internal infrastructure details).
<html>
<body>
<h1>Internal Server Error</h1>
<pre>
Error: Database connection failed
at DatabasePool.connect (/app/db/pool.js:45)
Connection: postgresql://admin:PASSWORD@internal-db:5432/webhookdb
</pre>
</body>
</html>Many platforms log webhook response errors in their Dashboards(e.g. https://liveblocks.io/docs/platform/webhooks), allowing users(developers) to inspect the full response and diagnose issues safely.
Instead of exposing the webhook response body to clients, log webhook response errors internally.
Why is this needed:
Display these logs in the Dashboard to help users debug webhook integration issues securely.