Skip to content

[Epic] Redesign azd telemetry: retention, user surfaces, cohorts, and dashboards #9385

Description

@hemarina

Goal

Improve azd telemetry so we can make design decisions from evidence, and grow adoption.

Our cooked tables and Power BI dashboards were built around templates, provision, and deploy. That no longer matches how azd is used:

  • Most traffic now comes from CI/CD and agents, but MAU counts local/desktop only, so our headline number describes a shrinking slice of our users.
  • Users increasingly start from a custom template or their own codebase, so the template pivot our dashboards depend on is going stale.
  • New features ship with no way to see whether anyone uses them, because reporting is provision/deploy shaped.
  • Raw events expire after 90 days, so no long-horizon question can be answered.
  • When telemetry breaks we find out late, by noticing a chart looks wrong.

This epic tracks the work to close those gaps.

Workstreams

Compliance — unblocks everything else

Data foundation

Dashboards

Analysis and reliability

Related

Kusto functions and Power BI models live in the internal azure-dev-tools repo under product-telemetry/azd/.

Metadata

Metadata

Labels

area/telemetryTelemetry, tracing, observabilityepicLarge multi-issue initiative

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions