Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[bot] Instrument AWS Bedrock Agent Runtime (2,630,075 weekly downloads)

Abierto
  • ¿Algo no está bien?
#2,603 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
52/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
aws, typescript
Área
backend, observability

Línea de trabajo

Start by reading js/src/auto-instrumentations/configs/all.ts and js/src/span-origin.ts, then compare the existing Bedrock Runtime instrumentation with the AWS SDK commands named in the issue. The issue also identifies e2e/scenarios/ as the location for an instrumentation scenario. Done means direct use of Bedrock Agent Runtime commands is traced and the new instrumentation is registered.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Summary

@aws-sdk/client-bedrock-agent-runtime is AWS's official SDK for invoking pre-built Amazon Bedrock Agents and Bedrock Flows — a distinct agent-execution surface from the already-instrumented Bedrock Runtime client (@aws-sdk/client-bedrock-runtime, which only covers direct model Converse/InvokeModel calls). InvokeAgentCommand, InvokeFlowCommand, and InvokeInlineAgentCommand run an agent's multi-step reasoning/tool-use loop server-side and stream back the trace, but none of this is captured as spans today.

What's missing

  • BedrockAgentRuntimeClient + InvokeAgentCommand — runs a configured Bedrock Agent against a prompt/session, optionally streaming the agent's reasoning trace (enableTrace) and tool invocations.
  • InvokeFlowCommand — executes a Bedrock Flow (a graph of prompt/tool/code nodes) and streams per-node outputs.
  • InvokeInlineAgentCommand — runs an ad hoc (not pre-registered) agent definition.

This is a different package/API surface than the AWS Bedrock Agent Runtime client that Strands Agents SDK optionally depends on (@aws-sdk/client-bedrock-agent-runtime appears only as an optional peer dependency of @strands-agents/sdk for Strands's own Bedrock backend — see e2e/scenarios/strands-agent-sdk-instrumentation/pnpm-lock.yaml). A caller using this AWS SDK client directly (not through Strands) gets zero tracing.

Weekly downloads

Weekly downloads: 2,630,075 (as of 2026-10-12; window 2026-10-04–2026-10-10; source https://api.npmjs.org/downloads/point/last-week/@aws-sdk/client-bedrock-agent-runtime)

Braintrust docs status

not_found — Checked https://www.braintrust.dev/docs/integrations/ai-providers/bedrock, which documents only the Bedrock Runtime client (ConverseCommand, ConverseStreamCommand, InvokeModelCommand, InvokeModelWithResponseStreamCommand via wrapBedrockRuntime/the auto-instrumentation hook) and the @anthropic-ai/bedrock-sdk path. Also checked https://www.braintrust.dev/docs/guides/traces/integrations (full tracing/agent-framework integration list) — no mention of Bedrock Agents, InvokeAgent, or Bedrock Flows anywhere in Braintrust's docs.

Upstream sources

Local repo files inspected

  • js/src/auto-instrumentations/configs/all.ts (full instrumentation registry — only bedrockRuntimeConfigs for AWS Bedrock, no Bedrock Agent Runtime entry)
  • js/src/span-origin.ts (INSTRUMENTATION_NAMES — only BEDROCK_RUNTIME, no Bedrock Agent entry)
  • Repo-wide case-insensitive search for bedrock-agent-runtime/BedrockAgentRuntime/InvokeAgent/InvokeFlow (only matches: binary provider-response cassette blobs with coincidental byte sequences, and @aws-sdk/client-bedrock-agent-runtime listed as an optional peer dependency in e2e/scenarios/strands-agent-sdk-instrumentation/pnpm-lock.yaml — i.e. Strands's own optional Bedrock backend, not direct instrumentation of this client)
  • e2e/scenarios/ directory listing (no Bedrock-Agent-named scenario)
Lenguaje dominante
TypeScript
Estrellas
29
Forks
16
Merge medio
1 d 16 h
PR fusionados (30 d)
64

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de braintrustdata/braintrust-sdk-javascript

Todos los issues de braintrustdata/braintrust-sdk-javascript

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.