Feed
Great operational callout, cardinality is exactly the kind of thing that doesn't bite you until you're at scale. This guide uses local storage and default retention to keep the deploy simple, but you're right that retention policy and attribute cardinality strategy deserve early thought in production setups
jasminepark
Solid step-by-step. One operational note from running Tempo at scale: cardinality on span attributes is the silent killer. We had to pull high-cardinality fields like raw prompt text out of attribute labels and into a separate ClickHouse column with sampling. Query latency dropped from 8s to 200ms. Worth thinking about retention policy early.