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
We've recently had an uptick in outages associated with the GO API (and the pass back to GOlr).
As we're already getting Enterprise Cloudflare for "free", I thought it would be good to experiment with the traffic shaping / QoS items in Cloudflare to see if there is anything that might be useful to us.
This is currently a low-effort background task, as we created log-only rules in Cloudflare to see if we're catching the right "bad" traffic.
The text was updated successfully, but these errors were encountered:
We've had a couple of spikes and I've tried filtering various ways to catch them after the fact. However, I am unsure that this will be effective, and it's often not any kind of obvious bot with an issue.
It may be more effective to try and catch actually outages while they occur (rather than spikes after the fact) and tune on them specifically.
We've recently had an uptick in outages associated with the GO API (and the pass back to GOlr).
As we're already getting Enterprise Cloudflare for "free", I thought it would be good to experiment with the traffic shaping / QoS items in Cloudflare to see if there is anything that might be useful to us.
This is currently a low-effort background task, as we created log-only rules in Cloudflare to see if we're catching the right "bad" traffic.
The text was updated successfully, but these errors were encountered: