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

[bot] Instrument AWS Bedrock AgentCore (876,384 weekly downloads)

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

Maintainer antworten meist innerhalb von 2 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

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

Rechercherichtung

Start by comparing the existing Bedrock integration in js/src/wrappers/bedrock-runtime.ts, js/src/instrumentation/plugins/bedrock-runtime-plugin.ts, js/src/instrumentation/plugins/bedrock-runtime-channels.ts, and js/src/auto-instrumentations/configs/bedrock-runtime.ts. Then inspect js/src/auto-instrumentations/configs/all.ts and the e2e/scenarios/ directory for integration patterns. Done means AgentCore runtime invocation and session lifecycle coverage is registered and exercised by an end-to-end scenario.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

<!-- library-gap-audit: aws-bedrock-agentcore -->

Summary

Amazon Bedrock AgentCore is AWS's dedicated agent-hosting/runtime service (distinct from both the model-invocation Bedrock Runtime and the RAG-oriented Bedrock Agent Runtime). Its official JS/TS client, @aws-sdk/client-bedrock-agentcore, exposes InvokeAgentRuntimeCommand — the core "run an agent and stream its output" execution API — plus session-management commands (e.g. StopRuntimeSessionCommand). None of this is instrumented in this repository.

What's missing

  • InvokeAgentRuntimeCommand (package @aws-sdk/client-bedrock-agentcore) — invokes a deployed AgentCore Runtime agent by ARN, optionally with a session ID for multi-turn continuity, and returns a streaming response (contentStart/contentDelta/contentStop events) with the agent's output. This is the primary agent-execution surface of the service.
  • Session lifecycle commands (e.g. StopRuntimeSessionCommand) that bound an agent-run session.

This is a separate npm package and separate AWS service from what's already instrumented here: js/src/wrappers/bedrock-runtime.ts and js/src/instrumentation/plugins/bedrock-runtime-plugin.ts / bedrock-runtime-channels.ts only cover @aws-sdk/client-bedrock-runtime (raw model invocation, e.g. InvokeModelCommand/ConverseCommand). A repo-wide case-insensitive search for bedrock-agentcore, AgentCore, and InvokeAgentRuntime returns zero matches anywhere in js/src/, js/src/auto-instrumentations/configs/all.ts (the full instrumentation registry), or any e2e/scenarios/* directory.

Weekly downloads

Weekly downloads: 876,384 (as of 2026-09-28; window 2026-09-20–2026-09-26; source https://api.npmjs.org/downloads/point/last-week/@aws-sdk/client-bedrock-agentcore).

Braintrust docs status

not_found — checked both https://www.braintrust.dev/docs/integrations and https://www.braintrust.dev/docs/guides/tracing/integrations. Both pages list "AWS Bedrock" generically but neither mentions "AgentCore," "Bedrock AgentCore," or the AgentCore runtime/session APIs anywhere.

Upstream sources

Local repo files inspected

  • js/src/wrappers/bedrock-runtime.ts, js/src/instrumentation/plugins/bedrock-runtime-plugin.ts, js/src/instrumentation/plugins/bedrock-runtime-channels.ts, js/src/auto-instrumentations/configs/bedrock-runtime.ts — confirm only @aws-sdk/client-bedrock-runtime is covered
  • js/src/auto-instrumentations/configs/all.ts (full instrumentation registry — no AgentCore entry)
  • Repo-wide case-insensitive search for bedrock-agentcore, AgentCore, InvokeAgentRuntime (no matches)
  • e2e/scenarios/ directory listing (no AgentCore-named scenario)
Vorherrschende Sprache
TypeScript
Sterne
28
Forks
14
Ø Merge
2 T. 16 Std.
Gemergte PRs (30 T.)
70

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.