docs(tracing): document allocation cost-trace hardening batch (June)#219
Open
simozzy wants to merge 1 commit into
Open
docs(tracing): document allocation cost-trace hardening batch (June)#219simozzy wants to merge 1 commit into
simozzy wants to merge 1 commit into
Conversation
Supersedes #217 and #218. Consolidates the June cost-tracing work into one coherent story: - Usage guide: a "results built by more than one allocation" note — the agent reports candidate steps and asks which to trace, or auto-routes when the question narrows to one step's rows (Tier B, sc-22795 / #6427, #6428). - June What's New: fold the hardening into the existing "Allocation root-cause tracing" entry — multi-writer handling, real-world column names (spaces / parens / %), StarRocks as well as Databend/Postgres, friendly table names, and driver/basis-table data-freshness (sc-22787/22790/22791/22801/22802). Only merged work is documented; the anomaly-percentile fix (sc-22803, plaid #6435) is excluded until it lands. The REST trace endpoint is intentionally not documented (agent/MCP is the customer-facing surface). 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
plaidcloud-docs | fc08a3f | Commit Preview URL Branch Preview URL |
Jul 01 2026, 03:31 PM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Consolidates the June allocation cost-tracing work into the docs, in one coherent story. Supersedes #217 and #218 (both edited June's What's New and would collide) — please close those in favour of this.
Changes
Usage guide (
tracing-allocations.mdx) — adds a "Results built by more than one allocation" note: the agent lists the candidate steps and asks which to trace, or auto-routes to the right one when the question narrows to rows only that step produced (Tier B, sc-22795 / plaid #6427, #6428).June What's New (
releases/2026-06.mdx) — folds the hardening into the existing "Allocation root-cause tracing" entry rather than listing internal-sounding bug fixes:%(sc-22787 #6420, sc-22790 #6425)Scope notes
🤖 Generated with Claude Code