Anthropic Claude API Telemetry

Implementation evidence

Anthropic Claude API Telemetry: from boundary to verified row

Use Anthropic Claude API Telemetry at a controlled application boundary, keep the event contract small, and verify a known outcome before building aggregate views.

1
Choose the outcome
Claude API cost analytics
2
Define the contract
provider, model, feature, and status
3
Instrument the boundary
Read the model from the API response and configuration instead of hard-coding a soon-to-age model identifier in analytics.
4
Verify the evidence
Exercise a known fixture, then inspect llm_request_completed for one correctly typed terminal row.

Before you start

Prerequisites and boundaries

The official Anthropic TypeScript SDK configured server-side
A server-side TELEMETRY_API_KEY
A product workflow and reviewed outcome definition

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.

anthropic-sdk-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.

anthropic-sdk

Anthropic Claude API Telemetry event

javascript

const startedAt = performance.now();
const message = await anthropic.messages.create({
  model: process.env.ANTHROPIC_MODEL,
  max_tokens: 1024,
  messages,
});

await telemetry.log("llm_request_completed", {
  provider: "anthropic",
  model: message.model,
  feature: "support_reply",
  status: "success",
  stop_reason: message.stop_reason,
  input_tokens: message.usage.input_tokens,
  output_tokens: message.usage.output_tokens,
  latency_ms: Math.round(performance.now() - startedAt),
  prompt_version: "support-v3",
  release: process.env.APP_RELEASE,
});

Event contract

provider, model, feature, and status

input_tokens, output_tokens, latency_ms, and stop_reason

run_id, prompt_version, reviewer_outcome, and release

Implementation checkpoints

Checkpoint 1

Read the model from the API response and configuration instead of hard-coding a soon-to-age model identifier in analytics.

Checkpoint 2

Log the request outcome after usage and stop reason are known, and log failures with a controlled error type.

Checkpoint 3

Keep raw prompts, completions, API keys, and tool payloads out of telemetry.

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.

anthropic-sdk-verification

Anthropic Claude API Telemetry verification query

sql

SELECT *
FROM llm_request_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.

AI cost guide Agent quality SQL Official Claude client SDKs Claude API reference

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