Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#2,526 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
65/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
aws, typescript
Ambito
observability

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

<!-- 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)
Lingua principale
TypeScript
Stelle
28
Fork
14
Merge medio
2g 16h
PR unite (30g)
70

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di braintrustdata/braintrust-sdk-javascript

Tutte le issue di braintrustdata/braintrust-sdk-javascript

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.