TechPrufer
Get started
GitLab
GitLab logoGitLab · Feature trail

Webhook Reliability and Self-Healing

3 posts · Aug 2016 – Nov 2024

What this trail covers

GitLab webhooks are being enhanced with self-healing capabilities. Previously, webhooks that encountered 4xx errors would be permanently disabled after multiple failures. The new system will temporarily disable webhooks of any error type (4xx, 5xx, network, etc.) with an increasing backoff period, up to 1 day. Webhooks will be permanently disabled only after 40 successive failures. Existing permanently disabled webhooks will be migrated to this new temporary disablement state. This aims to reduce the need for manual intervention when webhooks fail and improve overall reliability. This post details how to integrate GitLab webhooks with Twilio for SMS alerts on DevSecOps platform events, demonstrating a practical application of webhook reliability for immediate incident notification.

All GitLab trails
  1. GitLab Webhooks get smarter with self-healing capabilitiesIntroduces self-healing capabilities for GitLab webhooks, where failing webhooks will be temporarily disabled with an increasing backoff period (up to 1 day) instead of being permanently disabled after multiple 4xx errors. All error types (4xx, 5xx, network) will be treated the same. Webhooks will be permanently disabled after 40 successive failures. Existing permanently disabled webhooks will be migrated to this new temporary disablement state.
  2. Combine GitLab webhooks and Twilio for SMS alerts on DevSecOps platformThis post details the integration of GitLab webhooks with Twilio Functions to send SMS alerts for issue events. It outlines the setup of Twilio for SMS, the configuration of a Twilio Function to process webhook data and send messages, and the setup of GitLab project webhooks to trigger this function. The post also provides an example of expanding the use case to include multiple recipients, different event types, group-level configuration, and self-hosting message generation.
  3. Applying GitLab Labels AutomaticallyThis post details the implementation of a custom webhook server to automatically apply labels to GitLab merge requests. It describes how to process webhook events, identify merge requests, and use the GitLab API to update labels based on commit messages (e.g., '#patch', '#minor', '#major') and MR actions. It also provides code snippets for Ruby and discusses considerations for handling updates and multi-threading.