azurebackup-telemetry-report

Generate weekly Azure Backup MCP telemetry reports from Kusto events with 3-way error classification.

3.6k|579|Updated Apr 9, 2025
One-click install
npx skills add https://github.com/microsoft/mcp --skill azurebackup-telemetry-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azurebackup-telemetry-report
Source: https://github.com/microsoft/mcp/tree/main/tools/Azure.Mcp.Tools.AzureBackup/skills/azurebackup-telemetry-report
Command: npx skills add https://github.com/microsoft/mcp --skill azurebackup-telemetry-report

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill generates weekly, Outlook-ready telemetry reports for Azure Backup MCP tools by turning Kusto event data into actionable success metrics and a structured error analysis.

Core Features & Use Cases

  • Weekly Kusto telemetry reporting: Queries AzureDevExp on the ddazureclients Kusto cluster and summarizes tool-call outcomes for the last 7 days.
  • 3-way error classification: Categorizes failures into Customer (4xx), Azure Service (Azure SDK/API/auth), and MCP Tool Bug (tool code exceptions).
  • Week-over-week comparison: Computes key KPIs by contrasting this week vs the previous week and highlights deltas.
  • Git correlation: Links telemetry trends to merged PRs, shipped releases, and code changes within the Azure Backup tools area.
  • Investigation-ready artifacts: Produces an Outlook-compatible HTML report plus a second styled HTML output for stakeholders.

Quick Start

Use the azurebackup-telemetry-report skill to generate the Azure Backup MCP weekly telemetry report for the current 7-day period.

Frequently Asked Questions about azurebackup-telemetry-report

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

FAQPage Schema
How do I generate a weekly Azure Backup telemetry report from Kusto data?

Generate weekly Azure Backup telemetry reports by querying Kusto event data from the AzureDevExp database to summarize tool-call outcomes for the last 7 days. The report calculates success metrics and classifies failures for operational monitoring.

How does the 3-way error classification model work for Azure Backup MCP tool calls?

The 3-way error classification model categorizes Azure Backup MCP tool-call failures into Customer errors (4xx), Azure Service errors (SDK/API/auth issues), and MCP Tool Bugs (code exceptions). This structure helps triage root causes across weekly releases.

Do I need Kusto access to produce the Azure Backup telemetry report?

Yes, you need Kusto access to ddazureclients.kusto.windows.net with AzureDevExp permissions and the getAzureMcpEvents_ToolCalls function. You also need Git context from the microsoft/mcp repository to correlate telemetry trends with merged PRs.

Can I compare week-over-week success rate changes for Azure Backup MCP tools?

Yes, the telemetry report computes key KPIs by contrasting the current week versus the previous week. It highlights deltas in success rate changes, error hotspots, and performance percentiles to support stakeholder reporting.

What format does the weekly telemetry report output for stakeholders?

The weekly telemetry report produces an Outlook-compatible HTML report plus a second styled HTML output for stakeholders. These investigation-ready artifacts link Kusto telemetry trends to shipped releases and code changes.

Why do my Azure Backup MCP tool-call success metrics fluctuate across weekly releases?

Success metrics fluctuate due to merged PRs, shipped releases, and code changes within the Azure Backup tools area. The report correlates these Git context trends with Kusto telemetry data to explain shifts in tool-call outcomes.