Skip to content

Add Quality Metrics section to monitoring-plan#93

Open
lakmeedee wants to merge 2 commits into
Azure-Samples:managedfrom
lakmeedee:monitoring-plan-quality-metrics
Open

Add Quality Metrics section to monitoring-plan#93
lakmeedee wants to merge 2 commits into
Azure-Samples:managedfrom
lakmeedee:monitoring-plan-quality-metrics

Conversation

@lakmeedee
Copy link
Copy Markdown
Contributor

Adds a new Section 5.2 Quality Metrics to demos/analytics-using-managedcleanroom/tsg/monitoring-plan.md consolidating the QoS / quality telemetry items in one place:

  1. QoS / success rate of Cleanroom RP CRUD operations (incl. pause/resume) with client-side vs server-side classification, code and reason.
  2. QoS / success rate of Analytics Frontend operations with client-side vs server-side classification.
  3. #queries published / submitted / successfully run / failed to run at a collaboration level.
  4. Query execution failure reason classification (client-side: syntax, SKR, storage/KV access; server-side: data loading, etc.).
  5. Query execution time and average at a collaboration level.
  6. #parallel queries executing in a collaboration (with query IDs).

Also adds three rows to Section 5.1 Business Metrics: bytes of data scanned, average collaborators per collaboration, and collaboration distribution by workload type. Bumps Engineering Health Reports to Section 5.3.

…-plan

- Add new Section 5.2 Quality Metrics consolidating QoS/success-rate, query counts, failure-reason classification, query execution time, and parallel-query telemetry
- Bump Engineering Health Reports to Section 5.3
- Add 'Data volume processed (bytes of data scanned)', 'Average collaborators per collaboration', and 'Collaboration distribution by workload type' to Section 5.1 Business Metrics
@lakmeedee lakmeedee requested a review from a team as a code owner May 18, 2026 11:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant