Search historical hosted-agent logs by time, severity, and text

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

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
azure, github, go
Área
cli, observability

Línea de trabajo

Read the released monitor implementation at cli/azd/extensions/azure.ai.agents/internal/cmd/monitor.go and the linked hosted-agent tracing setup to understand current log sources and permissions. The issue says an experience spec must first settle command placement, filter semantics, output, and data sources, so implementation needs design work before a code entry point is clear. Done means the specified workflow covers retained data limits, filtering, isolation, output, failures, help, and examples.

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

Descripción

area/telemetry enhancement ext-agents ext-foundry

Customer problem

An operator needs to answer questions such as "Which errors occurred for this deployed agent in the last hour?" or "Where did this timeout appear across sessions?" They should not need the original application checkout, a live session, or a hand-written telemetry query for these common investigations.

Current behavior

In released azure.ai.agents 1.1.0, azd ai agent monitor targets one hosted-agent session and supports console/system selection, a trailing line count of 1-300, and following new entries. It has no time-window, severity, or search-pattern filters.

Existing example:

azd ai agent monitor support --session-id "<session-id>" --type console --tail 100

Azure CLI and Application Insights/KQL can query retained application telemetry today. That workaround requires identifying the telemetry resource, applying the right agent filter, and carrying context between tools. Application Insights application logs are not guaranteed to contain every hosted-agent console line or system event.

Requested experience

Add an agent-scoped historical log-query workflow to the Agents extension, using available retained telemetry rather than treating a live session tail as a historical search.

Illustrative command shape, not an available command:

azd ai agent logs query --project-endpoint "$Project" --agent-name support --since 1h --level error --output json --no-prompt

The experience spec should settle command placement, time and text-filter semantics, output, and supported data sources before implementation.

Acceptance criteria

  • Query a bounded relative or absolute time window for a known remote agent, with severity and text filtering and optional version/session narrowing where the data supports them.
  • Support investigations across retained sessions without requiring azure.yaml or a currently running session.
  • Carry the selected Foundry project and deployed-agent context into the query. Resolve connected telemetry where possible and provide explicit, actionable guidance when extra configuration is needed.
  • Identify supported retained data sources and coverage. Do not assume the Application Insights traces table contains all console/system logs or promise reconstruction of data that was never collected.
  • Distinguish no matching records from missing telemetry configuration, unsupported data sources, and access failures. Explain relevant retention/sampling limits.
  • Provide useful terminal output and stable JSON with timestamps and available agent/session/trace correlation. Define result limits and pagination.
  • Preserve current monitor/follow behavior, reject incompatible selectors, and cover cross-agent isolation, time/filter behavior, and non-interactive failures. Update help and examples.

Related work and evidence

Lenguaje dominante
Go
Estrellas
573
Forks
387
Merge medio
2 d 20 h
PR fusionados (30 d)
196

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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 Azure/azure-dev

Todos los issues de Azure/azure-dev

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.