Skip to content
This repository was archived by the owner on Oct 16, 2026. It is now read-only.
This repository was archived by the owner on Oct 16, 2026. It is now read-only.

trace: normalize OTLP and AgentV artifacts for Dashboard #1455

Closed

Description

@christso

Convert AgentV trace sidecars and OTLP JSON files into the Dashboard read model so the UI can render Phoenix-style trace trees without parsing raw OTLP directly.

Activity

  1. Necmttn commented on Jun 21, 2026

    @Necmttn

    For this normalization pass, I would keep the raw and dashboard layers separate.

    Raw OTLP/AgentV events should stay immutable, keyed by their source event id plus trace/span ids where present. The dashboard tree can then be a materialized read model over those rows, not the only persisted form of the trace.

    That buys two things:

    • idempotent re-projection when the AgentV or OTLP mapping changes
    • late correlation to sessions/artifacts without pretending telemetry and transcripts arrive in order

    The useful metadata to persist on the projection is probably source, source_event_id, trace_id, span_id, parent_id, projection_version, and raw_parser_version. If the UI later needs a different tree shape, you can rebuild it without losing provenance.


    Generated with ax.

  2. christso commented on Jun 22, 2026

    @christso
    CollaboratorAuthor

    Completed by PR #1474. The useful generic trace normalization work is merged; future trace-summary/cost direction is tracked in https://github.com/EntityProcess/agentv-beads/issues/9 and Phoenix surface cleanup in https://github.com/EntityProcess/agentv-beads/issues/10.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions