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

[bot] aws-sdk-bedrockruntime gem not instrumented

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

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
aws, ruby
Área
ai, backend-api-design, observability

Línea de trabajo

Empieza leyendo las integraciones existentes en lib/braintrust/contrib/, especialmente openai/ y anthropic/, y después inspecciona lib/braintrust/contrib.rb, Appraisals y braintrust.gemspec. La tarea estará terminada cuando la integración de AWS Bedrock Runtime esté registrada y cubra las APIs converse, streaming, invoke-model y async con las entradas, los metadatos, el uso y las salidas indicados.

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

Descripción

Summary

The aws-sdk-bedrockruntime gem is the official AWS SDK for invoking foundation models on Amazon Bedrock. With ~16.6M downloads, continuous releases (v1.75.0, April 2026), and a standardized converse/converse_stream API surface across all Bedrock-hosted models (Claude, Titan, Llama, Mistral, Cohere, etc.), it is not instrumented by this SDK.

The SDK instruments standalone provider clients for OpenAI (openai, ruby-openai) and Anthropic (anthropic), but has no instrumentation for the AWS Bedrock Runtime client, which is one of the most widely used ways to invoke generative AI models in Ruby production environments.

What is missing

No instrumentation exists for any aws-sdk-bedrockruntime execution surface. Key APIs that should be instrumented:

Converse API (unified chat)
  • client.converse(...) — Unified chat API with structured messages, system prompts, tool use (tool_config, tool_use, tool_result), inference config (temperature, max_tokens, top_p, stop_sequences), and guardrails. Returns structured ConverseResponse with usage metrics (input/output tokens), stop reason, and model-specific metadata. Works identically across all Bedrock-hosted models.
  • client.converse_stream(...) — Streaming variant with event-based output (content_block_delta, content_block_start, content_block_stop, message_start, message_stop, metadata). Includes token usage and latency metrics in the stream metadata event.
Invoke Model API (raw model invocation)
  • client.invoke_model(...) — Raw model invocation with provider-specific request body. Returns raw response body. Used for embeddings (e.g., Titan Embeddings, Cohere Embed) and other model-specific APIs.
  • client.invoke_model_with_response_stream(...) — Streaming variant of raw invocation.
Async Invoke API
  • client.start_async_invoke(...) — Asynchronous model invocation for long-running tasks.
  • client.get_async_invoke(...) — Check status of async invocation.
Expected instrumentation

The converse/converse_stream APIs are the primary instrumentation target due to their standardized request/response shapes:

Converse spans should capture:

  • Input: messages array, system prompts, tool configuration
  • Metadata: model_id, inference_config (temperature, max_tokens, top_p, stop_sequences), guardrail_config, additional_model_request_fields, provider, endpoint
  • Metrics: usage (input_tokens, output_tokens, total_tokens), latency metrics from stream metadata
  • Output: response messages, stop_reason, additional_model_response_fields

Invoke model spans (for embeddings) should capture:

  • Input: request body (model-specific)
  • Metadata: model_id, content_type, accept, provider
  • Output: response body metadata

Braintrust docs status

supported — Braintrust lists AWS Bedrock as a supported AI provider at https://www.braintrust.dev/docs. The Braintrust proxy supports Bedrock routing. However, there is no Ruby SDK auto-instrumentation for the aws-sdk-bedrockruntime gem — the SDK integrations page at https://www.braintrust.dev/docs/integrations/sdk-integrations does not list it as a supported Ruby library.

Upstream sources

Local repo files inspected

  • lib/braintrust/contrib/ — contains only openai/, ruby_openai/, ruby_llm/, anthropic/, and rails/ directories. No bedrock or aws directory.
  • lib/braintrust/contrib.rb — registers only 4 integrations: OpenAI, RubyOpenAI, RubyLLM, Anthropic. No Bedrock integration.
  • Appraisals — no appraisal scenarios for aws-sdk-bedrockruntime
  • braintrust.gemspec — no mention of aws or bedrock
  • Grep for bedrock across entire codebase returns zero matches
Lenguaje dominante
Ruby
Estrellas
9
Forks
10
Merge medio
22 h 10 min
PR fusionados (30 d)
6

Preparar el entorno

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

Todos los issues de braintrustdata/braintrust-sdk-ruby

Issues similares

Más issues de Ruby

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.