Skip to content

Track adoption of long-running agent invokes #10237

Description

@m5i-work

Problem

azd ai agent invoke has a --long-running option (and optional --no-wait), but extension usage telemetry does not distinguish long-running invocations from regular remote invokes. We cannot measure adoption or compare the two modes.

Proposed change

Emit one best-effort agent.invoke.selected extension usage event after resolving a remote invoke target and before the invoke request. Project-backed routes must resolve a hosted agent; explicit --agent-endpoint routes have no project kind to inspect. Resolution may authenticate or probe a brownfield agent first. Include only:

  • agent.invoke.protocol: the resolved invocable protocol
  • agent.invoke.long_running: whether --long-running was selected
  • agent.invoke.no_wait: whether --no-wait was selected

This measures selected remote routes, not all attempts, service acceptance, or success. Exclude local and non-hosted project invokes; do not emit names, IDs, endpoints, prompts, or raw errors. Keep the event schema, public telemetry reference, coverage matrix, and tests in sync.

Implementation: #10236

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/telemetryTelemetry, tracing, observabilityengineering itemInternal engineering work itemext-agentsazure.ai.agents extension

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions