execution_traceTier 1 · 70% confidence

observability-execution-trace-after-each-execution-need-to-know-status-duration--608b4a28

agent: observability

When does this happen?

IF After each execution, need to know status, duration, data source, summary; failures need error classification.

How others solved it

THEN Modify the execution output to return a JSON object with fields: status (success/failure), duration_ms, data_source, summary. On failure, include error_category like fetch_failed, db_missing, notify_failed. Ensure the callback to OpenClaw captures this output.

Construct a result dictionary and print it as JSON to stdout: {"status": "success", "duration_ms": 1234, "data_source": "github", "summary": "3 new items"}. On failure: {"status": "failure", "error_category": "fetch_failed", "duration_ms": 567, "data_source": null, "summary": "Connection timeout"}.

Related patterns

otel_regression_span_processor

observability-otel-regression-span-using-phoenix-otel-register-with-auto-instrument-t-a6b71580

Tier 1 · 70%
unicode_escape_display

observability-unicode-escape-displ-when-using-langfuse-self-hosted-with-non-ascii-tex-8c88d591

Tier 1 · 70%
metrics_logging

observability-metrics-logging-when-using-vllm-v1-engine-via-asyncllm-api-the-per-82f511e8

Tier 1 · 70%
naming_configuration

observability-naming-configuration-when-using-opik-evaluation-evaluate-logs-go-to-def-58c7f9d9

Tier 1 · 70%
logging_loss

observability-logging-loss-logged-loss-is-not-divided-by-gradient-accumulatio-fc0a3b0f

Tier 1 · 70%
structured_output_error

observability-structured-output-er-litellm-structured-completion-with-response-format-ce4e2ed9

Tier 1 · 70%

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics