azure-kusto
Query and analyze data in Azure Data Explorer (Kusto/ADX) using KQL for log analytics, telemetry, and time series analysis. WHEN: KQL queries, Kusto database queries, Azure Data Explorer, ADX clusters, log analytics, time series data, IoT telemetry, anomaly detection.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 267
01 前言 Front Matter
- name
- azure-kusto
- license
- MIT
- metadata
- { "author": "Microsoft", "version": "1.2.2" }
- description
- Query and analyze data in Azure Data Explorer (Kusto/ADX) using KQL for log analytics, telemetry, and time series analysis. WHEN: KQL queries, Kusto database queries, Azure Data Explorer, ADX clusters, log analytics, time series data, IoT telemetry, anomaly detection.
02 资源文件 10
- 资产文件assets/dot_chezmoidata.yaml.template6.5 KB
- 资产文件assets/dot_chezmoiignore.template4.5 KB
- 资产文件assets/README.md.template6.1 KB
- 参考文档references/chezmoi-commands.md12.1 KB
- 参考文档references/ignore-patterns.md7.8 KB
- 参考文档references/security-checklist.md7.8 KB
- 参考文档references/template-examples.md11.0 KB
- 脚本scripts/executable_check_secrets.py5.8 KB
- 脚本scripts/executable_generate_chezmoiignore.py9.3 KB
- 脚本scripts/executable_init_chezmoi_repo.sh6.3 KB
03 SKILL.md 正文
Azure Data Explorer (Kusto) Query & Analytics
Execute KQL queries and manage Azure Data Explorer resources for fast, scalable big data analytics on log, telemetry, and time series data.
Overview
This skill enables querying and managing Azure Data Explorer (Kusto), a fast and highly scalable data exploration service optimized for log and telemetry data. Azure Data Explorer provides sub-second query performance on billions of records using the Kusto Query Language (KQL).
Key capabilities:
- Query Execution: Run KQL queries against massive datasets
- Schema Exploration: Discover tables, columns, and data types
- Resource Management: List clusters and databases
- Analytics: Aggregations, time series, anomaly detection, machine learning
Core Workflow
- Discover Resources: List available clusters and databases in subscription. If the target table's location is unknown and multiple candidate clusters, databases, or Log Analytics workspaces exist, batch the search (see Pattern 6) and only report "not found" after all candidates are checked.
- Explore Schema: Retrieve table structures to understand data model
- Query Data: Execute KQL queries for analysis, filtering, aggregation
- Analyze Results: Process query output for insights and reporting
Query Patterns
Pattern 1: Basic Data Retrieval
Fetch recent records from a table with simple filtering.
Example KQL:
Events
| where Timestamp > ago(1h)
| take 100
Use for: Quick data inspection, recent event retrieval
Pattern 2: Aggregation Analysis
Summarize data by dimensions for insights and reporting.
Example KQL:
Events
| summarize count() by EventType, bin(Timestamp, 1h)
| order by count_ desc
Use for: Event counting, distribution analysis, top-N queries
Pattern 3: Time Series Analytics
Analyze data over time windows for trends and patterns.
Example KQL:
Telemetry
| where Timestamp > ago(24h)
| summarize avg(ResponseTime), percentiles(ResponseTime, 50, 95, 99) by bin(Timestamp, 5m)
| render timechart
Use for: Performance monitoring, trend analysis, anomaly detection
Pattern 4: Join and Correlation
Combine multiple tables for cross-dataset analysis.
Example KQL:
Events
| where EventType == "Error"
| join kind=inner (
Logs
| where Severity == "Critical"
) on CorrelationId
| project Timestamp, EventType, LogMessage, Severity
Use for: Root cause analysis, correlated event tracking
Pattern 5: Schema Discovery
Explore table structure before querying.
Tools: kusto_table_schema_get
Use for: Understanding data model, query planning
Pattern 6: Batch Search Across Candidate Sources
When a table's location is unknown and there are several candidate clusters, databases, or workspaces, batch read-only metadata discovery instead of querying candidates one at a time. List tables in each candidate database or workspace and match the exact table name before querying data.
After confirming which sources contain the table, query those sources together when needed:
union workspace('ws1').Requests, workspace('ws2').Requests
| take 1
Use for: Locating a table among many candidate resources without confusing an empty result with a missing table
Key Data Fields
When executing queries, common field patterns:
- Timestamp: Time of event (datetime) - use
ago(),between(),bin()for time filtering - EventType/Category: Classification field for grouping
- CorrelationId/SessionId: For tracing related events
- Severity/Level: For filtering by importance
- Dimensions: Custom properties for grouping and filtering
Result Format
Query results include:
- Columns: Field names and data types
- Rows: Data records matching query
- Statistics: Row count, execution time, resource utilization
- Visualization: Chart rendering hints (timechart, barchart, etc.)
KQL Best Practices
? Query Patterns:
- Use
summarizefor aggregations instead ofcount()alone - Use
bin()for time bucketing in time series - Use
projectto select only needed columns - Use
extendto add calculated fields
? Common Functions:
ago(timespan): Relative time (ago(1h), ago(7d))between(start .. end): Range filteringstartswith(),contains(),matches regex: String filteringparse,extract: Extract values from stringspercentiles(),avg(),sum(),max(),min(): Aggregations
Best Practices
- Filter early with time range filters to optimize query performance and use indexed columns first
- Use
takeorlimitfor exploratory queries to avoid large result sets - Leverage
summarizefor aggregations instead of client-side processing - Store frequently-used queries as functions in the database
- Use materialized views for repeated aggregations
- Monitor query performance and resource consumption
- Apply data retention policies to manage storage costs
- Use streaming ingestion for real-time analytics (< 1 second latency)
- Integrate with Azure Monitor for operational insights
MCP Tools Used
| Tool | Purpose |
|---|---|
kusto_cluster_list |
List all Azure Data Explorer clusters in a subscription |
kusto_database_list |
List all databases in a specific Kusto cluster |
kusto_query |
Execute KQL queries against a Kusto database |
kusto_table_schema_get |
Retrieve schema information for a specific table |
Required Parameters:
subscription: Azure subscription ID or display namecluster: Kusto cluster name (e.g., "mycluster")database: Database namequery: KQL query string (for query operations)table: Table name (for schema operations)
Optional Parameters:
resource-group: Resource group name (for listing operations)tenant: Azure AD tenant ID
Fallback Strategy: Azure CLI Commands
If Azure MCP Kusto tools fail, timeout, or are unavailable, use Azure CLI commands as fallback.
CLI Command Reference
| Operation | Azure CLI Command |
|---|---|
| List clusters | az kusto cluster list --resource-group <rg-name> |
| List databases | az kusto database list --cluster-name <cluster> --resource-group <rg-name> |
| Show cluster | az kusto cluster show --name <cluster> --resource-group <rg-name> |
| Show database | az kusto database show --cluster-name <cluster> --database-name <db> --resource-group <rg-name> |
KQL Query via Azure CLI
For queries, use the Kusto REST API or direct cluster URL:
az rest --method post \
--url "https://<cluster>.<region>.kusto.windows.net/v1/rest/query" \
--body "{ \"db\": \"<database>\", \"csl\": \"<kql-query>\" }"
When to Fallback
Switch to Azure CLI when:
- MCP tool returns timeout error (queries > 60 seconds)
- MCP tool returns "service unavailable" or connection errors
- Authentication failures with MCP tools
- Empty response when database is known to have data
Common Issues
- Access Denied: Verify database permissions (Viewer role minimum for queries)
- Query Timeout: Optimize query with time filters, reduce result set, or increase timeout
- Syntax Error: Validate KQL syntax - common issues: missing pipes, incorrect operators
- Empty Results: Check time range filters (may be too restrictive), verify table name
- Table Location Unknown: Use Pattern 6 to batch-search all candidate sources before concluding the data does not exist
- Cluster Not Found: Check cluster name format (exclude ".kusto.windows.net" suffix)
- High CPU Usage: Query too broad - add filters, reduce time range, limit aggregations
- Ingestion Lag: Streaming data may have 1-30 second delay depending on ingestion method
Use Cases
- Log Analytics: Application logs, system logs, audit logs
- IoT Analytics: Sensor data, device telemetry, real-time monitoring
- Security Analytics: SIEM data, threat detection, security event correlation
- APM: Application performance metrics, user behavior, error tracking
- Business Intelligence: Clickstream analysis, user analytics, operational KPIs
04 同仓库更多 Skills
azure-advisor-cost-optimization
Analyze Azure Advisor Cost/IdleResources findings and prevalidate deletion safety, including Service Groups. WHEN: "find unused Azure resources", "what resources am I paying for but no longer using", "idle-resource savings", "historical idle-resource savings", "are these idle resources safe to delete". Generic Cost, other subcategories, and cross-category requests use azure-advisor.
python-appservice-deploy
Deploy Python (Flask/Django/FastAPI) code to Azure App Service Linux. WHEN: "Flask App Service", "Django App Service", "FastAPI App Service", "deploy Python to App Service". DO NOT USE FOR: Container Apps, Functions, non-Python, Terraform/Bicep/IaC, full infra — use azure-prepare.
preset
Intelligently deploys Azure OpenAI models to optimal regions by analyzing capacity across all available regions. Automatically checks current region first and shows alternatives if needed. USE FOR: quick deployment, optimal region, best region, automatic region selection, fast setup, multi-region capacity check, high availability deployment, deploy to best location. DO NOT USE FOR: custom SKU selection (use customize), specific version selection (use customize), custom capacity configuration (use customize), PTU deployments (use customize).
customize
Interactive guided deployment flow for Azure OpenAI models with full customization control. Step-by-step selection of model version, SKU (GlobalStandard/Standard/ProvisionedManaged), capacity, RAI policy (content filter), and advanced options (dynamic quota, priority processing, spillover). USE FOR: custom deployment, customize model deployment, choose version, select SKU, set capacity, configure content filter, RAI policy, deployment options, detailed deployment, advanced deployment, PTU deployment, provisioned throughput. DO NOT USE FOR: quick deployment to optimal region (use preset).
capacity
Discovers available Azure OpenAI model capacity across regions and projects. Analyzes quota limits, compares availability, and recommends optimal deployment locations based on capacity requirements. USE FOR: find capacity, check quota, where can I deploy, capacity discovery, best region for capacity, multi-project capacity search, quota analysis, model availability, region comparison, check TPM availability. DO NOT USE FOR: actual deployment (hand off to preset or customize after discovery), quota increase requests (direct user to Azure Portal), listing existing deployments.
deploy-model
Unified Azure OpenAI model deployment skill with intelligent intent-based routing. Handles quick preset deployments, fully customized deployments (version/SKU/capacity/RAI policy), and capacity discovery across regions and projects. USE FOR: deploy model, deploy gpt, create deployment, model deployment, deploy openai model, set up model, provision model, find capacity, check model availability, where can I deploy, best region for model, capacity analysis. DO NOT USE FOR: listing existing deployments (use foundry_models_deployments_list MCP tool), deleting deployments, agent creation (use agent/create), project creation (use project/create).