LangGraph Agent Observability

Implementation evidence

LangGraph Agent Observability: from boundary to verified row

Use LangGraph Agent Observability at a controlled application boundary, keep the event contract small, and verify a known outcome before building aggregate views.

1
Choose the outcome
Stateful agent monitoring
2
Define the contract
run_id, graph_name, node_name, and status
3
Instrument the boundary
Emit node-level events from a controlled wrapper or callback and one terminal run event after graph invocation.
4
Verify the evidence
Exercise a known fixture, then inspect agent_run_completed for one correctly typed terminal row.

Before you start

Prerequisites and boundaries

@langchain/langgraph and @langchain/core
A stable run ID shared across graph events
A server-side TELEMETRY_API_KEY

Delivery setup

Install and initialize server-side

Import telemetry-sh in server-only code and initialize it once with process.env.TELEMETRY_API_KEY. Keep ingestion credentials out of browser bundles, client-visible environment variables, source control, logs, and exception messages.

langgraph-install

npm installation

bash

npm install telemetry-sh

1Prepare one reusable server-side delivery client with bounded network behavior.
2Add the outcome event at the success, failure, retry, or timeout boundary.
3Send controlled fixtures and inspect the stored rows before enabling an alert.

Snippet

Start with one structured event

Add this shape where the workflow completes, fails, or retries. Then build the dashboard from real fields.

langgraph

LangGraph Agent Observability event

javascript

const runId = crypto.randomUUID();
const startedAt = performance.now();
const result = await graph.invoke(
  { messages },
  { configurable: { thread_id: runId } }
);

await telemetry.log("agent_run_completed", {
  run_id: runId,
  graph_name: "support_agent",
  status: "success",
  message_count: result.messages.length,
  human_handoff: false,
  duration_ms: Math.round(performance.now() - startedAt),
  release: process.env.APP_RELEASE,
});

Event contract

run_id, graph_name, node_name, and status

tool_name, attempt, latency_ms, and error_type

checkpoint_count, human_handoff, reviewer_outcome, and release

Implementation checkpoints

Checkpoint 1

Emit node-level events from a controlled wrapper or callback and one terminal run event after graph invocation.

Checkpoint 2

Keep run ID stable across resumed checkpoints while recording each execution attempt separately.

Checkpoint 3

Do not send graph state, messages, checkpoint contents, or tool arguments wholesale.

Verification

Prove the event arrived

Run this after exercising known success and failure cases. Replace the fallback table name if your final event contract differs from the snippet.

langgraph-verification

LangGraph Agent Observability verification query

sql

SELECT *
FROM agent_run_completed
ORDER BY timestamp_utc DESC
LIMIT 20;

Confirm one terminal row per logical outcome, with the expected status, identifiers, units, and UTC time.

Inspect the inferred schema and verify that retries do not change field types or generate a new logical event ID.

Search the stored fields for credentials, raw payloads, prompts, private content, and unbounded error messages.

Exercise a provider timeout, ingestion rejection, and process shutdown before treating the dashboard as complete.

Implementation references

Review the event contract, data-safety guidance, and upstream primary documentation before enabling a new production path.

Nested tool-event SQL Agent quality SQL Official LangGraph JavaScript overview

Production boundary

Keep the outcome event small and recoverable

This pattern provides

A bounded, SQL-ready outcome beside the upstream workflow.
Stable fields for dashboards, alerts, and cross-event correlation.
A fixture-driven path for validating success, failure, retry, and timeout behavior.

This pattern does not provide

An OTLP exporter, automatic collection pipeline, or replacement for detailed traces and diagnostic logs.
Exactly-once delivery merely because the payload contains an event ID.
Permission to collect raw provider payloads, user content, credentials, or regulated data.

Delivery and idempotency Batching and shutdown Troubleshoot ingestion

Event schema starting points

Review the row grain, emit boundary, required types, privacy classes, example payload, and validation checklist before adapting a query or snippet to production.

AI operations10 fields