Tagging @gweaver for to-do notification.

Hello, @thiagocsf .

I’m working with a customer who relies heavily on GitLab webhooks for security and compliance controls. They were surprised to see this request closed with the note that “The Webhooks category is on maintenance-only mode”, and I’d like to clarify the direction so I can respond accurately.

1. What does “maintenance-only” concretely mean for webhooks? Are they expected to remain a supported integration surface long term, or are they on a deprecation path in favor of another mechanism?
2. If there is a preferred long-term alternative (e.g., a different events or streaming mechanism), can you point to any docs or roadmap items?
3. Today, what is the recommended way for customers to be proactively notified when webhooks are failing or get disabled, without relying on frequent API polling (given rate limits)?

Any guidance here on strategy and current best practices would be very helpful. Thank you.