fix(profiles): enable trace queries with the v2 storage backend #75

Merged

binjovi-bot merged 1 commit from codex/pipeline-profile-query-v2-20260909 into trunk

2026-09-09 11:44:24 +00:00

sean commented

2026-09-09 11:43:20 +00:00

Owner

Validation: reproduced the HTTP 501, then passed a real Pyroscope 2.3.1 integration check. Two traces in one profile return 3 and 7 samples; the combined query returns 10. Span filters isolate the same samples and an unknown span returns zero. Repository checks and Kubernetes server dry-run pass.

V1 data from 11:40 UTC until this rollout stays on disk but falls outside the new reader. This is a canary; fleet rollout still requires the overhead gate.

The live v1 store returns HTTP 501 for exact trace selection. Enable the v2 segment writer and reader, with the legacy reader retained before the declared cutover. Use seven-day retention for both storage versions and keep metadata and compaction work on the persistent disk. Validation: reproduced the HTTP 501, then passed a real Pyroscope 2.3.1 integration check. Two traces in one profile return 3 and 7 samples; the combined query returns 10. Span filters isolate the same samples and an unknown span returns zero. Repository checks and Kubernetes server dry-run pass. V1 data from 11:40 UTC until this rollout stays on disk but falls outside the new reader. This is a canary; fleet rollout still requires the overhead gate.

sean added 1 commit

2026-09-09 11:43:20 +00:00