AWS Lambda Structured Event Monitoring

Implementation evidence

AWS Lambda Structured Event Monitoring: from boundary to verified row

Use AWS Lambda Structured Event Monitoring at a controlled application boundary, keep the event contract small, and verify a known outcome before building aggregate views.

1
Choose the outcome
Serverless function reliability
2
Define the contract
function_name, invocation_type, and cold_start
3
Instrument the boundary
Initialize reusable clients outside the handler and emit only one final outcome per invocation.
4
Verify the evidence
Exercise a known fixture, then inspect lambda_invocation_completed for one correctly typed terminal row.

Before you start

Prerequisites and boundaries

A TELEMETRY_API_KEY configured as an encrypted Lambda environment variable
The telemetry-sh client initialized outside the handler when the runtime is reused
An explicit decision about ingestion failure and function completion

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-lambda-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.

aws-lambda

AWS Lambda Structured Event Monitoring event

javascript

let coldStart = true;

export const handler = async (event, context) => {
  const startedAt = performance.now();
  const result = await processBatch(event);

  await telemetry.log("lambda_invocation_completed", {
    function_name: context.functionName,
    aws_request_id: context.awsRequestId,
    status: "success",
    duration_ms: Math.round(performance.now() - startedAt),
    item_count: result.itemCount,
    cold_start: coldStart,
  });

  coldStart = false;
  return result;
};

Event contract

function_name, invocation_type, and cold_start

status, duration_ms, attempt, and error_type

aws_request_id, release, and safe workflow identifiers

Implementation checkpoints

Checkpoint 1

Initialize reusable clients outside the handler and emit only one final outcome per invocation.

Checkpoint 2

Await ingestion before returning unless a tested delivery mechanism handles flushing.

Checkpoint 3

Do not log the raw Lambda event because it may contain credentials or customer payloads.

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-lambda-verification

AWS Lambda Structured Event Monitoring verification query

sql

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

Background job monitoring Missing heartbeat SQL AWS Lambda Node.js logging

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.

Async reliability11 fields