skills.rest
microsoft
microsoftOFFICIAL
Explore all skills by this author →
Website𝕏@OpenAtMicrosoftGitHub

ff-oce-kusto

Writes and interprets Kusto queries for Fluid Framework telemetry investigation in the Office Fluid database.

4.9k|585|Updated Aug 22, 2019
Search Tags:#incident response#error investigation#KQL#kusto#fluid framework#Telemetry#office fluid
One-click install
npx skills add https://github.com/microsoft/FluidFramework --skill ff-oce-kusto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ff-oce-kusto
Source: https://github.com/microsoft/FluidFramework/tree/main/.agency/plugins/ff-oce/skills/ff-oce-kusto
Command: npx skills add https://github.com/microsoft/FluidFramework --skill ff-oce-kusto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Investigating Fluid Framework errors, performance regressions, and deployment issues requires deep knowledge of the Office Fluid Kusto database schema, correlation ID hierarchy, and partner-specific tables. This Skill provides the complete reference needed to write correct Kusto queries for telemetry investigations without memorizing dozens of tables and fields.

Core Features & Use Cases

  • Full Schema Reference: Documents all FluidRuntime tables (Error, Performance, Generic), OWH/QoS tables, and partner databases (OneNote, Outlook Web, Video, Scriptor, HostTracker) with field-level explanations.
  • Query Cookbook: Provides ready-to-use queries for session lookup, error timecharts, impact breadth assessment, version-to-error correlation, ICE/ACE rate calculation, and dataCorruptionError triage.
  • Investigation Playbooks: Covers partner incident response, FF bump tracking, render reliability, container reconnect analysis, and stress test automation queries.
  • Use Case: A partner reports elevated 429 throttling errors in Loop. Use this Skill to build a query that counts affected sessions and documents by container type, correlates errors with loader/runtime/driver versions, and identifies the regression window.

Quick Start

Ask the assistant to write a Kusto query that finds all Fluid errors for a given Session_Id or docId in the Office Fluid database over the past three days.

Frequently Asked Questions about ff-oce-kusto

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find all Fluid telemetry events for a session in Kusto?▼

Query the Office Fluid database with union Office_Fluid_FluidRuntime_* filtered by Session_Id or Data_hostCorrelationId. Sort by Event_Time and Event_Sequence to reconstruct the correct event order for the session.

How do I investigate a dataCorruptionError in Fluid Framework telemetry?▼

Filter Office_Fluid_FluidRuntime_Error by Data_errorType == 'dataCorruptionError', excluding reverse proxy noise with Data_stack !has '.goskope.com' and '.myshn.net'. Join distinct Data_docId values against DataCorruptionKnownDocIds to identify newly corrupted documents.

What is the difference between loaderVersion, runtimeVersion, and driverVersion?▼

Data_loaderVersion is tied to the host app build, Data_runtimeVersion is tied to the deployed container package, and Data_driverVersion reflects the ODSP driver. Correlating error spikes with each version identifies whether the host, container, or driver caused a regression.

Does querying the Office Fluid Kusto cluster require VPN?▼

Yes, the kusto.aria.microsoft.com cluster is only reachable on the Microsoft internal network and requires VPN plus M365HeartbeatTenantUsers group membership. If queries fail to connect, check VPN status first.

Why does the ffautomation wildcard query return no results?▼

The wildcard office_fluid_ffautomation* does not resolve in the Office Fluid Test database. Explicitly union the three tables: office_fluid_ffautomation_error, office_fluid_ffautomation_performance, and office_fluid_ffautomation_generic.

When should I not use this Fluid Kusto reference?▼

Do not use it for general Kusto questions unrelated to Fluid Framework telemetry. It is scoped specifically to the Office Fluid and Office Fluid Test databases and Fluid partner telemetry schemas.

Related Skills

Explore More Software Engineering Skills→
azaslonovazaslonov

skill-apim-skuv1-investigator

Investigate Azure API Management SKUv1 incidents using ICM, alerts, and Kusto telemetry.

Community
Advanced
unblockedunblocked
13

recommend-fixes

Validate incident fix options against historical remediation patterns.

Official
Advanced
thomasslobodathomassloboda

observability-troubleshooting

Correlates logs, traces, metrics, and dashboards to identify root causes of incidents.

Community
Intermediate
kortix-aikortix-ai

technical-sys-info

Explain Kortix runtime model, durability rules, paths, and service endpoints.

Official
Intermediate