ff-oce-kusto
Use this skill for any Kusto query or telemetry investigation specifically related to Fluid Framework or its partners. Triggers include: writing or running a Kusto query against the Office Fluid database, investigating Fluid Framework telemetry or error rates, querying Office_Fluid_FluidRuntime_* tables, looking up a Fluid session by Session_Id or docId, investigating a Fluid-related error in Loop or Whiteboard telemetry, monitoring an FF bump or partner ring deployment, checking Fluid render reliability or Scriptor errors, or when the user mentions Fluid-specific tables (Office_Fluid_FluidRuntime_*, OwhLoads, HostTracker, Scriptor) or Fluid-specific error types (dataCorruptionError, dataProcessingError, DeltaConnectionFailureToConnect, ICE, ACE). Do NOT trigger for general Kusto questions that are not related to Fluid Framework.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 4.9k
- Forks
- 590
01 前言 Front Matter
- name
- ff-oce-kusto
- version
- 1.0.0
- description
- Use this skill for any Kusto query or telemetry investigation specifically related to Fluid Framework or its partners. Triggers include: writing or running a Kusto query against the Office Fluid database, investigating Fluid Framework telemetry or error rates, querying Office_Fluid_FluidRuntime_* tables, looking up a Fluid session by Session_Id or docId, investigating a Fluid-related error in Loop or Whiteboard telemetry, monitoring an FF bump or partner ring deployment, checking Fluid render reliability or Scriptor errors, or when the user mentions Fluid-specific tables (Office_Fluid_FluidRuntime_*, OwhLoads, HostTracker, Scriptor) or Fluid-specific error types (dataCorruptionError, dataProcessingError, DeltaConnectionFailureToConnect, ICE, ACE). Do NOT trigger for general Kusto questions that are not related to Fluid Framework.
02 资源文件 4
- 参考文档references/checkpoint-safety.md9.3 KB
- 参考文档references/gke-training-deployment.md13.1 KB
- 参考文档references/kusto-query-reference.md76.4 KB
- 参考文档references/performance-diagnosis.md9.2 KB
03 SKILL.md 正文
Fluid Framework Kusto Reference
This skill provides a comprehensive reference for Fluid Framework telemetry investigation in Kusto. Load it whenever a Kusto query needs to be written, interpreted, or run against the Office Fluid database.
VPN required. The Office Fluid Kusto cluster (
https://kusto.aria.microsoft.com) is only reachable on the Microsoft internal network. If a query fails to connect or returns no results unexpectedly, remind the user to check that their VPN is on before troubleshooting further.
Cluster & Access
- Cluster:
https://kusto.aria.microsoft.com - Primary database:
Office Fluid - Database ID:
6a8929bcfc6d44e9b13fee392ada9cf0(use this, not the pretty name, as thedatabaseparameter inkusto_query) - Automation/stress test database:
Office Fluid Test - Database ID:
742fa5a288b045e5beab1a2b8e445a71— containsoffice_fluid_ffautomation_*tables used for stress test / pipeline telemetry. These tables are NOT in the primary "Office Fluid" database. - Retention: ~28 days
- VPN: Required (Microsoft internal network)
- Access requirement: M365HeartbeatTenantUsers group membership
Quick Orientation
The primary tables are:
Office_Fluid_FluidRuntime_Error— all errors (first stop)Office_Fluid_FluidRuntime_Performance— timing eventsOffice_Fluid_FluidRuntime_Generic— everything elseunion Office_Fluid_FluidRuntime_*— all three at onceOwhLoads(stored function) — denominator for ICE/ACE error rate queries
Key correlation ID hierarchy: Session_Id/Data_hostCorrelationId → Data_pageCorrelationId → Data_docId → Data_containerId
Key deployment ring field: Loop_Audience (FluidRuntime tables), Release_AudienceGroup (OWH/QoS tables)
Using the Full Reference
Before writing any non-trivial Kusto query, read the full reference file:
references/kusto-query-reference.md
This reference contains:
- Part 1 — All tables, fields, correlation IDs, version fields, stored functions, partner database schemas (OneNote, OWA, Loop FFX, Video, Scriptor, HostTracker, automation)
- Part 2 — Query Cookbook with ~20 sections of ready-to-use queries (session lookup, error timecharts, breadth assessment, version correlation, ICE rate calculations, EU global queries, ODSP flight changes, etc.)
- Part 3 — Investigation playbook patterns (incoming partner incident, dataCorruptionError triage, ICE error rate, important notes)
- Part 4 — Additional query sections: FF bump tracking (5 queries), render reliability, Scriptor errors, Video telemetry (10+ queries), container reconnects /
WhyIsTheContainerStuck(), stress test automation (FindBuildErrors,DidSummarizerRecover,SummarizerView)
Key Reminders
- Always use absolute timestamps in IcM notes (not
ago()) so queries remain reproducible - Always filter
Data_stack !has '.goskope.com'andData_channelFactoryType !has '.myshn.net'in corruption queries to exclude known reverse proxies - The
hll()/dcount_hll(hll_merge(...))pattern is required for EU-compliant distinct user counts across clusters - For EU data, use
macro-expand force_remote = true officefluid_global as X (...) | summarize ... Loop_Audience(FluidRuntime) andRelease_AudienceGroup(OWH/QoS) are the same concept; filter== "Production"to exclude dogfood noise
04 同仓库更多 Skills
trigger-pipelines-for-copilot-pr
Trigger ADO pipelines for a Copilot-created PR by posting /azp run comments. Use when the user asks to trigger CI pipelines for a specific PR.
review
Review changes relative to a prior state, such as a diff, pull request, branch, commit, or working-tree changes. Use for change-focused code review and regression analysis. Do not use to assess an existing file, API, design, implementation, or other artifact without a comparison; if the request is ambiguous, ask whether the user wants a change review and what prior state to compare against.
review-pr-local
The authority on pulling a pull request — Azure DevOps or GitHub — into an isolated local worktree so a human can review it in their editor, and on posting human-controlled review comments back to the PR (ADO via the ado PR-thread MCP tools or the Azure DevOps REST API, GitHub via the gh CLI). Auto-detects the platform and all identifiers from the PR URL; not tied to any specific repository. The AI assists an interactive human review and only ever posts comments the human explicitly requests. If you find yourself checking out a PR branch over the user's own working tree, or posting AI-authored review prose the human did not ask for, invoke this skill instead.
policy-check
This skill should be used when the user asks to "run policy check", "check policy", "policy-check", or needs to validate package compliance. Provides guidance on running policy checks for specific packages or the entire repository.
pipeline-test-triage
Triage test failures in an Azure DevOps pipeline run for Fluid Framework. Use when the user shares an ADO build/pipeline URL or build ID and wants failures analyzed, when they ask "why did this pipeline fail", "summarize the test failures", "is this test flaky or a real bug", "compare these runs", or wants bugs filed for genuine failures. Covers the Real Service End to End Tests pipeline as the worked example but applies to any FF test pipeline.
fluid-release
Fluid Framework client release group — minor releases, patch releases, and post-release type test updates. Covers release prep, branching, version bumps, changelogs, release notes, and type test baselines. In autonomous mode, auto-detects state from the repo, attempts to execute, and falls back to a GitHub issue on failure. Triggers on "release", "do the release", "release status", version bump, release notes, changelog, release branch, or release engineering.