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

[bot] Instrument aws-sdk-bedrockagentcore (43K weekly downloads)

Aperta
  • Qualcosa non va?
#205 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
aws, ruby
Ambito
ai, backend-api-design, observability-sre

Direzione di ricerca

Inizia leggendo lib/braintrust/contrib.rb e le directory di integrazione esistenti sotto lib/braintrust/contrib/, poi esamina i punti di ingresso di Aws::BedrockAgentCore::Client nella documentazione API collegata. Controlla Appraisals e braintrust.gemspec per la configurazione delle dipendenze e dei test. Il lavoro è completato quando le superfici di esecuzione di AgentCore, inclusi invoke_agent_runtime e le chiamate agli strumenti correlate, sono rappresentate nell'integrazione di tracing dell'SDK.

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

Descrizione

Summary

The aws-sdk-bedrockagentcore gem is the official, auto-generated AWS SDK client for Amazon Bedrock AgentCore — AWS's newer (2025-era) managed runtime for deploying and operating AI agents (and non-Bedrock, framework-agnostic agents, e.g. built with LangGraph/CrewAI/Strands) at scale. It exposes a distinct agent-run execution API (invoke_agent_runtime) separate from both raw model invocation and the classic Agents-for-Bedrock API, and is not instrumented by this SDK.

This is a separate gem/service from both aws-sdk-bedrockruntime (tracked in #152 — raw converse/invoke_model calls) and aws-sdk-bedrockagentruntime (classic Bedrock Agents invoke_agent, a distinct gem/API from this one). AgentCore Runtime is purpose-built to host and invoke arbitrary agent code (any framework, any model provider) as a managed session-based execution boundary — a clear, high-value agent-run tracing surface for a Ruby SDK whose stated purpose includes agent-execution observability.

What is missing

No instrumentation exists for any aws-sdk-bedrockagentcore execution surface. Key API:

  • client.invoke_agent_runtime(agent_runtime_arn:, runtime_session_id:, payload:, qualifier:, content_type:, accept:, mcp_session_id:, mcp_protocol_version:, ...) — Invokes a deployed AgentCore Runtime (the hosted agent) for one turn within a session, returning the agent's response payload (supports both buffered and streaming/SSE responses). This is the primary execution entry point for any agent hosted on AgentCore, regardless of the underlying agent framework or model provider — the direct agent-run analog to this SDK's existing model-call instrumentation.
  • Related generative/agent surfaces on the same client: invoke_code_interpreter (executes code in an AgentCore-managed sandbox) and invoke_browser (drives an AgentCore-managed browser tool) — both are tool-execution calls typically made during an agent run.
What a span should capture
  • Input: payload (the agent request body), runtime_session_id, agent_runtime_arn, qualifier (endpoint/version)
  • Metadata: provider (aws-bedrock-agentcore), content_type, mcp_session_id/mcp_protocol_version when present (AgentCore Runtime supports exposing agents as MCP servers)
  • Output: response payload, content_type/accept of the response, streaming status
  • Child spans: invoke_code_interpreter/invoke_browser calls made mid-run, mirroring how this SDK already models tool-call child spans for other integrations

Weekly downloads

43K (as of 2026-08-10; https://clickgems.clickhouse.com/dashboard/aws-sdk-bedrockagentcore) — ClickGems reports Last day / Last week / Last month / Total downloads sourced from RubyGems.org's public download dataset; RubyGems.org itself only exposes total and per-version download counts, not a weekly figure, so ClickGems was used as the directly-reported weekly stat.

Additional signal: current version 1.46.0 (per https://rubygems.org/api/v1/gems/aws-sdk-bedrockagentcore.json, checked 2026-08-10), part of the AWS SDK for Ruby's continuous auto-generated release train; total downloads 2,273,730 — notably high relative to the service's 2025 launch, indicating fast-growing adoption.

Braintrust docs status

not_found — Checked https://www.braintrust.dev/docs/integrations/sdk-integrations (Ruby-relevant tracing integrations list only OpenAI, Anthropic, Ruby LLM/ruby-openai; the separate "Agent frameworks" section lists OpenAI Agents SDK, Claude Agent SDK, LangGraph, CrewAI, AutoGen, Google ADK, Strands Agents SDK, Mastra, Pydantic AI, etc. — no Amazon Bedrock AgentCore entry) and https://www.braintrust.dev/docs generally. No mention of Bedrock AgentCore, BedrockAgentCore, or invoke_agent_runtime anywhere in Braintrust's documentation.

Upstream sources

Braintrust docs sources checked

Local repo files inspected

  • lib/braintrust/contrib.rb — registers only 4 integrations: OpenAI, RubyOpenAI, RubyLLM, Anthropic. No AWS/Bedrock integration of any kind.
  • lib/braintrust/contrib/ — contains only openai/, ruby_openai/, ruby_llm/, anthropic/, and rails/ directories. No bedrock or aws directory.
  • Appraisals — no appraisal scenarios for aws-sdk-bedrockagentcore or any AWS gem
  • braintrust.gemspec — no mention of aws or bedrock
  • Grep for bedrock, Bedrock, AgentCore, invoke_agent_runtime across lib/braintrust/ returns zero matches
  • Confirmed issue #152 (aws-sdk-bedrockruntime-not-instrumented) covers only the separate Aws::BedrockRuntime::Client (converse/invoke_model); searched all 46 currently-open issues and found no existing issue mentioning BedrockAgent or AgentCore, so this is a distinct, non-duplicate gap from both #152 and the newly-filed aws-sdk-bedrockagentruntime gap.
Lingua principale
Ruby
Stelle
9
Fork
10
Merge medio
3g 43m
PR unite (30g)
9

Preparare l'ambiente

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-ruby

Tutte le issue di braintrustdata/braintrust-sdk-ruby

Issue simili

Altre issue su Ruby

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.