You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ExecutionSummaryPlugin: internal log messages leak into the report as an "Unknown" category #2097
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 + JsonReporter for https://jsonplaceholder.typicode.com/*, with a mock for /users only.
Record, call GET /users once and GET /posts twice, then stop recording.
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 #2079 (docs PR: MicrosoftDocs/microsoft-cloud-pr#767). Once this is fixed, remove the Unknown row and examples from executionsummaryplugin.md.
Activity