You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of ratelimitqueue assumes a single worker thread which processes events; suitable for PagerDuty's current rate limit (120 per minute per key).
If PagerDuty decides to increase their rate limit per integration key, the event handler should be updated to process more events to meet the new rate limit. This is possible by ensuring queue is processed by a pool of workers in parallel.
The current implementation of
ratelimitqueue
assumes a single worker thread which processes events; suitable for PagerDuty's current rate limit (120 per minute per key).If PagerDuty decides to increase their rate limit per integration key, the event handler should be updated to process more events to meet the new rate limit. This is possible by ensuring queue is processed by a pool of workers in parallel.
Example implementation: https://github.com/JohnPaton/ratelimitqueue/blob/master/examples/example_workers.py
The text was updated successfully, but these errors were encountered: