Skip to content

Upstream integration cycle: OTLP log export, desktop telemetry, and per-signal observability settings #689

Closed

Description

@rynfar

Covers the complete OTLP observability series through bounded upstream head fa1e1715538f6f8ac076761f7821f68479f616ab (tip of t3code-upstream/main).

Sources

SHA Upstream Description
3bb06ad910 #12493 feat(server): export log records over OTLP
82059df152 #12520 feat(desktop): export main process telemetry over OTLP
a8693eb4ed #12540 chore(desktop): leave main process metrics export off until a metric exists
fa1e171553 #12657 refactor(observability): hold OTLP export settings per signal

Boundaries to preserve

  • Pylon server and desktop Effect layers, configuration resolution, and test runners.
  • Brand naming (pylon-server and desktop service names, PYLON_* / T3CODE_* env compatibility).
  • Flusher lifecycle and clean shutdown behavior.
  • Adversarial audit of log serialization, secret redaction, and error boundary handling.

Verification plan

  • Server observability & logging tests (serverLogger.test.ts, Observability.ts, etc.).
  • Desktop observability tests (DesktopObservability.test.ts).
  • Workspace typecheck (pnpm typecheck).
  • Independent adversarial review pass.

Activity

  1. added a commit that references this issue on Sep 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions