Webhook Enhancements and Event Flow Control

[hackerwins]

What would you like to be added:

Following the introduction of webhooks for authz and events (#188, #1156), we aim to improve stability and operational efficiency.

High Priority

1. Event Timing Control Library

   • Feature: Implement a rate limiter for event flow control.
   • Scope: Apply to both webhook and Pub/Sub events.
   • Goal: Prevent excessive event triggering.
   • Implementation: Develop a shared library for event timing control.

2. Webhook Failover Policy

   • Feature: Handle temporary network failures. Status(active, inactive) of webhook.
   • Scope: Define max retry attempts and retry intervals.
   • Goal: Ensure reliable event delivery.
   • Implementation: Introduce a basic retry mechanism with configurable parameters.

3. Webhook Call Result Logging

   • Feature: Log success/failure states for each webhook call.
   • Scope: Store essential debugging information.
   • Goal: Improve troubleshooting and monitoring.
   • Implementation: Establish a basic logging infrastructure.

Medium Priority

1. Dashboard UI Development

   • Feature: Develop an interface for webhook configuration and event monitoring.
   • Goal: Provide operational visibility.
   • Scope: Implement a basic management UI. Consider to introduce webhooks as a list.

2. Test Endpoint for Webhooks

   • Feature: Allow developers to trigger sample events and test webhook integrations.
   • Goal: Improve the developer experience.
   • Scope: Set up the necessary testing infrastructure.

Low Priority

1. Add Webhook Secret Key

   • Feature: Review the use of a project secret key and consider to add secret key to webhook.
   • Goal: Enhance webhook security.
   • Scope: Implement secret key to webhook.

2. Webhook Status Monitoring System

   • Feature: Collect detailed metrics, implement health checks, and set up alerts.
   • Goal: Strengthen operational monitoring.
   • Scope: Build a comprehensive monitoring solution.

Note

• Refer to https://liveblocks.io/docs/platform/webhooks

Why is this needed:

This issue outlines the next steps to enhance webhook reliability, monitoring, and security.