# Query Catalog (Generated)

This file is generated from JSON query definitions.

- Canonical source: `www/config/queries.json`
- Generator: `scripts/generate-doc-query-catalog.js`

Total queries: 305

Calculated column legend:

- `Yes` = KQL combines multiple query/result sets or combines multiple values into a derived metric (for example `join`, `union`, arithmetic formulas, or `iff/case` formulas).
- `No` = KQL does not clearly combine result sets/values and is primarily direct retrieval, filtering, grouping, or single-metric aggregation.

| Query ID | Name | Category | Calculated | Canonical Status | Events Used | Non-Canon Info | Description |
| --- | --- | --- | --- | --- | --- | --- | --- |
| aiep-4xx-trend | AI Endpoint Client Error (4xx) Trend | API Status — AI Endpoint | Yes | Canonical | table:requests | — | Client-side 4xx for AI Endpoint broken out by class (401 auth, 403 forbidden, 404 not-found, 429 throttled, other) over time. Informational only - drives an elevated-client-error note and a 401-spike flag, never the health pill. |
| aiep-dep-regression | AI Endpoint Dependency Latency Regression | API Status — AI Endpoint | Yes | Canonical | table:dependencies | — | Downstream dependencies of AI Endpoint whose P95 got worse (current vs prior half-window). Two-pass join on target with a >=200 successful-call floor (CurOK) that structurally excludes prod-named fail-only probe rows. Empty result is a positive signal (no downstream regression), not an error. Does not feed status. |
| aiep-endpoint-breakdown | AI Endpoint Breakdown | API Status — AI Endpoint | No | Canonical | table:requests | — | Top operations by volume with per-operation 5xx, 4xx and P95 latency. |
| aiep-health-summary | AI Endpoint Health Summary | API Status — AI Endpoint | Yes | Canonical | table:requests | — | Single-row health: total requests, 5xx server-error rate, 4xx client-error rate, and latency percentiles. Drives the status tile. |
| aiep-latency-regression | AI Endpoint Latency Regression | API Status — AI Endpoint | Yes | Canonical | table:requests | — | Period-over-period P50/P95/P99 for AI Endpoint: current half-window vs prior half. Drives the tile latency-delta chip and the baseline-sufficiency guard. Invoke at 2x the selected window so the prior half is populated. |
| aiep-latency-trend | AI Endpoint Latency Trend | API Status — AI Endpoint | Yes | Canonical | table:requests | — | P50/P95/P99 request latency over time; sparse bins (N<30) are nulled. Aggregate latency can swing with traffic mix across endpoints. |
| aiep-op-regression | AI Endpoint Per-Operation P95 Regression | API Status — AI Endpoint | Yes | Canonical | table:requests | — | Per-operation P95 regression for AI Endpoint (current vs prior half-window). Mix-shift-immune, so this is the authoritative latency status trigger. Only operations with >=25% and >=50ms P95 increase, >=100 calls each half, prior P95 >=100ms. Invoke at 2x the selected window. |
| aiep-traffic-trend | AI Endpoint Traffic & Failure Trend | API Status — AI Endpoint | No | Canonical | table:requests | — | Total requests and 5xx server errors over time (bin scales with the selected window). |
| aiep-uptime | AI Endpoint Uptime (window) | API Status — AI Endpoint | Yes | Canonical | table:requests | — | Uptime for AI Endpoint over the window: share of hourly buckets (with traffic) whose 5xx rate stayed under 5%. Labelled 'data available in window' because sparse services only have partial history. |
| apim-4xx-trend | APIM Client Error (4xx) Trend | API Status — APIM Gateway | Yes | Canonical | table:requests | — | Client-side 4xx for APIM broken out by class (401 auth, 403 forbidden, 404 not-found, 429 throttled, other) over time. Informational only - drives an elevated-client-error note and a 401-spike flag, never the health pill. |
| apim-availability | APIM Availability | API Status — APIM Gateway | Yes | Canonical | table:availabilityResults | — | Availability from the APIM ping webtest. availabilityResults.success is a string, so use toint(success)==1. |
| apim-dep-regression | APIM Dependency Latency Regression | API Status — APIM Gateway | Yes | Canonical | table:dependencies | — | Downstream dependencies of APIM whose P95 got worse (current vs prior half-window). Two-pass join on target with a >=200 successful-call floor (CurOK) that structurally excludes prod-named fail-only probe rows. Empty result is a positive signal (no downstream regression), not an error. Does not feed status. |
| apim-endpoint-breakdown | APIM Endpoint Breakdown | API Status — APIM Gateway | No | Canonical | table:requests | — | Top operations by volume with per-operation 5xx, 4xx and P95 latency. |
| apim-health-summary | APIM Health Summary | API Status — APIM Gateway | Yes | Canonical | table:requests | — | Single-row health: total requests, 5xx server-error rate, 4xx client-error rate, and latency percentiles. Drives the status tile. |
| apim-latency-regression | APIM Latency Regression | API Status — APIM Gateway | Yes | Canonical | table:requests | — | Period-over-period P50/P95/P99 for APIM: current half-window vs prior half. Drives the tile latency-delta chip and the baseline-sufficiency guard. Invoke at 2x the selected window so the prior half is populated. |
| apim-latency-trend | APIM Latency Trend | API Status — APIM Gateway | Yes | Canonical | table:requests | — | P50/P95/P99 request latency over time; sparse bins (N<30) are nulled so they render as gaps. This is where latency degradations become visible. |
| apim-op-regression | APIM Per-Operation P95 Regression | API Status — APIM Gateway | Yes | Canonical | table:requests | — | Per-operation P95 regression for APIM (current vs prior half-window). Mix-shift-immune, so this is the authoritative latency status trigger. Only operations with >=25% and >=50ms P95 increase, >=100 calls each half, prior P95 >=100ms. Invoke at 2x the selected window. |
| apim-traffic-trend | APIM Traffic & Failure Trend | API Status — APIM Gateway | No | Canonical | table:requests | — | Total requests and 5xx server errors over time (bin scales with the selected window). |
| apim-uptime | APIM Uptime (window) | API Status — APIM Gateway | Yes | Canonical | table:requests | — | Uptime for APIM over the window: share of hourly buckets (with traffic) whose 5xx rate stayed under 5%. Labelled 'data available in window' because sparse services only have partial history. |
| licapi-4xx-trend | Licensing API Client Error (4xx) Trend | API Status — Licensing API | Yes | Canonical | table:requests | — | Client-side 4xx for Licensing API broken out by class (401 auth, 403 forbidden, 404 not-found, 429 throttled, other) over time. Informational only - drives an elevated-client-error note and a 401-spike flag, never the health pill. |
| licapi-dep-regression | Licensing API Dependency Latency Regression | API Status — Licensing API | Yes | Canonical | table:dependencies | — | Downstream dependencies of Licensing API whose P95 got worse (current vs prior half-window). Two-pass join on target with a >=200 successful-call floor (CurOK) that structurally excludes prod-named fail-only probe rows. Empty result is a positive signal (no downstream regression), not an error. Does not feed status. |
| licapi-endpoint-breakdown | Licensing API Endpoint Breakdown | API Status — Licensing API | No | Canonical | table:requests | — | Top operations by volume with per-operation 5xx, 4xx and P95 latency. |
| licapi-health-summary | Licensing API Health Summary | API Status — Licensing API | Yes | Canonical | table:requests | — | Single-row health: total requests, 5xx server-error rate, 4xx client-error rate, and latency percentiles. Drives the status tile. |
| licapi-latency-regression | Licensing API Latency Regression | API Status — Licensing API | Yes | Canonical | table:requests | — | Period-over-period P50/P95/P99 for Licensing API: current half-window vs prior half. Drives the tile latency-delta chip and the baseline-sufficiency guard. Invoke at 2x the selected window so the prior half is populated. |
| licapi-latency-trend | Licensing API Latency Trend | API Status — Licensing API | Yes | Canonical | table:requests | — | P50/P95/P99 request latency over time; sparse bins (N<30) are nulled so they render as gaps. |
| licapi-op-regression | Licensing API Per-Operation P95 Regression | API Status — Licensing API | Yes | Canonical | table:requests | — | Per-operation P95 regression for Licensing API (current vs prior half-window). Mix-shift-immune, so this is the authoritative latency status trigger. Only operations with >=25% and >=50ms P95 increase, >=100 calls each half, prior P95 >=100ms. Invoke at 2x the selected window. |
| licapi-traffic-trend | Licensing API Traffic & Failure Trend | API Status — Licensing API | No | Canonical | table:requests | — | Total requests and 5xx server errors over time (bin scales with the selected window). |
| licapi-uptime | Licensing API Uptime (window) | API Status — Licensing API | Yes | Canonical | table:requests | — | Uptime for Licensing API over the window: share of hourly buckets (with traffic) whose 5xx rate stayed under 5%. Labelled 'data available in window' because sparse services only have partial history. |
| 1-tool-invocation-frequency | Tool Invocation Frequency | App MCP | No | Canonical | uno/app-mcp/tool-invoked | — | Monitor which MCP tools agents use most frequently: |
| 10-most-common-tool-combinations | Most Common Tool Combinations | App MCP | No | Canonical | uno/app-mcp/tool-invoked | — | Identify frequently used tool sequences: |
| 11-daily-tool-invocations-trend | Daily Tool Invocations Trend | App MCP | No | Canonical | uno/app-mcp/tool-invoked | — | Monitor tool usage over time: |
| 12-agent-retention-rate | Agent Retention Rate (7-Day) | App MCP | Yes | Canonical | table:customEvents | — | Percentage of unique agents that return within 7 days. Target: ≥40% return rate. |
| 12-unique-machines-using-each-tool | Unique Machines Using Each Tool | App MCP | No | Canonical | uno/app-mcp/tool-invoked | — | Track adoption across different installations: |
| 13-last-successful-feature-use-before-churn | Last Successful Feature Use Before Churn | App MCP | Yes | Canonical | FeatureUsageCanonicalEvent | — | Correlate 30-day inactivity to each machine's last successful feature-use event (per Feature Usage Definition). Returns exposure, churn count, churn rate, uplift, and impact by feature. |
| 13-pro-tool-adoption-rate | Pro Tool Adoption Rate | App MCP | No | Canonical | uno/app-mcp/tool-invoked | — | Percentage of sessions using Pro-licensed tools. Target: ≥20% of sessions. |
| 14-drop-off-after-feature | Drop-off After Feature | App MCP | Yes | Canonical | FeatureUsageCanonicalEvent | — | Canonical feature-success drop-off analysis using the Feature Usage Definition; outputs standardized `Period`, `Feature`, `Users` plus drop-off metrics. |
| 15-daily-active-users-by-feature | Daily Active Users by Feature Adoption | App MCP | Yes | Canonical | FeatureUsageCanonicalEvent | — | Daily canonical feature-success users based on the Feature Usage Definition; outputs standardized `Period`, `Feature`, `Users` (with Day aliases for compatibility). |
| 15-tool-sequences-top10 | Most Common Tool Sequences (Top 10) | App MCP | No | Canonical | uno/app-mcp/tool-invoked | — | Popular 3-tool chains revealing agent workflow patterns. |
| 16-monthly-active-users-by-feature | Monthly Active Users by Feature Adoption | App MCP | Yes | Canonical | FeatureUsageCanonicalEvent | — | Track monthly unique active users in complete calendar month windows sized from the selected timeframe, with month-over-month change, based on successful feature use per the Feature Usage Definition, including Hot Design (without agent), Hot Design Agent, and App MCP tool users: |
| 16-weekly-active-users-by-feature | Studio - Weekly Active Studio Users | App MCP | Yes | Canonical | FeatureUsageCanonicalEvent | — | Track weekly unique active users in complete calendar week windows sized from the selected timeframe, with week-over-week change, based on successful feature use per the Feature Usage Definition, including Hot Design (without agent), Hot Design Agent, and App MCP tool users: |
| 17-debug-active-user-source-events | Debug Active User Source Events | App MCP | No | Canonical | FeatureUsageCanonicalEvent | — | Inspect raw events and segment flags used by active-user KPIs: |
| 17-timeout-rate-by-tool | Timeout Rate by Tool | App MCP | Yes | Canonical | uno/app-mcp/tool-invocation-failed, uno/app-mcp/tool-invoked | — | Percentage of tool invocations ending in TimeoutException. Target: <0.1%. |
| 18-uno-version-adoption | Uno Version Adoption | App MCP | Yes | Canonical | uno/generation/generate-xaml | — | Top adopted Uno SDK major.minor version based on distinct users from `uno/generation/generate-xaml` events and `Product Version`, with history anchored to the latest NuGet release launch date. |
| 19-visual-debugging-intensity | Visual Debugging Intensity | App MCP | Yes | Canonical | uno/app-mcp/tool-invoked | — | Average screenshots + visual tree queries per session, indicating debugging workflow health. |
| 2-tool-success-rate | Tool Success Rate | App MCP | Yes | Canonical | uno/app-mcp/tool-invocation-failed, uno/app-mcp/tool-invoked | — | Track success vs. failure rates for each tool: |
| 20-uno-version-adoption-trend | Uno Version Adoption Trend | App MCP | Yes | Canonical | uno/generation/generate-xaml | — | Daily distinct users by Uno SDK major.minor versions from `uno/generation/generate-xaml` + `Product Version`, with history anchored to the latest NuGet release launch date (dashboard groups versions < 6.0 into `Legacy (<6.0)` and groups remaining non-primary versions into Other). |
| 21-mtbf | Mean Time Between Failures (MTBF) | App MCP | No | Canonical | uno/app-mcp/tool-invocation-failed, uno/app-mcp/tool-invoked | — | Average successful invocations before an error occurs. Target: >1000 invocations per failure. |
| 22-week-over-week-growth | Week-over-Week Session Growth | App MCP | Yes | Canonical | uno/app-mcp/tool-invoked | — | Percentage increase in unique sessions across fixed complete calendar weeks (not rolling 7-day windows; current partial week excluded). Target: ≥10% weekly growth. |
| 3-session-duration-tools-per-session | Session Duration & Tools Per Session | App MCP | No | Canonical | uno/app-mcp/tool-invoked | — | Analyze MCP session patterns: |
| 4-platform-usage-distribution | Platform Usage Distribution | App MCP | No | Canonical | uno/app-mcp/tool-invoked | — | See which platforms (WebAssembly, iOS, Android, etc.) are being used: |
| 5-error-analysis | Error Analysis | App MCP | Yes | Canonical | uno/app-mcp/tool-invocation-failed, uno/app-mcp/tool-invoked | — | Track and categorize MCP errors: |
| 6-top-active-sessions | Top Active Sessions | App MCP | No | Canonical | uno/app-mcp/tool-invoked | — | View the most active MCP sessions: |
| 7-daily-session-activity | Daily Session Activity | App MCP | No | Canonical | uno/app-mcp/tool-invoked | — | Track unique sessions over time: |
| 8-tool-usage-distribution-per-session | Tool Usage Distribution Per Session | App MCP | No | Canonical | uno/app-mcp/tool-invoked | — | See how many tools sessions typically use: |
| 9-session-duration-distribution | Session Duration Distribution | App MCP | Yes | Canonical | uno/app-mcp/tool-invoked | — | Analyze session length patterns: |
| planned-session-properties | Planned Session Properties | App MCP | No | Canonical | uno/app-mcp/tool-invocation-failed | — | The following session-level properties are planned for future implementation: |
| unoapp-mcpunknown-tool-invoked | Unknown Tool Invoked | App MCP | Yes | Canonical | table:customEvents | — | Tracks attempts to use non-existent tools (helpful for identifying agent errors or API misuse). |
| app-launch-connection-timeout | App Launch Connection Timeout Rate | Dev Server | Yes | Canonical | uno/dev-server/app-launch/connection-timeout, uno/dev-server/app-launch/launched | — | Monitor app launch connection timeouts vs. successful connections. |
| crash | Crash Rate | Dev Server | Yes | Canonical | uno/dev-server/startup, uno/dev-server/startup-failure | — | Monitor catastrophic Dev Server failures requiring restart. |
| hot-reload-success | Hot Reload Success Rate | Dev Server | Yes | Canonical | uno/dev-server/hot-reload/notify-, uno/dev-server/hot-reload/notify-completed, uno/dev-server/hot-reload/notify-failed, uno/dev-server/hot-reload/notify-no-changes, uno/dev-server/hot-reload/notify-rude-edit | — | Track Hot Reload operation outcomes across all connections. |
| server-uptime | Server Uptime Distribution | Dev Server | Yes | Canonical | uno/dev-server/shutdown | — | Analyze how long Dev Server instances run before shutdown. |
| startup-success | Startup Success Rate | Dev Server | Yes | Canonical | uno/dev-server/startup, uno/dev-server/startup-failure | — | Track successful vs. failed Dev Server startups. Target: >99% success rate. |
| cache-hit-rate-over-time | Cache Hit Rate Over Time | Docs MCP | No | Canonical | table:customMetrics | — | Track cache performance metrics to optimize caching strategy and reduce API calls. |
| docsmcp-4xx-trend | Docs MCP Client Error (4xx) Trend | Docs MCP | Yes | Canonical | table:requests | — | Client-side 4xx for Docs MCP broken out by class (401 auth, 403 forbidden, 404 not-found, 429 throttled, other) over time. Informational only - drives an elevated-client-error note and a 401-spike flag, never the health pill. |
| docsmcp-endpoint-breakdown | Docs MCP Endpoint Breakdown | Docs MCP | No | Canonical | table:requests | — | Top operations by volume with per-operation 5xx, 4xx and P95 latency. |
| docsmcp-health-summary | Docs MCP Health Summary | Docs MCP | Yes | Canonical | table:requests | — | Single-row health: total requests, 5xx server-error rate, 4xx client-error rate, and latency percentiles. Drives the status tile. |
| docsmcp-latency-regression | Docs MCP Latency Regression | Docs MCP | Yes | Canonical | table:requests | — | Period-over-period P50/P95/P99 for Docs MCP: current half-window vs prior half. Drives the tile latency-delta chip and the baseline-sufficiency guard. Invoke at 2x the selected window so the prior half is populated. |
| docsmcp-latency-trend | Docs MCP Latency Trend | Docs MCP | Yes | Canonical | table:requests | — | P50/P95/P99 request latency over time; sparse bins (N<30) are nulled so they render as gaps. |
| docsmcp-traffic-trend | Docs MCP Traffic & Failure Trend | Docs MCP | No | Canonical | table:requests | — | Total requests and 5xx server errors over time (bin scales with the selected window). |
| docsmcp-uptime | Docs MCP Uptime (window) | Docs MCP | Yes | Canonical | table:requests | — | Uptime for Docs MCP over the window: share of hourly buckets (with traffic) whose 5xx rate stayed under 5%. Labelled 'data available in window' because sparse services only have partial history. |
| ingestion-monitoring | Ingestion Monitoring | Docs MCP | No | Canonical | table:customEvents | — | Track document ingestion operations including volume and processing performance. |
| search-performance | Search Performance Analysis | Docs MCP | No | Canonical | table:customEvents | — | Compare search performance between cached and non-cached results. |
| throttling | Throttling Analysis | Docs MCP | No | Canonical | table:customEvents | — | Monitor rate limiting events and patterns across client requests. |
| top-search-patterns | Top Search Patterns | Docs MCP | No | Canonical | table:customEvents, table:requests | — | Identify most common search queries and their average response times. |
| feature-discovery-counts | Feature Discovery Counts | Feature Usage | Yes | Canonical | uno/app-mcp/tool-invoked, uno/hot-design/usage | — | Counts discovery events and unique users per feature. |
| feature-failure-counts | Feature Failure Counts | Feature Usage | Yes | Canonical | uno/app-mcp/tool-invocation-failed, uno/hot-design/usage | — | Counts failure events and unique users per feature where failure telemetry exists. |
| feature-reliability-rate | Feature Reliability Rate | Feature Usage | Yes | Canonical | uno/app-mcp/tool-invocation-failed, uno/app-mcp/tool-invoked, uno/hot-design/usage | — | Computes per-feature reliability from successful and failed outcome events. |
| feature-success-counts | Feature Success Counts | Feature Usage | Yes | Canonical | uno/app-mcp/tool-invoked, uno/hot-design/usage | — | Counts successful usage events and unique users per feature. |
| activation-rate-by-cohort | Activation Rate by Cohort | Growth Analytics | Yes | Canonical | FeatureUsageCanonicalEvent | — | Tracks activation rate (3+ features used in first session) by weekly cohort. Monitors product improvements impact on new user success. |
| active-users-trend-dauwaumau | Active Users Trend (DAU/WAU/MAU) | Growth Analytics | Yes | Canonical | table:customEvents | — | Core engagement metric showing product health and growth momentum using fixed complete calendar windows (not rolling windows); excludes partial current week/month for stable WoW/MoM comparability. DAU/WAU ratio (stickiness) should be >20% for healthy engagement. |
| diagnostic-hot-design-events-check | Diagnostic: Hot Design Events Check | Growth Analytics | No | Canonical | uno/hot-design | — | Diagnostic query to verify what Hot Design events exist in telemetry. |
| diagnostic-usage-event-types | Diagnostic: Usage Event Types | Growth Analytics | No | Canonical | uno/hot-design/usage | — | Diagnostic query to see what UsageEvent values exist in Hot Design usage events. |
| feature-adoption-depth | Feature Adoption Depth | Growth Analytics | Yes | Canonical | FeatureUsageCanonicalEvent | — | Tracks how many features each user adopts over time. Deeper feature usage correlates with higher retention and willingness to pay. |
| feature-co-occurrence | Feature Co-occurrence Matrix | Growth Analytics | Yes | Canonical | FeatureUsageCanonicalEvent | — | Canonical feature-success co-occurrence aligned to the Feature Usage Definition; outputs standardized `Period`, `Feature`, `Users` (Feature contains pair label). |
| feature-stickiness | Feature Stickiness (DAU/WAU) | Growth Analytics | Yes | Canonical | FeatureUsageCanonicalEvent | — | Canonical feature-success DAU/WAU stickiness aligned to the Feature Usage Definition; includes standardized `Period`, `Feature`, `Users` plus AvgDAU/AvgWAU/Stickiness. |
| feature-wau-trend | Feature WAU Trend | Growth Analytics | Yes | Proxy | uno/app-mcp/tool-invoked, uno/hot-design/usage | Framework currently treats this as proxy pending finalized weekly canonical feature WAU governance for cross-report consistency. | Weekly canonical feature-success users aligned to the Feature Usage Definition; outputs standardized `Period`, `Feature`, `Users` (with Week/WAU aliases). |
| feature-weekly-cohort-matrix | Feature Weekly Cohort Matrix | Growth Analytics | Yes | Canonical | FeatureUsageCanonicalEvent | — | Week-to-week cohort behavior organized by feature using canonical feature-success events. Rows are grouped by Feature and Cohort week; columns show retention-like continuation rates from cohort week through +6 weeks. |
| first-feature-usage | First Feature Usage Distribution | Growth Analytics | Yes | Canonical | FeatureUsageCanonicalEvent | — | First canonical feature discovery per user using the Feature Usage Definition; outputs standardized `Period`, `Feature`, `Users`. |
| gh1-activation-comparison | GH1 Activation Comparison | Growth Analytics | Yes | Proxy | uno/hot-design/usage | Non-canonical UsageEvent values: AddElement, DebugSessionStarted, PropertyChanged, ToolboxDoubleClickToAdd, ToolboxDragToCanvas, ToolboxDragToElements | Compares activation rates between auto-launched first sessions and manual second sessions (natural A/B test). |
| gh1-auto-launch-adoption-rate | GH1 Auto Launch Adoption Rate | Growth Analytics | Yes | Proxy | uno/hot-design/usage | Non-canonical UsageEvent values: DebugSessionStarted | Tracks percentage of new users who experience auto-launch feature with return session rates. |
| gh1-daily-activation-trend | GH1 Daily Activation Trend | Growth Analytics | Yes | Proxy | uno/hot-design/usage | Non-canonical UsageEvent values: AddElement, DebugSessionStarted, PropertyChanged, ToolboxDoubleClickToAdd, ToolboxDragToCanvas, ToolboxDragToElements | Day-by-day activation rate with version period overlay. |
| gh1-early-dropoff-rate | GH1 Early Dropoff Rate | Growth Analytics | Yes | Proxy | uno/hot-design/session-end, uno/hot-design/usage | Non-canonical UsageEvent values: DebugSessionStarted | Tracks early session exits (<=30 seconds) by day and version period. |
| gh1-onboarding-completion-rate | GH1 Onboarding Completion Rate | Growth Analytics | Yes | Proxy | uno/hot-design/session-end, uno/hot-design/usage | Non-canonical UsageEvent values: DebugSessionStarted | Tracks percentage of users who complete their first session by version. |
| gh1-return-session-quality | GH1 Return Session Quality | Growth Analytics | Yes | Proxy | uno/hot-design/usage | Non-canonical UsageEvent values: DebugSessionStarted | Ensures auto-launch doesn't harm voluntary engagement - tracks return rates by version (guard metric). |
| gh1-session-duration-guard | GH1 Session Duration Guard | Growth Analytics | Yes | Proxy | uno/hot-design/session-end, uno/hot-design/usage | Non-canonical UsageEvent values: DebugSessionStarted | Ensures auto-launch maintains quality engagement - tracks session duration by version (guard metric). |
| gh1-time-to-first-interaction | GH1 Time To First Interaction | Growth Analytics | Yes | Proxy | uno/hot-design/usage | Non-canonical UsageEvent values: AddElement, DebugSessionStarted, PropertyChanged, ToolboxDoubleClickToAdd, ToolboxDragToCanvas, ToolboxDragToElements | Measures time from session start to first meaningful action with version comparison. |
| gh1-version-impact-summary | GH1 Version Impact Summary | Growth Analytics | Yes | Proxy | uno/hot-design/session-end, uno/hot-design/usage | Non-canonical UsageEvent values: AddElement, DebugSessionStarted, PropertyChanged, ToolboxDoubleClickToAdd, ToolboxDragToCanvas, ToolboxDragToElements | Comprehensive comparison of all key metrics before and after version 6.5. |
| growth-hack-1-auto-launch-adoption | Growth Hack #1: Auto-Launch Adoption Rate | Growth Analytics | Yes | Canonical | hot-design/session-started | — | Released: v6.5.64 on 2026-02-03, v6.5.153 on 2026-02-10 |
| growth-hack-2-time-to-first-interaction | Growth Hack #2: Time to First Interaction | Growth Analytics | Yes | Proxy | uno/hot-design/session-started, uno/hot-design/usage | Non-canonical UsageEvent values: agentEvents, manualEvents | Released: v6.5.64 on 2026-02-03, v6.5.153 on 2026-02-10 |
| power-user-identification | Power User Identification | Growth Analytics | Yes | Canonical | table:customEvents | — | Identifies users with professional usage patterns (5+ days/week, high feature depth). Power users are 10x more likely to convert to paid plans. |
| retention-curve-d1-d7-d14-d30 | Retention Curve (D1, D7, D14, D30) | Growth Analytics | Yes | Canonical | table:customEvents | — | Shows percentage of users returning after 1, 7, 14, and 30 days. Most critical metric for product-market fit. |
| studio-new-returning-users-dauwaumau | New and Returning Users (DAU/WAU/MAU) | Growth Analytics | Yes | Canonical | FeatureUsageCanonicalEvent | — | Tracks Studio active, new, and returning users across fixed complete daily, weekly, and monthly windows (partial current day/week/month excluded) using canonical Studio feature-success signals. |
| studio-new-returning-users-waumau | New and Returning Users (WAU/MAU) | Growth Analytics | Yes | Canonical | FeatureUsageCanonicalEvent | — | Tracks Studio active, new, and returning users across fixed complete weekly and monthly windows (partial current week/month excluded) using canonical Studio feature-success signals. |
| time-to-first-activation | Time to First Activation | Growth Analytics | Yes | Canonical | FeatureUsageCanonicalEvent | — | Measures time from first app launch to first meaningful action. Speed to value predicts retention - users activating within 15 minutes show 3x higher D7 retention. |
| weekly-cohort-retention | Weekly Cohort Retention Analysis | Growth Analytics | Yes | Canonical | table:customEvents | — | Tracks retention by signup week to measure product improvements impact over time. Shows if new cohorts retain better than old ones. |
| active-sessions | Daily Active Sessions | Hot Design | No | Canonical | uno/hot-design, uno/hot-design/session-started, uno/hot-design/usage | — | Monitor daily session activity to identify usage trends and patterns. |
| chat-generate-image-count | Chat Generate Image Count | Hot Design | No | Canonical | uno/hot-design/usage | — | Measure attached image count (ImageCount) when ChatGenerateStarted is fired. |
| chat-view-usage | Chat View Usage Trends | Hot Design | No | Canonical | uno/hot-design/usage | — | Monitor chat view usage over time. |
| context-options-usage | Context Options Usage | Hot Design | No | Proxy | uno/hot-design/usage | Non-canonical UsageEvent values: ChatContextOptionAdded, ChatContextOptionRemoved | Track how users utilize context options in chat. |
| crash-events | Crash Events | Hot Design | No | Canonical | uno/hot-design/usage | — | Monitor crash events and their frequency. |
| exception-type | Exception Type Distribution | Hot Design | No | Canonical | uno/hot-design/usage | — | Identify the most common exception types. |
| feature-correlation | Feature Correlation Analysis | Hot Design | No | Proxy | uno/hot-design/usage | Non-canonical UsageEvent values: PropertyChanged, ToolboxDoubleClickToAdd, ToolboxDragToCanvas, ToolboxDragToElements | Identify which features are commonly used together. |
| flyout-interaction-event-phases | Flyout Interaction Event Phases | Hot Design | No | Proxy | uno/hot-design/usage | Non-canonical UsageEvent values: PropertyFlyoutClosed, PropertyFlyoutOpened, ZoomFlyoutClosed, ZoomFlyoutOpened | Track opened/closed event phases for flyout interactions. |
| force-ui-update-event-phases | Force UI Update Event Phases | Hot Design | Yes | Proxy | uno/hot-design/usage | Non-canonical UsageEvent values: ForceUIUpdateCompleted, ForceUIUpdateStarted | Track started/completed phases for forced UI update flow. |
| form-factor-preferences | Form Factor Preferences | Hot Design | No | Proxy | uno/hot-design/usage | Non-canonical UsageEvent values: ChangeFormFactor | Understand which device form factors users target most. |
| hot-design-mode-entryexit-frequency | Hot Design Mode Entry/Exit Frequency | Hot Design | Yes | Canonical | uno/hot-design/usage | — | Track how often users enter and leave Hot Design mode. |
| identifying-hot-design-agent-users | Identifying Hot Design Agent Users | Hot Design | No | Proxy | uno/hot-design/usage | Non-canonical UsageEvent values: ChatGenerateCancelled, ChatImageAttached, ChatImageRemoved, ChatViewStartNew, ChatXamlPreviewSelected | Track users who specifically engage with the advanced Hot Design Agent AI capabilities. |
| identifying-hot-design-users | Identifying Hot Design Users | Hot Design | No | Canonical | uno/hot-design, uno/hot-design/session-started, uno/hot-design/usage | — | Track users who engage with the core Hot Design visual designer, regardless of AI feature usage. |
| image-attachment-methods | Image Attachment Methods | Hot Design | No | Proxy | uno/hot-design/usage | Non-canonical UsageEvent values: ChatImageAttached | Understand how users attach images to chat prompts. |
| license-status | License Status Distribution | Hot Design | Yes | Proxy | uno/hot-design/usage | LicenseTier is partially unknown for non-trial users because UsageEvent does not carry the specific paid tier (Professional vs Enterprise) | Understand the distribution of license statuses across users. |
| most-changed-properties | Top 10 Most Changed Properties | Hot Design | No | Proxy | uno/hot-design/usage | Non-canonical UsageEvent values: PropertyChanged | Identify which properties users modify most frequently. |
| most-common-search-terms-toolbox | Most Common Search Terms (Toolbox) | Hot Design | No | Proxy | uno/hot-design/usage | Non-canonical UsageEvent values: ToolboxSearch | Identify popular search terms in the toolbox. |
| most-used-toolbox-controls | Most Used Toolbox Controls | Hot Design | No | Proxy | uno/hot-design/usage | Non-canonical UsageEvent values: ToolboxDoubleClickToAdd, ToolboxDragToCanvas, ToolboxDragToElements | Track which controls users drag from the toolbox most often. |
| onboarding-funnel | Onboarding Funnel Analysis | Hot Design | Yes | Proxy | uno/hot-design/session-started, uno/hot-design/usage | Non-canonical UsageEvent values: PropertyChanged, ToolboxDoubleClickToAdd, ToolboxDragToCanvas, ToolboxDragToElements | Track user journey from first session to active usage. |
| operation-failure | Operation Failure Rate | Hot Design | Yes | Proxy | uno/hot-design/usage | Non-canonical UsageEvent values: AddElement, AddParent, ApplyTemplate, ChangeProperties, DeleteElement, MoveElement | Track failure rates for critical operations. |
| power-users-identification | Power Users Identification | Hot Design | Yes | Canonical | uno/hot-design | — | Identify highly engaged users for feedback and testing. |
| prompt-length | Average Prompt Length | Hot Design | No | Canonical | uno/hot-design/usage | — | Understand typical prompt lengths for XAML generation. |
| search-usage-by-category | Search Usage by Category | Hot Design | Yes | Proxy | uno/hot-design/usage | Non-canonical UsageEvent values: ElementsSearch, PreviewsSearch, PropertySearch, StoriesSearch, ToolboxSearch | Track which search features users utilize most. |
| session-duration | Session Duration Distribution | Hot Design | Yes | Canonical | uno/hot-design, uno/hot-design/session-end, uno/hot-design/usage | — | Understand how long users typically spend in Hot Design sessions. |
| session-quality-score | Session Quality Score | Hot Design | Yes | Canonical | uno/hot-design, uno/hot-design/session-end, uno/hot-design/session-started | — | Calculate a quality metric for sessions based on completion and activity. |
| sessions-and-average-duration | Total Sessions and Average Duration | Hot Design | No | Canonical | uno/hot-design | — | Track the total number of Hot Design sessions and their average duration to understand usage patterns. |
| time-in-hot-design-mode-per-session | Average Time in Hot Design Mode Per Session | Hot Design | Yes | Canonical | uno/hot-design/usage | — | Calculate average active time users spend in Hot Design mode. |
| trial-period-conversion | Trial Period Conversion Rate | Hot Design | Yes | Proxy | uno/hot-design/usage | Non-canonical UsageEvent values: HotDesignIsAvailable, HotDesignTrialPeriod | Track conversion from trial to licensed status. |
| unable-to-find-xaml-events | Unable To Find XAML Events | Hot Design | No | Proxy | uno/hot-design/usage | Non-canonical UsageEvent values: UnableToFindXaml | Track frequency of UnableToFindXaml events and available dimensions. |
| undoredo-operation-event-phases | Undo/Redo Operation Event Phases | Hot Design | No | Proxy | uno/hot-design/usage | Non-canonical UsageEvent values: RedoCompleted, RedoStarted, UndoCompleted, UndoStarted | Track started/completed event phases for undo/redo operations. |
| user-engagement-score | User Engagement Score | Hot Design | Yes | Proxy | uno/hot-design/session-started, uno/hot-design/usage | Non-canonical UsageEvent values: DebugSessionStarted, ElementsSearch, PreviewsSearch, PropertyChanged, PropertySearch, StoriesSearch, ToolboxDoubleClickToAdd, ToolboxDragToCanvas, ToolboxDragToElements, ToolboxSearch | Calculate a composite engagement score based on multiple activities. |
| weekly-active-users | Weekly Active Users | Hot Design | No | Canonical | uno/hot-design | — | Track unique users actively using Hot Design each week. |
| xaml-generation-progress-phases | XAML Generation Progress Phases | Hot Design | No | Canonical | uno/hot-design/usage | — | Track the phases of XAML generation to identify bottlenecks. |
| xaml-generation-success | XAML Generation Success Rate | Hot Design | Yes | Canonical | uno/hot-design/usage | — | Calculate the success rate of XAML generation requests. |
| 1-dev-server-start-success | Dev Server Start Success Rate | IDE Extensions | Yes | Canonical | uno/vs-vsix/server-start-, uno/vs-vsix/server-start-enumeration-exception, uno/vs-vsix/server-start-failure, uno/vs-vsix/server-start-package-layout-failure, uno/vs-vsix/server-start-success | — | Calculate success rate of dev server starts NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 1-extension-load-success | Extension Load Success Rate | IDE Extensions | Yes | Canonical | uno/vscode/extension-, uno/vscode/extension-failure, uno/vscode/extension-loaded | — | Calculate the success rate of extension loads NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 1-extension-load-success-rate-by-ide | Extension Load Success Rate by IDE Version | IDE Extensions | Yes | Canonical | uno/rider/extension-, uno/rider/extension-failure, uno/rider/extension-loaded | — | Calculate extension load success rate segmented by Rider version NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 1-ide-usage | IDE Usage Distribution | IDE Extensions | Yes | Canonical | uno/rider/extension-loaded, uno/vs-vsix/server-start-success, uno/vs-vsix/udei-opened, uno/vscode/extension-loaded | — | Distribution of active users across all IDE extensions NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 1-vs-code-success-paths | VS Code Success Paths | IDE Extensions | Yes | Proxy | uno/dev-server/app-launch/connected, uno/dev-server/hot-reload/notify-complete, uno/dev-server/shutdown, uno/hot-design/usage, uno/vscode/extension-loaded | Out-of-scope events: uno/dev-server/app-launch/connected, uno/dev-server/hot-reload/notify-complete, uno/dev-server/shutdown | Core + optional success paths for VS Code (Core 4-stage, Hot Design, Agent Preview). |
| 1-vs-code-usage-funnel | VS Code Usage Funnel | IDE Extensions | Yes | Canonical | uno/dev-server/app-launch/connected, uno/dev-server/app-launch/connection-timeout, uno/dev-server/hot-reload/notify-complete, uno/dev-server/hot-reload/notify-failed, uno/dev-server/hot-reload/notify-rude-edit, uno/dev-server/parent-process-lost, uno/dev-server/parent-process-lost-forced-exit, uno/dev-server/shutdown, uno/dev-server/startup-failure, uno/vscode/extension-failure, uno/vscode/extension-loaded | — | Core IDE cycle funnel for VS Code using the 4-stage model (Discovery, App Connected, Hot Reload, Shutdown), with failure/abandoned breakdown, measured across all unique users in the selected timeframe (excluding CI) |
| 1-vs-code-usage-funnel-hdagent | VS Code HD Agent Funnel | IDE Extensions | Yes | Proxy | uno/dev-server/app-launch/connected, uno/dev-server/app-launch/connection-timeout, uno/dev-server/parent-process-lost, uno/dev-server/parent-process-lost-forced-exit, uno/dev-server/shutdown, uno/dev-server/startup-failure, uno/hot-design/session-end, uno/hot-design/session-started, uno/hot-design/usage, uno/hot-design/usage/Crash, uno/vscode/extension-failure, uno/vscode/extension-loaded | Out-of-scope events: uno/dev-server/app-launch/connected, uno/dev-server/app-launch/connection-timeout, uno/dev-server/parent-process-lost, uno/dev-server/parent-process-lost-forced-exit, uno/dev-server/shutdown, uno/dev-server/startup-failure | Hot Design Agent funnel for VS Code using the 8-stage model (Discovery, App Connected, HD Session Started, Chat View Opened, Chat Generate Started, Chat Preview Applied, HD Session End, Shutdown), with failure/abandoned breakdown including HD Crash events, measured across all unique users in the selected timeframe (excluding CI) |
| 1-vs-code-usage-funnel-hotdesign | VS Code Hot Design Funnel | IDE Extensions | Yes | Proxy | uno/dev-server/app-launch/connected, uno/dev-server/app-launch/connection-timeout, uno/dev-server/parent-process-lost, uno/dev-server/parent-process-lost-forced-exit, uno/dev-server/shutdown, uno/dev-server/startup-failure, uno/hot-design/session-end, uno/hot-design/session-started, uno/hot-design/usage, uno/hot-design/usage/Crash, uno/vscode/extension-failure, uno/vscode/extension-loaded | Out-of-scope events: uno/dev-server/app-launch/connected, uno/dev-server/app-launch/connection-timeout, uno/dev-server/parent-process-lost, uno/dev-server/parent-process-lost-forced-exit, uno/dev-server/shutdown, uno/dev-server/startup-failure | Hot Design IDE cycle funnel for VS Code using the 6-stage model (Discovery, App Connected, HD Session Started, HD Property Changed, HD Session End, Shutdown), with failure/abandoned breakdown including HD Crash events, measured across all unique users in the selected timeframe (excluding CI) |
| 10-daily-server-start-activity | Daily Server Start Activity | IDE Extensions | Yes | Canonical | uno/vs-vsix/server-start-, uno/vs-vsix/server-start-enumeration-exception, uno/vs-vsix/server-start-failure, uno/vs-vsix/server-start-package-layout-failure, uno/vs-vsix/server-start-success | — | Track daily server start attempts and success rate NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 2-extension-load-success-rate-across | Extension Load Success Rate Across All IDEs | IDE Extensions | Yes | Canonical | uno/rider/extension-, uno/rider/extension-failure, uno/rider/extension-loaded, uno/vs-vsix/server-start-, uno/vs-vsix/server-start-success, uno/vscode/extension-, uno/vscode/extension-failure, uno/vscode/extension-loaded | — | Compare extension load success rates across IDEs NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 2-project-creation | Project Creation Trends | IDE Extensions | Yes | Canonical | uno/rider/project-created | — | Track new Uno project creation over time |
| 2-rider-success-paths | Rider Success Paths | IDE Extensions | Yes | Proxy | uno/dev-server/app-launch/connected, uno/dev-server/hot-reload/notify-complete, uno/dev-server/shutdown, uno/hot-design/usage, uno/rider/extension-loaded | Out-of-scope events: uno/dev-server/app-launch/connected, uno/dev-server/hot-reload/notify-complete, uno/dev-server/shutdown | Core + optional success paths for Rider (Core 4-stage, Hot Design, Agent Preview). |
| 2-rider-usage-funnel | Rider Usage Funnel | IDE Extensions | Yes | Canonical | uno/dev-server/app-launch/connected, uno/dev-server/app-launch/connection-timeout, uno/dev-server/hot-reload/notify-complete, uno/dev-server/hot-reload/notify-failed, uno/dev-server/hot-reload/notify-rude-edit, uno/dev-server/parent-process-lost, uno/dev-server/parent-process-lost-forced-exit, uno/dev-server/shutdown, uno/dev-server/startup-failure, uno/rider/extension-failure, uno/rider/extension-loaded | — | Core IDE cycle funnel for Rider using the 4-stage model (Discovery, App Connected, Hot Reload, Shutdown), with failure/abandoned breakdown, measured across all unique users in the selected timeframe (excluding CI) |
| 2-rider-usage-funnel-hdagent | Rider HD Agent Funnel | IDE Extensions | Yes | Proxy | uno/dev-server/app-launch/connected, uno/dev-server/app-launch/connection-timeout, uno/dev-server/parent-process-lost, uno/dev-server/parent-process-lost-forced-exit, uno/dev-server/shutdown, uno/dev-server/startup-failure, uno/hot-design/session-end, uno/hot-design/session-started, uno/hot-design/usage, uno/hot-design/usage/Crash, uno/rider/extension-failure, uno/rider/extension-loaded | Out-of-scope events: uno/dev-server/app-launch/connected, uno/dev-server/app-launch/connection-timeout, uno/dev-server/parent-process-lost, uno/dev-server/parent-process-lost-forced-exit, uno/dev-server/shutdown, uno/dev-server/startup-failure | Hot Design Agent funnel for Rider using the 8-stage model (Discovery, App Connected, HD Session Started, Chat View Opened, Chat Generate Started, Chat Preview Applied, HD Session End, Shutdown), with failure/abandoned breakdown including HD Crash events, measured across all unique users in the selected timeframe (excluding CI) |
| 2-rider-usage-funnel-hotdesign | Rider Hot Design Funnel | IDE Extensions | Yes | Proxy | uno/dev-server/app-launch/connected, uno/dev-server/app-launch/connection-timeout, uno/dev-server/parent-process-lost, uno/dev-server/parent-process-lost-forced-exit, uno/dev-server/shutdown, uno/dev-server/startup-failure, uno/hot-design/session-end, uno/hot-design/session-started, uno/hot-design/usage, uno/hot-design/usage/Crash, uno/rider/extension-failure, uno/rider/extension-loaded | Out-of-scope events: uno/dev-server/app-launch/connected, uno/dev-server/app-launch/connection-timeout, uno/dev-server/parent-process-lost, uno/dev-server/parent-process-lost-forced-exit, uno/dev-server/shutdown, uno/dev-server/startup-failure | Hot Design IDE cycle funnel for Rider using the 6-stage model (Discovery, App Connected, HD Session Started, HD Property Changed, HD Session End, Shutdown), with failure/abandoned breakdown including HD Crash events, measured across all unique users in the selected timeframe (excluding CI) |
| 2-server-start-performance-average | Server Start Performance (Average Duration with Percentiles) | IDE Extensions | No | Canonical | uno/vs-vsix/server-start-success | — | Performance metrics for successful server starts NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 2-top-extension-failures | Top Extension Failures | IDE Extensions | Yes | Canonical | uno/vscode/extension-failure | — | Most common extension failure types NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 3-build-activity-patterns | Build Activity Patterns | IDE Extensions | Yes | Canonical | uno/rider/solution-build | — | Solution build frequency and patterns NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 3-server-start-performance | Server Start Performance Trend | IDE Extensions | No | Canonical | uno/vs-vsix/server-start-success | — | Track server start performance over time NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 3-udei-action-popularity | UDEI Action Popularity | IDE Extensions | Yes | Canonical | uno/vscode/udei-action-clicked | — | Most frequently used UDEI actions |
| 3-udei-engagement-across-ides | UDEI Engagement Across IDEs | IDE Extensions | Yes | Canonical | uno/rider/udei-opened, uno/vs-vsix/udei-opened, uno/vscode/udei-opened | — | Compare UDEI usage across all IDE extensions |
| 3-visual-studio-success-paths | Visual Studio Success Paths | IDE Extensions | Yes | Proxy | uno/dev-server/app-launch/connected, uno/dev-server/hot-reload/notify-complete, uno/dev-server/shutdown, uno/hot-design/usage, uno/vs-vsix/server-start-success | Out-of-scope events: uno/dev-server/app-launch/connected, uno/dev-server/hot-reload/notify-complete, uno/dev-server/shutdown | Core + optional success paths for Visual Studio (Core 4-stage, Hot Design, Agent Preview). |
| 3-visual-studio-usage-funnel | Visual Studio Usage Funnel | IDE Extensions | Yes | Canonical | uno/dev-server/app-launch/connected, uno/dev-server/app-launch/connection-timeout, uno/dev-server/hot-reload/notify-complete, uno/dev-server/hot-reload/notify-failed, uno/dev-server/hot-reload/notify-rude-edit, uno/dev-server/parent-process-lost, uno/dev-server/parent-process-lost-forced-exit, uno/dev-server/shutdown, uno/dev-server/startup-failure, uno/vs-vsix/server-start-failure, uno/vs-vsix/server-start-success | — | Core IDE cycle funnel for Visual Studio using the 4-stage model (Discovery, App Connected, Hot Reload, Shutdown), with failure/abandoned breakdown, measured across all unique users in the selected timeframe (excluding CI) |
| 3-visual-studio-usage-funnel-hdagent | Visual Studio HD Agent Funnel | IDE Extensions | Yes | Proxy | uno/dev-server/app-launch/connected, uno/dev-server/app-launch/connection-timeout, uno/dev-server/parent-process-lost, uno/dev-server/parent-process-lost-forced-exit, uno/dev-server/shutdown, uno/dev-server/startup-failure, uno/hot-design/session-end, uno/hot-design/session-started, uno/hot-design/usage, uno/hot-design/usage/Crash, uno/vs-vsix/server-start-failure, uno/vs-vsix/server-start-success | Out-of-scope events: uno/dev-server/app-launch/connected, uno/dev-server/app-launch/connection-timeout, uno/dev-server/parent-process-lost, uno/dev-server/parent-process-lost-forced-exit, uno/dev-server/shutdown, uno/dev-server/startup-failure | Hot Design Agent funnel for Visual Studio using the 8-stage model (Discovery, App Connected, HD Session Started, Chat View Opened, Chat Generate Started, Chat Preview Applied, HD Session End, Shutdown), with failure/abandoned breakdown including HD Crash events, measured across all unique users in the selected timeframe (excluding CI) |
| 3-visual-studio-usage-funnel-hotdesign | Visual Studio Hot Design Funnel | IDE Extensions | Yes | Proxy | uno/dev-server/app-launch/connected, uno/dev-server/app-launch/connection-timeout, uno/dev-server/parent-process-lost, uno/dev-server/parent-process-lost-forced-exit, uno/dev-server/shutdown, uno/dev-server/startup-failure, uno/hot-design/session-end, uno/hot-design/session-started, uno/hot-design/usage, uno/hot-design/usage/Crash, uno/vs-vsix/server-start-failure, uno/vs-vsix/server-start-success | Out-of-scope events: uno/dev-server/app-launch/connected, uno/dev-server/app-launch/connection-timeout, uno/dev-server/parent-process-lost, uno/dev-server/parent-process-lost-forced-exit, uno/dev-server/shutdown, uno/dev-server/startup-failure | Hot Design IDE cycle funnel for Visual Studio using the 6-stage model (Discovery, App Connected, HD Session Started, HD Property Changed, HD Session End, Shutdown), with failure/abandoned breakdown including HD Crash events, measured across all unique users in the selected timeframe (excluding CI) |
| 4-daily-active-users-by-plugin-version | Daily Active Users by Plugin Version | IDE Extensions | No | Canonical | uno/vscode/extension-loaded | — | Track daily active users segmented by plugin version |
| 4-debug-vs-non-debug-launch-ratio | Debug vs Non-Debug Launch Ratio | IDE Extensions | Yes | Canonical | uno/rider/debugger-launched, uno/rider/no-debugger-launch | — | Compare debugger usage across launches NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 4-dev-server-restart-frequency-by-ide | Dev Server Restart Frequency by IDE | IDE Extensions | Yes | Canonical | uno/rider/dev-server-restart, uno/vscode/dev-server-restart | — | Compare dev server restart patterns across IDEs NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 4-failures-by-server-package | Failures by Server Package | IDE Extensions | Yes | Canonical | uno/vs-vsix/server-start-failure, uno/vs-vsix/server-start-package-layout-failure | — | Server start failures segmented by package type NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 4-funnel-dropoff | Funnel Dropoff Analysis | IDE Extensions | Yes | Canonical | uno/dev-server/app-launch/connected, uno/dev-server/hot-reload/notify-complete, uno/dev-server/shutdown, uno/rider/extension-loaded, uno/vs-vsix/server-start-success, uno/vscode/extension-loaded | — | Detailed analysis of user dropoff between 4-stage IDE cycle stages across all IDEs |
| 5-cross-ide-funnel-comparison | Cross-IDE Funnel Comparison | IDE Extensions | Yes | Canonical | uno/dev-server/app-launch/connected, uno/dev-server/hot-reload/notify-complete, uno/dev-server/shutdown, uno/rider/extension-loaded, uno/vs-vsix/server-start-success, uno/vscode/extension-loaded | — | Compare 4-stage IDE cycle completion rates across all three IDE extensions |
| 5-dev-server-restart-frequency | Dev Server Restart Frequency | IDE Extensions | Yes | Canonical | uno/vscode/dev-server-restart | — | Average dev server restarts per user per day |
| 5-extension-failure-rate-comparison | Extension Failure Rate Comparison | IDE Extensions | Yes | Canonical | uno/rider/extension-failure, uno/vs-vsix/server-start-enumeration-exception, uno/vs-vsix/server-start-failure, uno/vs-vsix/server-start-package-layout-failure, uno/vs-vsix/udei-failure, uno/vscode/extension-failure | — | Compare failure rates across all IDE extensions NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 5-top-extension-failures-by-plugin | Top Extension Failures by Plugin Version | IDE Extensions | No | Canonical | uno/rider/extension-failure | — | Most common extension failures segmented by plugin version |
| 5-udei-reliability-score | UDEI Reliability Score | IDE Extensions | Yes | Canonical | uno/vs-vsix/udei-, uno/vs-vsix/udei-action-clicked, uno/vs-vsix/udei-failure, uno/vs-vsix/udei-opened | — | Calculate UDEI reliability metrics NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 6-enumeration-failures-by-ide-version | Enumeration Failures by IDE Version | IDE Extensions | No | Canonical | uno/vs-vsix/enumeration-fail | — | Project enumeration failures segmented by Visual Studio version NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 6-extension-health-dashboard | Extension Health Dashboard | IDE Extensions | Yes | Canonical | uno/vscode/dev-server-restart, uno/vscode/extension-, uno/vscode/extension-failure, uno/vscode/extension-loaded, uno/vscode/udei-opened | — | Comprehensive health metrics for VS Code extension NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 6-funnel-analysis-with-time-cohorts | Funnel Analysis with Time Cohorts | IDE Extensions | Yes | Canonical | uno/dev-server/shutdown, uno/rider/extension-loaded, uno/vs-vsix/server-start-success, uno/vscode/extension-loaded | — | Track how 4-stage IDE cycle completion rates vary by installation cohort (weekly cohorts) |
| 6-ide-version-adoption | IDE Version Adoption | IDE Extensions | Yes | Canonical | uno/rider/extension-loaded | — | Distribution of users across Rider versions |
| 7-performance-comparison-success-vs | Performance Comparison: Success vs Failure Duration | IDE Extensions | No | Canonical | uno/vs-vsix/server-start-enumeration-exception, uno/vs-vsix/server-start-failure, uno/vs-vsix/server-start-success | — | Compare duration of successful vs failed server starts NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 7-user-engagement-score | User Engagement Score | IDE Extensions | No | Canonical | uno/rider/debugger-launched, uno/rider/extension-loaded, uno/rider/no-debugger-launch, uno/rider/project-created, uno/rider/solution-build, uno/rider/udei-opened | — | Composite engagement metric based on multiple activities NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 8-top-udei-actions-by-frequency | Top UDEI Actions by Frequency | IDE Extensions | Yes | Canonical | uno/vs-vsix/udei-action-clicked | — | Most frequently used UDEI actions |
| 9-plugin-version | Plugin Version Distribution | IDE Extensions | Yes | Canonical | table:customEvents | — | Distribution of active users by plugin version |
| ide-abandonment-by-stage | IDE Abandonment by Stage | IDE Extensions | Yes | Canonical | uno/dev-server/app-launch/connected, uno/dev-server/hot-reload/notify-complete, uno/dev-server/shutdown, uno/rider/extension-loaded, uno/vs-vsix/server-start-success, uno/vscode/extension-loaded | — | Dropped users and drop rate between adjacent stages of the 4-stage IDE cycle by IDE. |
| ide-cycle-completion-rate | IDE Cycle Completion Rate | IDE Extensions | Yes | Canonical | uno/dev-server/app-launch/connected, uno/rider/extension-loaded, uno/vs-vsix/server-start-success, uno/vscode/extension-loaded | — | Completion from IDE discovery to app connected by IDE (required core stages). |
| ide-failure-reason-distribution | IDE Failure Reason Distribution | IDE Extensions | Yes | Canonical | uno/dev-server/app-launch/connection-timeout, uno/dev-server/parent-process-lost-forced-exit, uno/dev-server/startup-failure, uno/rider/extension-failure, uno/vs-vsix/server-start-enumeration-exception, uno/vs-vsix/server-start-failure, uno/vs-vsix/server-start-package-layout-failure, uno/vs-vsix/udei-failure, uno/vscode/extension-failure | — | Distribution of failure reason buckets by IDE for core cycle failures. |
| ide-recovery-after-failure | IDE Recovery After Failure | IDE Extensions | Yes | Canonical | uno/dev-server/app-launch/connected, uno/dev-server/app-launch/connection-timeout, uno/dev-server/parent-process-lost-forced-exit, uno/dev-server/startup-failure, uno/rider/extension-loaded, uno/vs-vsix/server-start-success, uno/vscode/extension-loaded | — | Users who recover to app connected within 24h after a failure, by IDE. |
| ide-repeat-success-rate | IDE Repeat Success Rate | IDE Extensions | Yes | Canonical | uno/dev-server/app-launch/connected, uno/rider/extension-loaded, uno/vs-vsix/server-start-success, uno/vscode/extension-loaded | — | Share of connected users who reach app connected at least twice in timeframe. |
| ide-stage-conversion-rates | IDE Stage Conversion Rates | IDE Extensions | Yes | Canonical | uno/dev-server/app-launch/connected, uno/dev-server/hot-reload/notify-complete, uno/dev-server/shutdown, uno/rider/extension-loaded, uno/vs-vsix/server-start-success, uno/vscode/extension-loaded | — | Stage-by-stage conversion from discovery for each IDE 4-stage cycle. |
| ide-time-to-connect | IDE Time to Completion | IDE Extensions | Yes | Canonical | uno/dev-server/shutdown, uno/rider/extension-loaded, uno/vs-vsix/server-start-success, uno/vscode/extension-loaded | — | Median/P90 minutes from IDE discovery to shutdown by IDE. |
| ide-version-segmented-completion | IDE Version-Segmented Completion | IDE Extensions | Yes | Canonical | uno/dev-server/app-launch/connected, uno/rider/extension-loaded, uno/vs-vsix/server-start-success, uno/vscode/extension-loaded | — | Completion rate by IDE and plugin version (discovery cohort to app connected). |
| vs-ai-agent-impact-on-completion | Visual Studio AI/Agent Impact on Completion | IDE Extensions | Yes | Proxy | uno/dev-server/app-launch/connected, uno/hot-design/usage, uno/vs-vsix/server-start-success | Out-of-scope events: uno/dev-server/app-launch/connected; Non-canonical UsageEvent values: ChatGenerateStarted, ChatViewOpened, ChatXamlPreviewApplied | Completion comparison for Visual Studio discovery cohort split by AI/agent usage signals. Signals currently rely on hot-design chat usage events and may undercount true AI usage. |
| vs-dropoff-stage-diagnostics | Visual Studio Stage Drop-off Diagnostics | IDE Extensions | Yes | Canonical | uno/dev-server/app-launch/connected, uno/dev-server/hot-reload/notify-complete, uno/dev-server/shutdown, uno/vs-vsix/server-start-success | — | Focused stage-to-stage drop-off for Visual Studio 4-stage cycle to isolate the primary loss transition. |
| vs-failure-reason-diagnostics | Visual Studio Failure Reason Diagnostics | IDE Extensions | Yes | Proxy | uno/app-mcp/tool-invocation-failed, uno/dev-server/hot-reload/notify-failed, uno/dev-server/startup-failure, uno/docs-mcp/SearchError, uno/hot-design/usage, uno/uno-check/check-fail, uno/vs-vsix/server-start-failure, uno/vs-vsix/server-start-success, uno/vs-vsix/udei-failure | Out-of-scope events: uno/dev-server/hot-reload/notify-failed, uno/dev-server/startup-failure, uno/docs-mcp/SearchError, uno/uno-check/check-fail, uno/vs-vsix/udei-failure | Focused Visual Studio failure reason diagnostics aligned to Feature Usage Definition failure rules, scoped to users in the Visual Studio discovery cohort. |
| vs-stage-latency-diagnostics | Visual Studio Stage Latency Diagnostics | IDE Extensions | Yes | Canonical | uno/dev-server/app-launch/connected, uno/dev-server/hot-reload/notify-complete, uno/dev-server/shutdown, uno/vs-vsix/server-start-success | — | Focused transition latency for Visual Studio 4-stage cycle (median and P90 minutes) to identify slow stages linked to abandonment. |
| kpi-r1-adoption-funnel-proxy | KPI R 1 Adoption Funnel Proxy | KPI Framework | Yes | Proxy | uno/licensing/license-status, uno/app-mcp/tool-invoked, uno/hot-design/usage, uno/docs-mcp/SearchRequest, uno/uno-check/check-success, uno/hot-design/session-end | Telemetry-only funnel proxy; GA visitor stage and full cross-product canonical trial-start coverage are not fully joined. | Proxy funnel from trial starts to first activation and high-intent usage (telemetry-only, no GA join). NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| kpi-r1-funnel-monthly-stage-trend | KPI R 1 Funnel Monthly Stage Trend | KPI Framework | Yes | Proxy | uno/licensing/license-status, uno/app-mcp/tool-invoked, uno/hot-design/usage, uno/docs-mcp/SearchRequest, uno/uno-check/check-success, uno/hot-design/session-end | Monthly trend is proxy because it excludes GA top-of-funnel visitor telemetry and relies on telemetry-only stage reconstruction. | Monthly funnel stage trend (trial starts, activated users, high-intent users) for Report 1 charts. NOTE: This is telemetry-only and excludes the GA visitor stage until GA join is implemented. |
| kpi-r1-strict-cohort-funnel | KPI R 1 Strict Cohort Funnel | KPI Framework | Yes | Canonical | FeatureUsageCanonicalEvent | — | Strict cohort funnel for Report 1: trial-start cohort users who activate within 7 days and reach high-intent within 7 days. Uses explicit analysis start/end dates and includes only cohorts with a fully closed 7-day observation window. |
| kpi-r10-monthly-trial-starts-proxy | KPI R 10 Monthly Trial Starts Proxy | KPI Framework | No | Proxy | uno/licensing/license-status | Trial starts are proxy for attribution because GA visitor denominator and UTM persistence are not joined for canonical attribution. | Monthly trial starts trend for attribution baseline (without GA visitor denominator). NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| kpi-r10-traffic-to-trial-proxy-correlation | KPI R 10 Traffic To Trial Proxy Correlation | KPI Framework | Yes | Proxy | uno/uno-check/check-start, uno/has-updates, uno/platform/new-project, uno/licensing/license-status | Traffic-to-trial correlation is proxy because upstream traffic is represented by OSS/tooling telemetry signals rather than canonical GA channel attribution. | Monthly proxy correlation of upstream OSS/tooling traffic signals versus trial starts for Report 10. NOTE: GA traffic is not yet joined, so this is a telemetry proxy and not final attribution. |
| kpi-r2-time-to-activation-histogram | KPI R 2 Time To Activation Histogram | KPI Framework | Yes | Canonical | FeatureUsageCanonicalEvent | — | Time-to-activation histogram buckets for Activation Analysis charts. |
| kpi-r5-activation-rate-by-environment | KPI R 5 Activation Rate By Environment | KPI Framework | Yes | Canonical | FeatureUsageCanonicalEvent | — | Activation rate by developer environment for Report 5 grouped-bar requirements. |
| kpi-r5-developer-environment-distribution | KPI R 5 Developer Environment Distribution | KPI Framework | No | Proxy | uno/app-mcp/tool-invoked, uno/hot-design/usage | Environment distribution remains proxy while environment dimensions are not fully normalized and documented across all producers. | Developer environment and host distribution for active users by week. NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| kpi-r6-ai-funnel-proxy | KPI R 6 AI Funnel Proxy | KPI Framework | Yes | Proxy | uno/hot-design/usage | AI funnel is proxy because explicit suggestion lifecycle telemetry (prompt_sent/suggestion_generated/suggestion_accepted/suggestion_rejected) is not fully instrumented. | AI funnel proxy for Report 6: opened -> prompt started -> generation progress -> preview applied. NOTE: Explicit suggestion lifecycle telemetry is not yet available. TODO: Add/Document `prompt_sent`, `suggestion_generated`, `suggestion_accepted`, and `suggestion_rejected` events in Telemetry-HotDesign.md. |
| kpi-r6-ai-paid-vs-free-wau-trend | KPI R 6 AI Paid VS Free WAU Trend | KPI Framework | Yes | Proxy | uno/hot-design/usage, uno/docs-mcp/SearchRequest | Out-of-scope events: uno/docs-mcp/SearchRequest | Weekly AI WAU trend split by paid-vs-free proxies for Report 6 monthly trend. NOTE: Free AI proxy currently uses Docs MCP only; App MCP context/interactivity split is pending telemetry normalization. |
| kpi-r7-oss-studio-proxy-bridge | KPI R 7 OSS Studio Proxy Bridge | KPI Framework | Yes | Proxy | uno/uno-check/check-start, uno/has-updates, uno/platform/new-project, uno/licensing/license-status | OSS-to-Studio bridge is proxy because identity-level stitch between OSS telemetry and Studio telemetry is unavailable. | Weekly proxy bridge trend comparing OSS/tooling signals and Studio trial starts (no identity-level stitch). Default lookback 120 days to cover pre/post HD auto-launch. NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| kpi-r8-retention-benchmark-trend | KPI R 8 Retention Benchmark Trend | KPI Framework | Yes | Canonical | table:customEvents | — | Monthly trend of cohort retention benchmarks (W1 and W4) for Report 8 monthly trend chart. |
| kpi-r9-aha-candidate-retention | KPI R 9 Aha Candidate Retention | KPI Framework | Yes | Canonical | FeatureUsageCanonicalEvent | — | Candidate Aha moment proxy: early feature usage and 7-day return behavior. |
| 1-license-status | License Tier Distribution | Licensing | Yes | Canonical | uno/licensing/license-status | — | Shows the distribution of unique users across license tiers over the last 30 days. |
| 10-help-support-navigation-patterns | Help & Support Navigation Patterns | Licensing | Yes | Canonical | uno/licensing/nav-to-help- | — | Identifies most accessed help resources over the last 30 days. NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 11-license-expiry-warning | License Expiry Warning Analysis | Licensing | Yes | Canonical | uno/licensing/license-status | — | Tracks licenses approaching expiration at 7, 30, and 90-day thresholds. |
| 12-devserver-service-lifecycle-health | DevServer Service Lifecycle Health | Licensing | No | Canonical | N/A, uno/licensing/devserver/service- | — | Monitors DevServer service reliability over the last 7 days. NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 13-new-trials-wow | New Trials per Week (WoW) | Licensing | No | Canonical | uno/licensing/license-status | — | Week-over-week trend of new trial users. Counts the first appearance of each unique user identity with a Trial license per week. |
| 14-trial-conversion-wow | Trial-to-Paid Conversion (WoW) | Licensing | Yes | Canonical | uno/licensing/license-status | — | Week-over-week trial-to-paid conversion rate. Converted = a unique user identity that first appeared with a Trial license and later emitted a license-status event with a paid tier (Professional or Business). Conversions are attributed to the week the trial started, not the week the paid license appeared. Note: conversion is inferred from license-status tier changes, not billing/purchase events. |
| 2-authentication-success | Authentication Success Rate | Licensing | No | Canonical | uno/licensing/login-, uno/licensing/login-canceled, uno/licensing/login-failure, uno/licensing/login-success, uno/licensing/login-timeout | — | Calculates login success rate with breakdown by outcome over the last 7 days. NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 3-licensespring-api-performance | LicenseSpring API Performance | Licensing | No | Canonical | table:customEvents | — | Analyzes API performance with percentile metrics over the last 24 hours. |
| 4-trial-period | Trial Period Analysis | Licensing | Yes | Canonical | uno/licensing/license-status | — | Monitors trial usage and identifies trials approaching expiration in the last 30 days. |
| 5-feature-access-denial | Feature Access Denial Analysis | Licensing | No | Canonical | uno/licensing/devserver/license-feature-not-granted | — | Identifies features users attempt to access without valid licenses over the last 30 days. NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 6-license-manager-reliability | License Manager Reliability | Licensing | No | Canonical | uno/licensing/devserver/license-manager-start, uno/licensing/devserver/manager-failed, uno/licensing/devserver/manager-started | — | Monitors license manager startup success rates over the last 7 days. NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 7-authentication-error | Authentication Error Analysis | Licensing | No | Canonical | uno/licensing/login-failure, uno/licensing/login-timeout | — | Identifies common authentication failure patterns over the last 7 days. NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 8-user-navigation-to-purchase-funnel | User Navigation to Purchase Funnel | Licensing | Yes | Canonical | uno/licensing/nav-to-, uno/licensing/nav-to-my-account, uno/licensing/nav-to-purchase-now, uno/licensing/nav-to-trial-extension | — | Tracks user engagement with purchase-related navigation over the last 30 days. NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 9-api-error-rate-by-operation | API Error Rate by Operation | Licensing | No | Canonical | table:customEvents | — | Calculates success and failure rates per API operation over the last 7 days. |
| studio-chat-view-usage-trend | Studio Chat View Usage Trend | Studio | No | Canonical | uno/hot-design/usage | — | Monitor chat view usage over time. |
| studio-daily-active-sessions | Studio Daily Active Sessions | Studio | No | Canonical | uno/hot-design, uno/hot-design/session-started, uno/hot-design/usage | — | Monitor daily session activity to identify usage trends and patterns. |
| studio-tool-invocation-frequency | Studio Tool Invocation Frequency | Studio | No | Canonical | uno/app-mcp/tool-invoked | — | Monitor which MCP tools agents use most frequently: |
| studio-tool-success-rate | Studio Tool Success Rate | Studio | Yes | Canonical | uno/app-mcp/tool-invocation-failed, uno/app-mcp/tool-invoked | — | Track success vs. failure rates for each tool: |
| studio-tool-timeout-rate-by-tool | Studio Tool Timeout Rate By Tool | Studio | Yes | Canonical | uno/app-mcp/tool-invocation-failed, uno/app-mcp/tool-invoked | — | Percentage of tool invocations ending in TimeoutException. Target: <0.1%. |
| studio-xaml-generation-success-rate | Studio XAML Generation Success Rate | Studio | Yes | Canonical | uno/hot-design/usage | — | Calculate the success rate of XAML generation requests. |
| studio-live-action-edit-iterate | Studio Live Action — Made an Edit / Iterated | Studio Live Telemetry | No | Proxy | uno/studio-live/compilation-started | No dedicated edit/iterate event is emitted by Studio Live; sessions with two or more compilation-started events are used as the proxy for iterative editing. | Coverage proxy for making an edit / iterating (issue #845). No dedicated edit event exists; sessions with two or more compilations are treated as iterative editing. Returns sessions with compiles, iterative sessions, and average compiles per session. |
| studio-live-action-preview-reached | Studio Live Action — Reached a Running Preview | Studio Live Telemetry | No | Proxy | uno/studio-live/compilation-succeeded | No dedicated running-preview event is emitted by Studio Live; a successful compilation (compilation-succeeded) is used as the proxy for a rendered preview. | Coverage proxy for reaching a running preview (issue #845). No dedicated preview event exists; a successful compilation is treated as the rendered preview. Returns proxy event, session, and user counts. |
| studio-live-action-returning-users | Studio Live Action — Returned 2 or More Times | Studio Live Telemetry | Yes | Canonical | uno/studio-live/session-start | — | Coverage for repeat visits (issue #845): users with two or more Studio Live sessions in the period, from session-start. Returns total users, returning users, and returning rate. |
| studio-live-action-save-export | Studio Live Action — Saved or Exported a Project | Studio Live Telemetry | No | Canonical | uno/studio-live/project-download-completed | — | Coverage for saving (Trigger=Workspace) and exporting (Trigger=Export) a project (issue #845), from project-download-completed. Web Studio Live has no in-place save; a workspace download is the save. Returns save, export, and untagged completion counts plus distinct users. |
| studio-live-activation-rate | Studio Live Activation Rate (Dual Source) | Studio Live Telemetry | Yes | Proxy | uno/studio-live/project-download-started, uno/studio-live/project-download-completed, uno/generation/generate-xaml-done | Reach baseline includes Wasm-inferred non-studio-live activity. | Share of reached users that performed a first-value action across direct and Wasm-inferred Studio Live activity. |
| studio-live-agent-cancellation-rate | Studio Live Agent Cancellation Rate | Studio Live Telemetry | Yes | Canonical | uno/studio-live/agent-suggestion-generated, uno/studio-live/agent-generation-cancelled | — | Share of agent prompt cycles cancelled before completion, with CancelReason breakdown (UserStop, ConversationCleared, NewGeneration). |
| studio-live-agent-duration | Studio Live Agent Generation Duration | Studio Live Telemetry | Yes | Canonical | uno/studio-live/agent-suggestion-generated | — | Median and P90 generation duration (ms) from agent-suggestion-generated telemetry, segmented by outcome category. |
| studio-live-agent-empty-response-rate | Studio Live Agent Empty Response Rate | Studio Live Telemetry | Yes | Canonical | uno/studio-live/agent-empty-response, uno/studio-live/agent-prompt-sent | — | Data Source: customEvents Events: uno/studio-live/agent-empty-response, uno/studio-live/agent-prompt-sent Aggregation: Daily count of empty agent completions (the alertable model-outage signal, #2578), prompt count, and empty responses per 1,000 prompts. CI-excluded. Note: Empty-response volume is low and has historically been CI-heavy; CI exclusion is applied so this tracks real user-facing model outages, not test traffic. |
| studio-live-agent-prompt-volume | Studio Live Agent Prompt Volume | Studio Live Telemetry | No | Canonical | uno/studio-live/agent-prompt-sent | — | Daily and weekly Studio Live agent prompt submission volume from agent-prompt-sent telemetry. |
| studio-live-agent-success-rate | Studio Live Agent Generation Success Rate | Studio Live Telemetry | Yes | Canonical | uno/studio-live/agent-suggestion-generated | — | Distribution of agent generation outcome categories (Success, Warning, Critical, IterationLimitReached, ContextOverflowExhausted) from agent-suggestion-generated telemetry. |
| studio-live-cohort-retention-weekly | Studio Live Weekly Cohort Retention | Studio Live Telemetry | Yes | Proxy | uno/studio-live/session-start | Anonymous web identity does not persist across visits (1 of 3,592 users seen in 2+ weeks over 90d), so weekly retention is structurally degenerate until a durable identity ships. | Data Source: customEvents Events: uno/studio-live/session-start Aggregation: Weekly cohorts by first in-window session-start; retention = any session-start in cohort week + N (N = 1, 4, 12). WnPct is null until cohort week + N is a complete calendar week (no fake zeros); cohorts younger than W1 and the partial current cohort week are excluded. Note: Cohort entry is window-scoped, so the earliest cohorts in the window are left-censored (users active before the window appear new). Use 90d+ selections for meaningful W4/W12 columns. NOTE: This query requires undocumented telemetry: a durable cross-visit user identity. Live validation (2026-07-07, 90d, pinned timespan) found only 1 of 3,592 users active in two or more distinct weeks - anonymous web identity does not persist across visits, so weekly retention reads ~0% regardless of actual user behavior. Current result is provisional and may under-report. TODO: Add/Document a durable (account-backed) user identity on session-start in Telemetry-StudioLive.md and instrumentation source. |
| studio-live-compilation-duration | Studio Live Compilation Duration | Studio Live Telemetry | No | Canonical | uno/studio-live/compilation-succeeded | — | Daily P50/P90 successful compilation duration in milliseconds. |
| studio-live-compilation-error-categories | Studio Live Compilation Error Categories | Studio Live Telemetry | No | Canonical | uno/studio-live/compilation-failed | — | Build-error compilations grouped by sanitized ErrorCategory (Syntax, Type, Dependency, Other). |
| studio-live-compilation-failure-breakdown | Studio Live Compilation Failure Breakdown | Studio Live Telemetry | No | Canonical | uno/studio-live/compilation-failed | — | Compilation failures grouped by OutcomeCategory, including worker-infrastructure failure outcomes. |
| studio-live-compilation-funnel | Studio Live Compilation Funnel | Studio Live Telemetry | Yes | Canonical | uno/studio-live/compilation-started, uno/studio-live/compilation-succeeded, uno/studio-live/compilation-failed | — | Compilation started/succeeded/failed counts with success and failure rates from compilation telemetry. |
| studio-live-compilation-retry-recovery | Studio Live Compilation Retry Recovery | Studio Live Telemetry | No | Canonical | uno/studio-live/compilation-retried | — | Distribution of compilation retries by consecutive-attempt depth, surfacing compile-fail loops. |
| studio-live-daily-active-users | Studio Live Daily Active Users | Studio Live Telemetry | No | Canonical | uno/studio-live/session-start | — | Daily active Studio Live users from session-start telemetry. |
| studio-live-direct-inferred-mix-trend | Studio Live Direct vs Inferred Mix Trend | Studio Live Telemetry | Yes | Proxy | uno/studio-live/session-start, uno/generation/generate-xaml | Mix includes Wasm-based inferred activity from non-studio-live event names. | Weekly event mix split between direct studio-live events and Wasm-inferred non-studio-live events. |
| studio-live-download-conversion-trend | Studio Live Download Conversion Trend | Studio Live Telemetry | Yes | Canonical | uno/studio-live/project-download-started, uno/studio-live/project-download-completed | — | Weekly download conversion rate trend for Studio Live. |
| studio-live-download-funnel | Studio Live Download Funnel | Studio Live Telemetry | Yes | Canonical | uno/studio-live/project-download-started, uno/studio-live/project-download-completed, uno/studio-live/project-download-failed | — | Download funnel counts and conversion rates from started to completed and failed outcomes. |
| studio-live-engaged-minutes-per-user | Studio Live Engaged Minutes per User | Studio Live Telemetry | Yes | Canonical | uno/studio-live/session-heartbeat | — | Data Source: customEvents Events: uno/studio-live/session-heartbeat Measurement: ActiveMs (double; foreground milliseconds per 60s heartbeat interval) Aggregation: Daily engaged minutes per active user: sum of ActiveMs per user per day / 60000, averaged over users emitting heartbeats that day. Raw daily rows (weekend filtering is a dashboard toggle). Replaces the session-end duration metric, which under-samples on WASM flush loss. |
| studio-live-error-rate | Studio Live Error Rate | Studio Live Telemetry | No | Canonical | uno/studio-live/error | — | Sanitized runtime error events grouped by Category with critical-severity counts. |
| studio-live-error-trend-normalized | Studio Live Usage Normalized Error Trend | Studio Live Telemetry | Yes | Canonical | uno/studio-live/error, uno/studio-live/session-heartbeat | — | Data Source: customEvents Events: uno/studio-live/error, uno/studio-live/session-heartbeat Aggregation: Weekly error events per 1,000 session heartbeats, plus Critical-severity errors per 1,000 heartbeats. Complete calendar weeks only (partial leading and current weeks excluded). Heartbeat volume is the usage denominator so error trends are not confounded by traffic growth. |
| studio-live-failure-free-session-rate | Studio Live Failure-Free Session Rate | Studio Live Telemetry | Yes | Proxy | uno/studio-live/error, uno/studio-live/project-download-failed, uno/generation/generate-xaml-failed, uno/hot-design/usage | Session set includes Wasm-inferred non-studio-live activity. | Share of Studio Live sessions without crash/failure indicators in direct + Wasm-inferred telemetry. |
| studio-live-gate-to-entitled-conversion | Studio Live Gate to Entitled Conversion | Studio Live Telemetry | Yes | Proxy | uno/studio-live/license-feature-not-granted, uno/studio-live/license-feature-info-returned, uno/studio-live/agent-prompt-sent | Built on upstream-emitted Uno.Licensing.Sdk gate events with machine-scoped identity; conversion is inferred from event ordering rather than purchase confirmation. | Data Source: customEvents Events: uno/studio-live/license-feature-not-granted, uno/studio-live/license-feature-info-returned, uno/studio-live/agent-prompt-sent Aggregation: Users hitting license-feature-not-granted who later emit license-feature-info-returned for the same Feature (entitlement is encoded by which event fires; there is no entitlement property), plus entitled-to-active-AI conversion (entitled users with at least one agent-prompt-sent). NOTE: This query requires undocumented telemetry: license-feature- events carry only a Feature property (values like uno.studioweb, uno.aigen) - no tier, trial, or purchase data, so conversion is inferred from event ordering, not from a purchase confirmation. Current result is provisional and may under-report. TODO: Add/Document sanitized tier/trial dimensions on license-feature- events in the upstream Uno.Licensing.Sdk instrumentation. |
| studio-live-inferred-coverage | Studio Live Inferred Coverage Ratio | Studio Live Telemetry | Yes | Proxy | uno/studio-live/session-start, uno/generation/generate-xaml | Coverage uses Wasm-based inference for non-studio-live events. | Share of Studio Live reach that is inferred via Wasm non-studio-live events. |
| studio-live-monthly-stickiness | Studio Live Monthly Stickiness | Studio Live Telemetry | Yes | Canonical | uno/studio-live/session-start | — | Data Source: customEvents Events: uno/studio-live/session-start Aggregation: DAU/MAU stickiness per complete calendar month: AvgDAU = mean of daily distinct users, MAU = monthly distinct users, StickinessPercent = 100 * AvgDAU / MAU. Partial leading and current months are excluded per the fixed-window rule. Note: Requires a timeframe spanning at least one complete calendar month (use 90d+); shorter selections return no rows by design. |
| studio-live-new-user-activation-rate | Studio Live New User Activation Rate | Studio Live Telemetry | Yes | Canonical | uno/studio-live/session-start, uno/studio-live/compilation-succeeded | — | Data Source: customEvents Events: uno/studio-live/session-start, uno/studio-live/compilation-succeeded Aggregation: Share of new users (first-ever session-start falling inside the selected window, using a fixed 180-day first-seen baseline) who reach their first successful compilation within 7 days of first session. Users first seen less than 7 days ago are excluded so every counted user had a complete activation horizon. Note: First-seen is left-censored at the 180-day baseline: a user inactive for more than 180 days before returning is counted as new. As of 2026-07 the baseline predates Studio Live production telemetry, so censoring is negligible. |
| studio-live-reach-daily-users | Studio Live Reach DAU (Direct + Wasm Inferred) | Studio Live Telemetry | Yes | Proxy | uno/studio-live/session-start, uno/generation/generate-xaml, uno/generation/generate-xaml-done | Includes inferred Studio Live activity derived from non-studio-live events where OS Architecture is Wasm. | Daily Studio Live reach combining direct studio-live events and Wasm-inferred activity from non-studio-live events. |
| studio-live-reach-weekly-users | Studio Live Reach WAU (Direct + Wasm Inferred) | Studio Live Telemetry | Yes | Proxy | uno/studio-live/session-start, uno/generation/generate-xaml, uno/generation/generate-xaml-done | Includes inferred Studio Live activity derived from non-studio-live events where OS Architecture is Wasm. | Weekly Studio Live reach combining direct studio-live events and Wasm-inferred activity. |
| studio-live-retention-summary | Studio Live D1/D7/D30 Retention Summary | Studio Live Telemetry | Yes | Proxy | uno/studio-live/session-start, uno/generation/generate-xaml | Retention cohort includes Wasm-inferred users from non-studio-live event names. | Retention summary using first-seen versus last-seen recurrence for direct + Wasm-inferred Studio Live users. |
| studio-live-session-summary | Studio Live Session Summary | Studio Live Telemetry | No | Proxy | uno/studio-live/session-start, uno/studio-live/session-end | Average session duration is computed from session-end events that under-deliver (~2% of started sessions) on WASM flush loss; session and user counts from session-start remain reliable. | Session volume, unique users, and average session duration for Studio Live. |
| studio-live-signup-to-value-funnel | Studio Live Signup to Value Funnel | Studio Live Telemetry | Yes | Proxy | uno/studio-live/license-feature-info-returned, uno/studio-live/license-feature-not-granted, uno/studio-live/session-start, uno/studio-live/agent-prompt-sent, uno/studio-live/agent-suggestion-generated, uno/studio-live/compilation-succeeded, uno/studio-live/project-download-completed | Top-of-funnel uses upstream-emitted license-gate events as a signup proxy; identity for anonymous web users is machine-scoped and stages are not sequence-enforced per user. | Data Source: customEvents Events: uno/studio-live/license-feature-info-returned, uno/studio-live/license-feature-not-granted, uno/studio-live/session-start, uno/studio-live/agent-prompt-sent, uno/studio-live/agent-suggestion-generated, uno/studio-live/compilation-succeeded, uno/studio-live/project-download-completed Aggregation: Distinct users per funnel stage within the window (stages are not sequence-enforced per user); GatedNoSessionUsers counts gate-touch users with no session-start. NOTE: This query requires undocumented telemetry: there is no true account-signup event for Studio Live; the license gate touch (either license-feature event) is the top-of-funnel proxy. License-gate events are emitted by the upstream Uno.Licensing.Sdk and carry only a Feature property. Current result is provisional and may under-report. TODO: Add/Document a dedicated signup/account-created telemetry event for Studio Live in Telemetry-StudioLive.md and instrumentation source. |
| studio-live-time-to-first-value | Studio Live Time to First Value | Studio Live Telemetry | Yes | Canonical | uno/studio-live/session-start, uno/studio-live/compilation-succeeded | — | Data Source: customEvents Events: uno/studio-live/session-start, uno/studio-live/compilation-succeeded Aggregation: Per-user minutes from first in-window session-start to first successful compilation (median, P90, user count), CI-excluded, canonical identity. Users whose first compilation precedes their first in-window session are excluded. |
| studio-live-wasm-session-depth | Studio Live Wasm Session Depth | Studio Live Telemetry | Yes | Proxy | uno/studio-live/session-start, uno/studio-live/session-heartbeat, uno/generation/generate-xaml | Wasm session set includes inferred non-studio-live events. | Session volume and p50/p95 duration for Wasm Studio Live sessions. |
| studio-live-weekly-active-creators | Studio Live Weekly Active Creators | Studio Live Telemetry | No | Canonical | uno/studio-live/compilation-succeeded | — | Data Source: customEvents Events: uno/studio-live/compilation-succeeded Aggregation: Distinct users with at least one successful compilation per complete calendar week (startofweek buckets; partial leading and current weeks excluded), CI-excluded, canonical identity. North Star metric. Note: Week-over-week growth is computed in the dashboard UI from adjacent rows per the snapshot contract; the query intentionally emits raw weekly rows only. |
| studio-live-weekly-active-users | Studio Live Weekly Active Users | Studio Live Telemetry | No | Canonical | uno/studio-live/session-start | — | Weekly active Studio Live users from session-start telemetry. |
| check-duration-by-outcome | Check Duration by Outcome | Uno.Check | No | Canonical | uno/uno-check/check-fail, uno/uno-check/check-success, uno/uno-check/check-warn | — | customEvents NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| check-duration-percentiles | Check Duration Percentiles | Uno.Check | No | Canonical | uno/uno-check/check-fail, uno/uno-check/check-success, uno/uno-check/check-warn | — | customEvents NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| check-execution-time | Check Execution Time Distribution | Uno.Check | No | Canonical | uno/uno-check/check-fail, uno/uno-check/check-success, uno/uno-check/check-warn | — | customEvents NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| check-volume | Daily Check Volume Trend | Uno.Check | No | Canonical | uno/uno-check/check-start | — | customEvents |
| failed-checks-co-occurrence-matrix | Failed Checks Co-occurrence Matrix | Uno.Check | No | Canonical | uno/uno-check/check-fail, uno/uno-check/check-warn | — | customEvents NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| framework-combination-patterns | Framework Combination Patterns | Uno.Check | No | Canonical | uno/uno-check/check-start | — | customEvents |
| most-common-failed-checks | Most Common Failed Checks | Uno.Check | No | Canonical | uno/uno-check/check-fail, uno/uno-check/check-warn | — | customEvents NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| most-requested-frameworks | Most Requested Frameworks | Uno.Check | No | Canonical | uno/uno-check/check-start | — | customEvents |
| overall-success-rate-last-7-days | Overall Success Rate (Last 7 Days) | Uno.Check | No | Canonical | uno/uno-check/check-, uno/uno-check/check-fail, uno/uno-check/check-success, uno/uno-check/check-warn | — | customEvents NOTE: This query requires undocumented telemetry (event/property). Current result is provisional and may under-report. TODO: Add/Document telemetry for required event/property in Telemetry-<Component>.md and instrumentation source. |
| 1-success-vs-cancellation | Success vs. Cancellation Rate | Wizard | No | Canonical | uno/wizard/live | — | Track wizard completion rates and understand user drop-off patterns. |
| configuration-popularity-over-time | Configuration Popularity Over Time | Wizard | No | Canonical | uno/wizard/live | — | Track how preference for different presets or platforms evolves over time. |
| dailyweekly-project-creation | Daily/Weekly Project Creation Trends | Wizard | No | Canonical | uno/wizard/live | — | Visualize project creation activity over time to identify usage patterns and growth trends. |
| duration-by-outcome | Duration by Outcome | Wizard | No | Canonical | uno/wizard/live | — | Compare wizard duration for completed projects vs. cancelled sessions. |
| full-configuration-pattern | Full Configuration Pattern Analysis | Wizard | No | Canonical | uno/wizard/live | — | Identify the most common complete configuration patterns (preset + platform + markup + theme). |
| mean-median-and-percentile | Mean, Median, and Percentile Analysis | Wizard | Yes | Canonical | uno/wizard/live | — | Statistical analysis of wizard completion times to understand typical user behavior and outliers. |
| popular-preset-platform-combinations | Popular Preset + Platform Combinations | Wizard | No | Canonical | uno/wizard/live | — | Analyze which preset and platform combinations are most frequently used together. |
| project-creation-funnel | Project Creation Funnel | Wizard | Yes | Canonical | uno/wizard/live | — | Analyze the wizard completion funnel from start to finish, including command generation as an alternative outcome. |
| top-markup-languages | Top Markup Languages | Wizard | Yes | Canonical | uno/wizard/live | — | Analyze the distribution of XAML vs. C# markup preferences. |
| top-platform-combinations | Top Platform Combinations | Wizard | No | Canonical | uno/wizard/live | — | Find the most popular platform combinations selected by users. |
| top-presets-by-usage | Top Presets by Usage | Wizard | No | Canonical | uno/wizard/live | — | Analyze which template presets are most popular among users. |
| top-themesdesign-systems | Top Themes/Design Systems | Wizard | No | Canonical | uno/wizard/live | — | Identify which design systems (Material, Fluent, Cupertino, Native) are most popular. |
| 1-high-failure-rate-alert | High Failure Rate Alert | XAML Generation | Yes | Canonical | uno/generation/generate-xaml, uno/generation/generate-xaml-failed | — | Trigger Condition: Failure rate exceeds 5% in the last hour |
| 2-performance-degradation-alert | Performance Degradation Alert | XAML Generation | No | Canonical | uno/generation/generate-xaml-done | — | Trigger Condition: P95 duration exceeds 20 seconds in the last hour |
| bucketed-file-count-performance | Bucketed File Count Performance Analysis | XAML Generation | Yes | Canonical | uno/generation/generate-xaml, uno/generation/generate-xaml-done | — | Analyze performance impact across different file count ranges. |
| builds-per-user-session-statistics | Builds Per User Session Statistics | XAML Generation | No | Canonical | uno/generation/generate-xaml | — | Analyze user session patterns to understand typical usage. |
| correlation-between-file-count-and | Correlation Between File Count and Generation Duration | XAML Generation | Yes | Canonical | uno/generation/generate-xaml, uno/generation/generate-xaml-done | — | Show how file count impacts generation performance. |
| daily-weekly-and-monthly-active-users | Daily, Weekly, and Monthly Active Users (DAU/WAU/MAU) | XAML Generation | No | Canonical | uno/generation/generate-xaml | — | Track unique user engagement using fixed complete calendar windows (not rolling windows): last full day, last full week, last full month. |
| debug-vs-release-build | Debug vs Release Build Distribution | XAML Generation | Yes | Canonical | uno/generation/generate-xaml | — | Understand the split between debug and release builds. |
| distribution-by-unoruntime | Distribution by UnoRuntime | XAML Generation | No | Canonical | uno/generation/generate-xaml | — | Visualize the distribution of builds across different Uno Platform runtimes. |
| failure-rate-by-configuration | Failure Rate by Configuration | XAML Generation | Yes | Canonical | uno/generation/generate-xaml, uno/generation/generate-xaml-failed | — | Identify which configurations experience the highest failure rates. |
| file-count-statistics-by-unoruntime | File Count Statistics by UnoRuntime | XAML Generation | No | Canonical | uno/generation/generate-xaml | — | Analyze average, median, and maximum file counts across different runtimes. |
| generation-duration-by-unoruntime | Average Generation Duration by UnoRuntime | XAML Generation | Yes | Canonical | uno/generation/generate-xaml, uno/generation/generate-xaml-done | — | Measure average performance across different Uno Platform runtimes with percentile analysis. |
| ide-usage | IDE Usage Distribution | XAML Generation | No | Canonical | uno/generation/generate-xaml | — | Track which IDEs are most commonly used for XAML generation builds. |
| most-used-target-frameworks | Top 10 Most Used Target Frameworks | XAML Generation | No | Canonical | uno/generation/generate-xaml | — | Identify which target frameworks are most commonly used. |
| overall-xaml-generation-success | Overall XAML Generation Success Rate | XAML Generation | Yes | Canonical | uno/generation/generate-xaml, uno/generation/generate-xaml-done, uno/generation/generate-xaml-failed | — | Calculate the success rate across all XAML generation attempts to monitor system health. |
| performance-trend-over-time | Daily Performance Trend Over Time | XAML Generation | No | Canonical | uno/generation/generate-xaml-done | — | Visualize daily performance trends to identify performance degradation or improvements. |
| sla-compliance-tracking | SLA Compliance Tracking | XAML Generation | No | Canonical | uno/generation/generate-xaml-done | — | Track the percentage of builds completing within defined SLA targets. |
| slow-builds-detection-outliers-10 | Slow Builds Detection (Outliers > 10 seconds) | XAML Generation | Yes | Canonical | uno/generation/generate-xaml, uno/generation/generate-xaml-done | — | Identify builds taking longer than 10 seconds to investigate performance issues. |
| top-failure-exception-types | Top Failure Exception Types | XAML Generation | No | Canonical | uno/generation/generate-xaml-failed | — | Identify the most common exception types causing XAML generation failures. |
| ui-automation-mapping-adoption | UI Automation Mapping Adoption | XAML Generation | Yes | Canonical | uno/generation/generate-xaml | — | Track the adoption rate of UI Automation mapping feature. |
| weekly-user-retention-cohort | Weekly User Retention Cohort Analysis | XAML Generation | No | Canonical | uno/generation/generate-xaml | — | Analyze user retention patterns across fixed complete calendar weeks (cohort-based, not rolling windows). |