[mping]

On paper this looks smart, but when you hit a but that triggers under very specific conditions (weird bugs happen more often as you scale), you are gonna wish you had tracing for that.

The ideal setup is that you trace as much for some given time frame, if your stack supports compression and tiered storage it becomes cheap er

[rbanffy]

> you are gonna wish you had tracing for that

It’s never too late to add data collection and redeploy the affected service. If the bug is bad, you’ll be able to catch it then.