通过命令行创建与管理 Eventhouse 的 KQL 架构、导入与策略配置
复制安装指令,让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "eventhouse-authoring-cli" 技能: 1. 下载 https://raw.githubusercontent.com/microsoft/skills-for-fabric/main/plugins/fabric-skills/skills/eventhouse-authoring-cli/SKILL.md 2. 保存为 ~/.claude/skills/eventhouse-authoring-cli/SKILL.md 3. 装好后重载技能,告诉我可以用了
请为 Fabric Eventhouse 生成 CLI 命令:创建名为 telemetry 的表,包含 deviceId:string、ts:datetime、temperature:real 三列;再创建一个函数 recent_hot_devices,返回最近 1 小时温度高于 80 的设备。
一组可执行的 KQL 管理命令或脚本,用于创建表结构和查询函数。
帮我生成 Eventhouse 的 CLI 命令:为 telemetry 表创建 JSON ingestion mapping,把字段 id、timestamp、temp 映射到 deviceId、ts、temperature,并从 Azure Storage 指定路径批量导入数据。
包含映射定义与导入命令的脚本,可直接用于搭建数据接入流程。
请输出 KQL 管理脚本:将 telemetry 表保留期设置为 30 天、启用合适缓存策略,并创建一个按小时聚合平均温度的物化视图。
一份完整的策略与物化视图配置脚本,便于部署到 Eventhouse。
Update Check — ONCE PER SESSION (mandatory) The first time this skill is used in a session, run the check-updates skill before proceeding.
- GitHub Copilot CLI / VS Code: invoke the
check-updatesskill.- Claude Code / Cowork / Cursor / Windsurf / Codex: compare local vs remote package.json version.
- Skip if the check was already performed earlier in this session.
CRITICAL NOTES
- To find the workspace details (including its ID) from workspace name: list all workspaces and, then, use JMESPath filtering
- To find the item details (including its ID) from workspace ID, item type, and item name: list all items of that type in that workspace and, then, use JMESPath filtering
| Task | Reference | Notes |
|---|---|---|
| Finding Workspaces and Items in Fabric | COMMON-CLI.md § Finding Workspaces and Items in Fabric |
| Mandatory — READ link first [needed for workspace/item ID resolution] |
| Fabric Topology & Key Concepts | COMMON-CORE.md § Fabric Topology & Key Concepts | Hierarchy, Finding Things in Fabric |
| Environment URLs | COMMON-CORE.md § Environment URLs | KQL Cluster URI, KQL Ingestion URI |
| Authentication & Token Acquisition | COMMON-CORE.md § Authentication & Token Acquisition | Wrong audience = 401; KQL audience: kusto.kusto.windows.net |
| Core Control-Plane REST APIs | COMMON-CORE.md § Core Control-Plane REST APIs | List Workspaces, List Items, Item Creation |
| Pagination | COMMON-CORE.md § Pagination |
| Long-Running Operations (LRO) | COMMON-CORE.md § Long-Running Operations (LRO) |
| Rate Limiting & Throttling | COMMON-CORE.md § Rate Limiting & Throttling |
| OneLake Data Access | COMMON-CORE.md § OneLake Data Access | Requires storage.azure.com token, not Fabric token |
| Job Execution | COMMON-CORE.md § Job Execution |
| Capacity Management | COMMON-CORE.md § Capacity Management |
| Gotchas & Troubleshooting | COMMON-CORE.md § Gotchas & Troubleshooting |
| Best Practices | COMMON-CORE.md § Best Practices |
| Tool Selection Rationale | COMMON-CLI.md § Tool Selection Rationale |
| Authentication Recipes | COMMON-CLI.md § Authentication Recipes | az login flows and token acquisition |
Fabric Control-Plane API via az rest | COMMON-CLI.md § Fabric Control-Plane API via az rest | Always pass --resource https://api.fabric.microsoft.com or az rest fails |
| Pagination Pattern | COMMON-CLI.md § Pagination Pattern |
| Long-Running Operations (LRO) Pattern | COMMON-CLI.md § Long-Running Operations (LRO) Pattern |
OneLake Data Access via curl | COMMON-CLI.md § OneLake Data Access via curl | Use curl not az rest (different token audience) |
…