Support batch insights in BatchEvaluationRunner

Aberta
#678 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
45/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
aws, python

Direção de pesquisa

Examine the BatchEvaluationRunner class to understand its current dataset-based workflow. Review the StartBatchEvaluation API and the listed Builtin.Insight types (FailureAnalysis, UserIntent, ExecutionSummary) to understand the constraints. Determine if insights can be integrated into the existing runner or require a separate component. Check for any existing tests related to batch evaluation or insights.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

enhancement

BatchEvaluationRunner does not expose the batch insights workflow.

Requested behavior

Support requesting batch insights through BatchEvaluationRunner, with job polling and access to the resulting insights. The original report identifies these StartBatchEvaluation insights:

  • Builtin.Insight.FailureAnalysis
  • Builtin.Insight.UserIntent
  • Builtin.Insight.ExecutionSummary

The workflow should enforce the API constraint that insights and evaluators cannot be requested in the same job.

Why this matters

The reporter uses insights to cluster failures and identify root causes that can be addressed through prompt changes. Without SDK support, the evaluation improvement workflow requires custom orchestration outside BatchEvaluationRunner.

Open design question

Confirm whether the runner's dataset-based workflow is compatible with insights and which inputs are supported. Use that finding to determine how to expose insights through the runner, or whether a separate insights runner is needed. This compatibility question remains unresolved.

Original report environment: bedrock-agentcore 1.23.0, Python 3.13, us-west-2.

Linguagem predominante
Python
Estrelas
786
Forks
163
Merge médio
4h
PRs com merge (30d)
22

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de aws/bedrock-agentcore-sdk-python

Todas as issues de aws/bedrock-agentcore-sdk-python

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.