ExecutionSummaryPlugin: internal log messages leak into the report as an "Unknown" category

Aperta
  • Qualcosa non va?
#2,097 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@waldekmastykarz ci sta già lavorando.

Dal 5/11/2026.

  • #2088 di @waldekmastykarz — aperta

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

bug work in progress

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)

  1. Configure MockResponsePlugin + ExecutionSummaryPlugin + JsonReporter for https://jsonplaceholder.typicode.com/*, with a mock for /users only.
  2. Record, call GET /users once and GET /posts twice, then stop recording.
  3. 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.

Lingua principale
C#
Stelle
841
Fork
90
Merge medio
2g 10h
PR unite (30g)
63

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di dotnet/dev-proxy

Tutte le issue di dotnet/dev-proxy

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.