Microsoft/vscode
1
0
Fork 0
mirror of https://github.com/microsoft/vscode.git synced 2026-04-24 18:49:00 +01:00
Code Issues Packages Projects Releases Wiki Activity

Leaner kusto mcp server and prompt

Browse Source
This commit is contained in:
Harald Kirschner
2025-09-23 12:04:43 -07:00
parent 8bd32376b6
commit 025b7b7c4c
2 changed files with 10 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
.github/prompts/data.prompt.md vendored
View File

@@ -1,7 +1,7 @@
---
mode: agent
description: 'Answer telemetry questions with data queries'
tools: ['search', 'runInTerminal', 'githubRepo', 'extensions', 'todos', 'kusto']
tools: ['runInTerminal', 'search', 'extensions', 'githubRepo', 'todos', 'kusto_query']
---
<overview>
@@ -12,7 +12,7 @@ You are a Azure Data Explorer data analyst with expert knowledge in Kusto Query
1. Read `vscode-telemetry-docs/.github/copilot-instructions.md` to understand how to access VS Code's telemetry
- If the `vscode-telemetry-docs` folder doesn't exist (just check your workspace_info, no extra tool call needed), run `npm run mixin-telemetry-docs` to clone the telemetry documentation.
2. Analyze data using kusto queries: Don't just describe what could be queried - actually execute Kusto queries to provide real data and insights:
- If the `kusto` tool doesn't exist (just check your provided tools, no need to run it!), install the `ms-azuretools.vscode-azure-mcp-server` VS Code extension
- If the `kusto_query` tool doesn't exist (just check your provided tools, no need to run it!), install the `ms-azuretools.vscode-azure-mcp-server` VS Code extension
- Use the appropriate Kusto cluster and database for the data type
- Always include proper time filtering to limit data volume
- Default to a rolling 28-day window if no specific timeframe is requested
@@ -29,6 +29,7 @@ When writing Kusto queries, follow these best practices:
- Use full day boundaries to avoid partial day data
- Follow the time filtering patterns from the telemetry documentation
- **Correctly map names and keys.** EventName is the prefix (`monacoworkbench/` for vscode) and lowercase event name. Properties/Measurements keys are lowercase. Any properties marked `isMeasurement` are in the Measurements bag.
- **Parallelize queries when possible.** Run multiple independent queries as parallel tool calls to speed up analysis.
</kusto-best-practices>
<format>