Amazon Bedrock model telemetry

Test the integration

Send and verify events with Amazon Bedrock model telemetry

Use Amazon Bedrock model telemetry where your app knows the final result. Collect only the fields you need, then verify a test event before building charts.

1
Choose the outcome
Bedrock model cost attribution
2
Define the contract
provider, model_id, inference_profile, region, feature, and status
3
Log the final result
Record the actual model or inference profile identifier because routing and price can differ.
4
Check the stored event
Exercise a known fixture, then inspect llm_request_completed for one correctly typed terminal row.

Before you start

AWS credentials with the minimum Bedrock model permission
A server-side TELEMETRY_API_KEY
Approved model, region, feature, and prompt-version dimensions

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.

aws-bedrock-install

npm installation

bash

npm install telemetry-sh

1Create one reusable server-side client. Set its timeout and retry limit.
2Log an event when the operation succeeds, fails, retries, or times out.
3Send test events with known results 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.

aws-bedrock

Amazon Bedrock model telemetry event

javascript

import {
  BedrockRuntimeClient,
  ConverseCommand,
} from "@aws-sdk/client-bedrock-runtime";
import telemetry from "telemetry-sh";

const bedrock = new BedrockRuntimeClient({ region: process.env.AWS_REGION });
const startedAt = performance.now();
const modelId = process.env.BEDROCK_MODEL_ID;

try {
  const response = await bedrock.send(new ConverseCommand({
    modelId,
    messages,
  }));

  await telemetry.log("llm_request_completed", {
    provider: "aws_bedrock",
    model: modelId,
    region: process.env.AWS_REGION,
    feature: "research_assistant",
    status: "success",
    latency_ms: Math.round(performance.now() - startedAt),
    input_tokens: response.usage?.inputTokens,
    output_tokens: response.usage?.outputTokens,
    total_tokens: response.usage?.totalTokens,
    finish_reason: response.stopReason,
  });

  return response;
} catch (error) {
  await telemetry.log("llm_request_completed", {
    provider: "aws_bedrock",
    model: modelId,
    region: process.env.AWS_REGION,
    feature: "research_assistant",
    status: "failed",
    latency_ms: Math.round(performance.now() - startedAt),
    error_type: classifyProviderError(error),
  });
  throw error;
}

Event schema

provider, model_id, inference_profile, region, feature, and status

input_tokens, output_tokens, latency_ms, stop_reason, and estimated_cost_usd

attempt, tool_count, error_type, and reviewed business outcome

Check your setup

Checkpoint 1

Record the actual model or inference profile identifier because routing and price can differ.

Checkpoint 2

Use Bedrock response usage rather than estimating tokens from text length.

Checkpoint 3

Keep message content, tool arguments, credentials, and raw model responses outside general 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.

aws-bedrock-verification

Amazon Bedrock model 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.

LLM cost SQL AI time-to-first-token SQL Agent observability use case Bedrock Converse API Bedrock inference APIs

Where to log

Keep the outcome event small and recoverable

This pattern provides

Record the outcome as an event you can query with SQL.
Stable fields for dashboards, alerts, and cross-event correlation.
Test events for checking success, failure, retries, and timeouts.

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

Example event schemas

Check what each event records, when to send it, and which field types it needs. Review the example payload and privacy checklist before using it in production.

AI operations10 fields