feat(db): add migration for traces and spans tables

[koxudaxi]

TL;DR

Added database schema for traces and spans to support distributed tracing functionality.

What changed?

• Created a new traces table to store trace information with fields for:

  • Trace identifiers
  • Service information (name, version)
  • Resource attributes
  • Organization/project/environment relationships

• Created a new spans table to store span data with fields for:

  • Span identifiers and relationships (trace_id, span_id, parent_span_id)
  • Timing information (start/end times)
  • Span attributes, status, events, and links
  • Performance metadata (dropped counts)

• Added appropriate foreign key constraints to maintain data integrity

• Created indexes to optimize query performance for common access patterns

How to test?

1. Apply the migration to a test database
2. Verify the tables are created with the correct schema
3. Test inserting trace and span data to ensure constraints work properly
4. Verify the indexes are created and used in relevant queries

Why make this change?

This database schema is the foundation for implementing distributed tracing capabilities in our application. The tables will store OpenTelemetry-compatible trace and span data, allowing us to:

• Track request flows across multiple services
• Analyze performance bottlenecks
• Troubleshoot errors in distributed systems
• Provide observability into application behavior

[koxudaxi]

• feat(api): add API Key auth to /traces endpoint #1607 : 2 dependent PRs (#1609 , #1768 )
• feat(db): add TraceService for OTLP ingestion #1606
• feat(db): add migration for traces and spans tables #1605 👈 (View in Graphite)
• feat(db): add traces and spans schema #1604
• fix(api): distinguish handler NotFoundError from route-not-found in Effect API #1635
• v2

This stack of pull requests is managed by Graphite. Learn more about stacking.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	v2-docs	f2e8bb0	Jan 05 2026, 02:16 PM

[willbakst]

The migration files here are wrong. I believe v2 base is at 0011 right now.

Also, this is missing the journal update as well? Did you clear the migrations and run bun run db:generate?

[willbakst]

Please resolve merge conflicts

[koxudaxi]

Merge activity

• Jan 5, 2:12 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jan 5, 2:12 PM UTC: @koxudaxi merged this pull request with Graphite.