observability: OpenTelemetry tracing across services, LLM calls and task containers #1326

Closed
opened 2026-10-27 13:39:56 +00:00 by sam · 0 comments
Owner

archie-core has no tracing: no go.opentelemetry.io import, no tracer provider, no traceparent anywhere. A task crosses gateway, state store, archied, NATS and an agent container with nothing to correlate the hops except inconsistent slog keys (task, task_id, event_id). Delivered in four stages; each is useful on its own.

Acceptance criteria

One task's life (event intake, dispatch, container run, LLM calls, result) is visible as one trace, and its log lines carry the trace id.

Close reason

All children complete.


Imported from beads archie-core-fzb3x · GitHub #1856 · type epic · priority P2 · created 2026-10-25 · closed 2026-10-27

archie-core has no tracing: no go.opentelemetry.io import, no tracer provider, no traceparent anywhere. A task crosses gateway, state store, archied, NATS and an agent container with nothing to correlate the hops except inconsistent slog keys (task, task_id, event_id). Delivered in four stages; each is useful on its own. ### Acceptance criteria One task's life (event intake, dispatch, container run, LLM calls, result) is visible as one trace, and its log lines carry the trace id. ### Close reason All children complete. --- _Imported from beads `archie-core-fzb3x` · GitHub #1856 · type epic · priority P2 · created 2026-10-25 · closed 2026-10-27_
sam added the mediumepic labels 2026-10-27 13:39:56 +00:00
sam self-assigned this 2026-10-27 13:39:56 +00:00
sam closed this issue 2026-10-27 13:39:56 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1326