Archie's OTLP traces carry only gRPC, HTTP and gen_ai attributes. No span names the task, workflow, step or attempt it belongs to, so the trace store can't answer which workflow or step is slow or failing, which is what the traces are being kept for.
Done when the spans for a task's run and its steps carry task id, workflow, step and attempt attributes (and the model and token counts on agent calls), so a trace search or span-metrics dimension can group by them.
Archie's OTLP traces carry only gRPC, HTTP and gen_ai attributes. No span names the task, workflow, step or attempt it belongs to, so the trace store can't answer which workflow or step is slow or failing, which is what the traces are being kept for.
Done when the spans for a task's run and its steps carry task id, workflow, step and attempt attributes (and the model and token counts on agent calls), so a trace search or span-metrics dimension can group by them.
Workflow runs now emit spans (internal/domain/workflow/trace.go, commit 98fb9dfd). workflow.run: archie.task.id, archie.workflow, archie.attempt, archie.outcome (task status; parked is recorded as an error, empty means interrupted). workflow.step per top-level step: same plus archie.step, outcome succeeded/failed/skipped, errors recorded. agent.run per agent call: same plus gen_ai.request.model, gen_ai.usage.input_tokens, gen_ai.usage.output_tokens. Spans use the existing global provider and ctx propagation; they are produced in the worker and reach the backend through the existing container exporter.
Workflow runs now emit spans (internal/domain/workflow/trace.go, commit 98fb9dfd). workflow.run: archie.task.id, archie.workflow, archie.attempt, archie.outcome (task status; parked is recorded as an error, empty means interrupted). workflow.step per top-level step: same plus archie.step, outcome succeeded/failed/skipped, errors recorded. agent.run per agent call: same plus gen_ai.request.model, gen_ai.usage.input_tokens, gen_ai.usage.output_tokens. Spans use the existing global provider and ctx propagation; they are produced in the worker and reach the backend through the existing container exporter.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Archie's OTLP traces carry only gRPC, HTTP and gen_ai attributes. No span names the task, workflow, step or attempt it belongs to, so the trace store can't answer which workflow or step is slow or failing, which is what the traces are being kept for.
Done when the spans for a task's run and its steps carry task id, workflow, step and attempt attributes (and the model and token counts on agent calls), so a trace search or span-metrics dimension can group by them.
Workflow runs now emit spans (internal/domain/workflow/trace.go, commit
98fb9dfd). workflow.run: archie.task.id, archie.workflow, archie.attempt, archie.outcome (task status; parked is recorded as an error, empty means interrupted). workflow.step per top-level step: same plus archie.step, outcome succeeded/failed/skipped, errors recorded. agent.run per agent call: same plus gen_ai.request.model, gen_ai.usage.input_tokens, gen_ai.usage.output_tokens. Spans use the existing global provider and ctx propagation; they are produced in the worker and reach the backend through the existing container exporter.