Skip to main content
Solved

Webhook Output Lacks Option To Rate-Limit Calls Per Request

  • January 20, 2026
  • 6 replies
  • 6 views
M
This message originated from Cribl Community Slack.
Click here to view the original link.

In the webhook output, there's an 'event per request' setting. But am I correct to say there's no option to rate-limit the calls?

Best answer by Stefan Laschitzki

You can reduce the number of error by specifying an exponential retry for 429 in the retry section and potentially reduced concurrency. The "error" handling is not configurable, though

6 replies

S
Not as of now. You can configure the concurrency, but not a real rate-limit. Rate-limiting has been introduced to Cribl2Cribl protocols recently. It might get transported to other Destinations going forward.
M
Any other way to cleanly handle the 429 returns? I'd like cribl to stop throwing errors and increase the error counter because of this. Cribl can perfectly engage a backpressure disk buffer and slowly empty it by the time the next run comes around.
S
You can reduce the number of error by specifying an exponential retry for 429 in the retry section and potentially reduced concurrency. The "error" handling is not configurable, though
M
Ah, found it. Let me fiddle with that to at least reduce the amount of errors thrown.
M
Do you happen to have a reference for a feature request to get rate limiting in outbound webhooks?
S
I guess it fits into PROD-209, but I'd recommend to raise it in https://cribl-community.slack.com/archives/CGCU5A18B. Then PM can properly map it.
Terms & ConditionsAccessibility statement