azmon-mirroredcatalogs-operations-cli

Onboard Azure Monitor telemetry into Microsoft Fabric and correlate it with business data.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/paulasilvatech/Fabric-Agentic-SDLC --skill azmon-mirroredcatalogs-operations-cli-paulasilvatech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: azmon-mirroredcatalogs-operations-cli
Source: https://github.com/paulasilvatech/Fabric-Agentic-SDLC/tree/main/.github/skills/azmon-mirroredcatalogs-operations-cli
Command: npx skills add https://github.com/paulasilvatech/Fabric-Agentic-SDLC --skill azmon-mirroredcatalogs-operations-cli-paulasilvatech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams running applications on Azure Monitor, Application Insights, or Log Analytics cannot easily connect operational telemetry to business outcomes like orders, revenue, or customer impact. This Skill guides the full onboarding of that telemetry into Microsoft Fabric as a Mirrored Catalog item and turns it into verified business-impact insights. ## Core Features & Use Cases - Mirrored Catalog onboarding: Walks through a strict 17-stage workflow covering Log Analytics workspace selection, identity validation, connection resolution (Service Principal or OAuth), Mirrored Catalog item creation, and external Delta table registration in an Eventhouse KQL database. - Business-impact correlation: Discovers business tables across Fabric data surfaces, verifies join keys (including identifiers hidden in dynamic Properties/CustomDimensions fields), and builds a confirmed correlation model with bins, metrics, and thresholds. - Dashboards and Operations Agents: Optionally generates a Real-Time (KQL) Dashboard and ready-to-paste Operations Agent instructions for automated business-impact alerting. - Use Case: An engineer asks whether a latency spike affected bookings. The Skill mirrors the App Insights workspace into Fabric, registers queryable external tables, finds a verified BookingId join, and produces an Operations Agent that alerts when error counts put revenue at risk. ## Quick Start Ask the assistant to onboard your Application Insights Log Analytics workspace into Microsoft Fabric and correlate the telemetry with your business data to measure impact on orders or revenue.

Frequently Asked Questions about azmon-mirroredcatalogs-operations-cli

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

FAQPage Schema
How do I onboard Azure Monitor data into Microsoft Fabric?▼

Use this Skill's staged workflow: select the Log Analytics workspace, choose a Fabric workspace, validate an identity, resolve a connection, and create a Mirrored Catalog item. The Skill then registers the mirrored tables as queryable external Delta tables in an Eventhouse KQL database.

How to correlate Application Insights telemetry with business data?▼

The Skill discovers business tables across Eventhouse, KQL databases, Warehouses, and Lakehouses, then verifies join keys against real data. It inspects dynamic fields like Properties and CustomDimensions for hidden identifiers such as BookingId or OrderId before falling back to time-window correlation.

Can I create an Azure Monitor OAuth connection through the Fabric API?▼

No, OAuth Azure Monitor connector creation is UI-guided only and must be done once in Fabric Manage Connections. The Skill detects and reuses existing OAuth connections, while Service Principal connector creation is fully automated.

Why is my mirrored table not queryable in the Eventhouse KQL database?▼

A OneLake shortcut alone only creates a storage link, not a queryable table. Each mirrored table must be registered as an external Delta table with a .create external table kind=delta command, then verified with external_table('<name>') | take 1.

Does this Skill support Service Principal authentication for Fabric?▼

Yes, Service Principal is the recommended identity and the default connection mode, supporting automated non-interactive connector create-or-reuse. Secrets must come from environment variables or Key Vault references and are never requested in chat.

When should I use eventhouse-cli instead of this Skill?▼

Use eventhouse-cli for general Eventhouse and KQL querying or authoring unrelated to Azure Monitor onboarding. This Skill is specifically for mirroring Azure Monitor telemetry into Fabric and building business-impact correlations, dashboards, and Operations Agents.