Correlation identifiers
Span vocabulary
harmonia.stage.executeharmonia.agent.invokeharmonia.agent.delegateharmonia.model.generateharmonia.output.validate
Durable agent activity
The Monitoring Agents view reads structured activity from the existing tenant-scoped DynamoDB job event stream. Each record identifies its kind (handoff, tool_call, retry, or failure), status, responsible role, safe public message, operation, and trace. Handoffs identify both roles; retries and failures carry a stable code, category, retryability, and bounded attempt counts.
Events are written only after the corresponding typed artifact passes deterministic validation and persistence. They describe what happened but cannot advance a stage, approve content, or authorize an effect.
Native Strands signals
WhenHARMONIA_TELEMETRY_ENABLED=true, OTEL_EXPORTER_OTLP_ENDPOINT is required. Fargate task sidecars receive OTLP/gRPC on loopback and export metadata-only traces using task IAM roles. CloudWatch Logs receives application stdout and collector logs. The AgentCore role has the managed runtime’s logging, tracing, and metrics permissions; actual export remains an authenticated rehearsal check.
Python resource attributes include service name, AWS region, release, and environment. HARMONIA_TELEMETRY_SAMPLE_RATE controls parent-based sampling. Content capture is disabled before inference. Native provider instrumentation and application event projections remain separate from execution authority.
Operator activity explorer
Open Monitoring → Agent activity to query the safe DynamoDB projection. It supports:- log, trace, and metric modes;
- agent, stage, outcome, severity, model, tool, job, trace, time-window, and free-text filters;
- opaque forward cursors with previous/next navigation;
- nested parent/child spans by trace ID;
- per-agent latency, invocation, failure, token, inference-call, and tool-call summaries for the current filtered page.
retentionEpochSeconds; the DynamoDB table enables TTL on ttlEpochSeconds, which the repository projects from validated records.
Privacy boundary
- Recorded
- Excluded
IDs, stages, roles, handoff endpoints, tool names, model names, counts, attempt numbers, durations, policy versions, outcomes, safe error codes/categories, and timestamps.
Local trace-contract tests prove propagation and redaction behavior. A judge-facing claim still requires authenticated CloudWatch traces or log exports correlated with the same DynamoDB records.
