microsoft / microsoft/DataFactory.MCP
Reliability & Observability - Query Execution Metrics
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 42
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
Issue: Add query execution metrics to response
Labels: enhancement, observability, priority:medium
Problem:
No visibility into query performance. Can't tell if a query is slow due to data volume, bad patterns, or service issues.
Proposed Solution:
Include in execute_query response:
- Execution time (ms)
- Rows scanned vs. returned
- Whether query folding occurred
Acceptance Criteria:
- Response includes
execution_time_ms - Response includes
rows_scannedandrows_returned - Response includes
query_foldedboolean (if detectable)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the execute_query entry point and its response model. Check how query execution exposes timing, scanned and returned row counts, and query folding detection; done means the response includes execution_time_ms, rows_scanned, rows_returned, and a query_folded boolean when detectable, with tests covering the fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100