The open-source-blog execution flow in one diagram (with sequence chart)
Most open-source-blog articles stop at "how to use it" and never cover "when not to use it". This is an attempt at the second half.
Worth noting: the official docs do cover this, just in a very inconspicuous spot. I only found it reading the source comments, where the author explains the reasoning — roughly "so that it degrades into predictable behaviour in extreme cases".
We also fixed monitoring along the way: replaced average-based alerts with percentiles and split them per endpoint. False alerts dropped by about seventy percent and the on-call rotation visibly cheered up.