ExecutionSummaryPlugin: internal log messages leak into the report as an "Unknown" category
維護者通常 1 天內回覆
評估
這個 Issue 還沒有評估資料。
描述
Description
ExecutionSummaryPlugin reports (both groupBy: url and groupBy: messageType) contain an Unknown category filled with internal or noise log entries. These include request timestamps, messages from plugins that skipped the request (for example, No matching mock response found), the request line itself, and processing markers. None of these help a user who's reading the summary.
Cause
GetGroupedByUrlData and GetGroupedByMessageTypeData in DevProxy.Plugins/Reporting/ExecutionSummaryPlugin.cs filter out only MessageType.InterceptedResponse. GetReadableMessageTypeForSummary maps every other unhandled MessageType to "Unknown" (_ => "Unknown"). That includes Normal, Skipped, Processed, FinishedProcessingRequest, and Timestamp. The same mapping exists in ExecutionSummaryPluginReportBase.cs.
Repro (Dev Proxy v4.0.0)
- Configure
MockResponsePlugin+ExecutionSummaryPlugin+JsonReporterforhttps://jsonplaceholder.typicode.com/*, with a mock for/usersonly. - Record, call
GET /usersonce andGET /poststwice, then stop recording. - Inspect
ExecutionSummaryPlugin_JsonReporter.json.
groupBy: url output (excerpt):
{
"GET https://jsonplaceholder.typicode.com/users": {
"Unknown": {
"2026-11-05T10:41:13.1151430+00:00": 1,
"GET https://jsonplaceholder.typicode.com/users": 1
},
"Requests mocked": { "200 https://jsonplaceholder.typicode.com/users": 1 }
},
"GET https://jsonplaceholder.typicode.com/posts": {
"Unknown": {
"No matching mock response found": 2,
"GET https://jsonplaceholder.typicode.com/posts": 2
},
"Requests passed through": { "Passed through": 2 }
}
}
Expected
Exclude internal message types (Timestamp, Skipped, Processed, FinishedProcessingRequest, and likely Normal) from the summary. Alternatively, map them to meaningful categories so that Unknown doesn't appear in normal runs.
Related
Found while documenting the report shape for dotnet/dev-proxy#2079 (docs PR: MicrosoftDocs/microsoft-cloud-pr#767). Once this is fixed, remove the Unknown row and examples from executionsummaryplugin.md.
- 主要語言
- C#
- 星號
- 841
- 分支
- 90
- 平均合併
- 2 天 10 小時
- 30 天內合併 PR
- 63
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
dotnet/dev-proxy 的其他 Issue
-
Add `devproxy cert export` to write the root certificate to a file可能已有人在做 @waldekmastykarz 於 1 天前認領。 未關閉work in progress
dotnet/dev-proxy#2085 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Update "Use Dev Proxy with Node.js" for native `fetch` proxy support and certificate trust可能已有人在做 @waldekmastykarz 於 1 天前認領。 未關閉documentation work in progress
dotnet/dev-proxy#2084 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Reference the API-inventory preset from the CI/CD and Record docs可能已有人在做 @waldekmastykarz 於 1 天前認領。 未關閉documentation work in progress
dotnet/dev-proxy#2083 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Document the shutdown contract for `POST /proxy/stopProxy`可能已有人在做 @waldekmastykarz 於 1 天前認領。 未關閉documentation work in progress
dotnet/dev-proxy#2081 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
`devproxy --detach` blocks callers that capture its output可能已有人在做 @waldekmastykarz 於 1 天前認領。 未關閉work in progress
dotnet/dev-proxy#2080 · 已指派 1 人 ·
維護者通常 1 天內回覆
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 77/100
BEagle1984/silverback#280 ·
-
難度 2/5 1-3 小時 新手友好度 63/100
-
Status: Needs Triage
難度 2/5 1-3 小時 新手友好度 66/100
PSAppDeployToolkit/PSAppDeployToolkit#2392 ·
維護者通常 1 天內回覆
-
Playground selection bar: comes back after Apply or scrolling while focus is in the Markdown pane未關閉
難度 2/5 1-3 小時 新手友好度 82/100
sillsdev/SIL.TextEditing#175 ·
維護者通常 1 天內回覆
-
needs attention untriaged
難度 2/5 1-3 小時 新手友好度 78/100
AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet#3666 ·
維護者通常 3 天內回覆