go-lambda-observability-otel

To add OpenTelemetry tracing and metrics to Go AWS Lambda, you set up centralized tracer and meter providers, instrument HTTP API and SQS adapters, and propagate context across hexagonal boundaries without leaking backend concerns into domain code.

Preserving request correlation across hexagonal boundaries in Go Lambda services requires propagating OpenTelemetry context through inbound adapters and application use cases, ensuring trace spans stay linked without leaking backend-specific telemetry concerns into domain code.

Yes, you can use OpenTelemetry to instrument AWS SDK v2 outbound calls in Go Lambda. The Skill provides safe instrumentation for outbound dependencies, adding meaningful spans and metrics around these calls while keeping signal names stable and low-cardinality.

The best way to bootstrap OpenTelemetry providers for Go Lambda microservices is centralized setup in one place for reusable execution environments, establishing tracer and meter providers that apply consistently across inbound adapters, use cases, and AWS SDK v2 calls.

To keep OpenTelemetry spans low-cardinality when instrumenting SQS processing in Go, use stable signal names and avoid injecting sensitive payloads or high-cardinality message attributes into span or metric data during boundary instrumentation.

No, OpenTelemetry instrumentation does not leak backend-specific concerns into Go domain code when applied correctly. This Skill ensures portable observability by centralizing provider setup and instrumenting boundaries, keeping domain logic clean and telemetry concerns separated.