feat: add traces_detail_by_time table and materialized view for enhanced trace data retrieval

[JivusAyrus]

Summary by CodeRabbit

• New Features
  • Added a time-partitioned trace details dataset for improved trace analysis and filtering.
  • Added automatic ingestion of root-span details, including operation, client, HTTP, status, and error information.
  • Added optimized filtering across common trace attributes and automatic removal of data older than 30 days.

Checklist

• I have discussed my proposed changes in an issue and have received approval to proceed.
• I have followed the coding standards of the project.
• Tests or benchmarks have been added or updated.
• If applicable, I have provided instructions for reviewers for manually validating my changes.
• Documentation has been updated on https://github.com/wundergraph/docs-website.
• I have read the Contributors Guide.

[coderabbitai]

Walkthrough

Adds a ClickHouse table for time-partitioned trace span details and a materialized view that transforms eligible router root spans from cosmo.otel_traces into the new table.

Changes

Trace detail storage

Layer / File(s)	Summary
Trace detail table schema controlplane/clickhouse/migrations/20260707090829_traces_detail_by_time.sql	Creates cosmo.traces_detail_by_time with trace metadata, timestamps, status fields, HTTP/client attributes, query indexes, UTC-date partitioning, and 30-day TTL cleanup.
Root-span materialized view controlplane/clickhouse/migrations/20260707090830_traces_detail_by_time_mv.sql	Creates a materialized view that transforms eligible router root spans from cosmo.otel_traces, computes error status, maps span attributes, and supports rollback.

Estimated code review effort: 3 (Moderate) | ~20 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: adding the traces_detail_by_time table and materialized view for trace retrieval.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

---

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 71.16%. Comparing base (64eaf60) to head (fbf56b6).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3093      +/-   ##
==========================================
+ Coverage   62.37%   71.16%   +8.79%     
==========================================
  Files         262      335      +73     
  Lines       31003    49389   +18386     
  Branches        0     6049    +6049     
==========================================
+ Hits        19337    35146   +15809     
- Misses      10158    14217    +4059     
+ Partials     1508       26    -1482     

see 597 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[comatory]

Is this a prep work? I only see new tables being added, where's the application logic?

[JivusAyrus]

Is this a prep work? I only see new tables being added, where's the application logic?

We create the tables and leave them for 30 days, so the data gets populated and after that we change the code to use these tables.

[claude]

Claude Code Review

Claude Code Review is paused for this repository. To reconnect it, an admin of this repository's GitHub organization (or the account owner, for personal repositories) who can also manage your Claude organization's Code Review settings needs to re-link GitHub in Code Review settings. This is a one-time step.

_{Tip: disable this comment in your organization's Code Review settings.}