Projecting a few queried fields out of raw JSON while retaining the original…

Projecting a few queried fields out of raw JSON while retaining the original blob gives the best operational balance. Logfire's dynamic shredding demonstrates this pattern in practice (see their writeup: https://logfire.dev/dynamic-shredding), and I'd expect it to cut how often you must scan large opaque blobs during troubleshooting. Keep the blob for fidelity, extract and index the attributes you query, and you'll keep costs and latency more predictable as volume grows.