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

Aberta
  • Algo errado?
#2,097 0 comentários 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 1 dia

@waldekmastykarz já está trabalhando nisso.

Desde 5/11/2026.

  • #2088 de @waldekmastykarz — aberto

Avaliação

Esta issue ainda não foi avaliada.

Descrição

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.

Linguagem predominante
C#
Estrelas
841
Forks
90
Merge médio
2d 10h
PRs com merge (30d)
63

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de dotnet/dev-proxy

Todas as issues de dotnet/dev-proxy

Issues semelhantes

Mais issues de C#

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.