Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

[bot] Instrument AWS Bedrock Agent Runtime (2,532,884 weekly downloads)

Geschlossen
  • Stimmt etwas nicht?
#2,603 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
52/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
aws, typescript
Bereich
backend, observability

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

typescript

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)
Vorherrschende Sprache
TypeScript
Sterne
29
Forks
21
Ø Merge
1 T. 15 Std.
Gemergte PRs (30 T.)
76

Entwicklungsumgebung

  • Enthält ein Dockerfile oder eine Docker-Compose-Datei
  • Keine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus braintrustdata/braintrust-sdk-javascript

Alle Issues in braintrustdata/braintrust-sdk-javascript

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.