azure-resource-health-diagnose

Solid

Analyze Azure resource health, diagnose issues from logs and telemetry, and create a remediation plan for identified problems.

AI & Automation 34,887 stars 4287 forks Updated today MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Azure Resource Health & Issue Diagnosis This workflow analyzes a specific Azure resource to assess its health status, diagnose potential issues using logs and telemetry data, and develop a comprehensive remediation plan for any problems discovered. ## Prerequisites - Azure MCP server configured and authenticated - Target Azure resource identified (name and optionally resource group/subscription) - Resource must be deployed and running to generate logs/telemetry - Prefer Azure MCP tools (`azmcp-*`) over direct Azure CLI when available ## Workflow Steps ### Step 1: Get Azure Best Practices **Action**: Retrieve diagnostic and troubleshooting best practices **Tools**: Azure MCP best practices tool **Process**: 1. **Load Best Practices**: - Execute Azure best practices tool to get diagnostic guidelines - Focus on health monitoring, log analysis, and issue resolution patterns - Use these practices to inform diagnostic approach and remediation recommendations ### Step 2: Resource Discovery & Identification **Action**: Locate and identify the target Azure resource **Tools**: Azure MCP tools + Azure CLI fallback **Process**: 1. **Resource Lookup**: - If only resource name provided: Search across subscriptions using `azmcp-subscription-list` - Use `az resource list --name <resource-name>` to find matching resources - If multiple matches found, prompt user to specify subscription/resource group - Gather detailed resource information: - Resource type and ...

Details

Author
github
Repository
github/awesome-copilot
Created
1 years ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category