10 actions in 6 pieces of software · ranked by words, meaning and measured trust · 652 ms
libraryAzure/azure-kusto-pythonrecord4,168,879 downloads/month
- kusto
- azure
- ingest
- analytics
- data
skillmicrosoft/azure-skillsrecord
- 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.
- azure-kusto
skillmicrosoft/azure-skillsrecord
- azure-kusto-irql
Compose IRQL (Incident Response Query Language) queries for Kusto cybersecurity investigations. Translates natural language hunting questions into composable IRQL pipelines using Get_*, Extract_*, and Enrich_* functions. WHEN: IRQL query, security hunt, threat hunting KQL, incident response query, c
- azure-kusto-irql
skillmicrosoft/azure-skillsrecord
- azure-cost
Azure cost management: query costs, forecast spending, optimize to reduce waste. WHEN: "Azure costs", "Azure bill", "cost breakdown", "how much am I spending", "forecast spending", "optimize costs", "reduce spending", "orphaned resources", "rightsize VMs", "cost spike", "reduce storage costs", "AKS
- azure-cost
skillmicrosoft/azure-skillsrecord
- azure-cost-optimization
Identify Azure cost savings from usage and spending data. USE FOR: optimize Azure costs, reduce Azure spending/expenses, analyze Azure costs, find cost savings, generate cost optimization report, identify orphaned resources to delete, rightsize VMs, reduce waste, optimize Redis costs, optimize stora
- azure-cost-optimization
skillmicrosoft/GitHub-Copilot-for-Azurerecord
- azure-cost-optimization
Identify and quantify cost savings across Azure subscriptions by analyzing actual costs, utilization metrics, and generating actionable optimization recommendations. USE FOR: optimize Azure costs, reduce Azure spending, analyze Azure costs, find cost savings, generate cost optimization report, find
- azure-cost-optimization
Labels are the instruments' verdict and are never changed by ranking. Agents and robots get this same answer as JSON at /api/v1/find?q=…&answer=1 and through the MCP server.