Skip to content

Revert "[Diagnostics] Add EventPipe Buffer Mode and EventFilter" - #55195

Merged
gewarren merged 1 commit into
mainfrom
revert-54631-eventpipe-non-lossy-buffering-docs
Jul 30, 2026
Merged

gewarren merged 1 commit into
mainfrom
revert-54631-eventpipe-non-lossy-buffering-docs

Conversation

@gewarren

@gewarren gewarren commented Jul 30, 2026 •

Copy link
Copy Markdown
Collaborator

@gewarren
gewarren requested review from a team and tommcdon as code owners July 30, 2026 18:53
Copilot AI review requested due to automatic review settings July 30, 2026 18:53
@dotnetrepoman dotnetrepoman Bot added this to the July 2026 milestone Jul 30, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR reverts recently added documentation for unreleased diagnostics features (EventPipe buffering mode and EventPipe provider event filters) across several diagnostics articles.

Changes:

  • Reverts EventPipeSessionConfiguration buffering mode and EventPipeProvider event filter API documentation.
  • Removes documentation for DOTNET_EventPipeBufferingMode/streaming startup session behavior and dotnet-trace --buffering-mode.
  • Updates exception documentation structure in the NETCore client API article and rolls back several ms.date values.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

File Description
docs/core/diagnostics/microsoft-diagnostics-netcore-client.md Reverts unreleased API surface docs (buffering mode, event filter) and adjusts exception docs and metadata.
docs/core/diagnostics/eventpipe.md Reverts unreleased environment variable docs for non-lossy buffering/streaming and updates metadata.
docs/core/diagnostics/dotnet-trace.md Reverts unreleased --buffering-mode option docs and updates metadata.
docs/core/diagnostics/dotnet-gcdump.md Reverts non-lossy buffering note and updates troubleshooting wording and metadata.
Comments suppressed due to low confidence (2)

docs/core/diagnostics/dotnet-gcdump.md:256

  • Docs style in this repo uses "might" (not "may") for possibility. Update this sentence to match the style guidance.
   `dotnet-gcdump` works by collecting a trace of events emitted by the garbage collector during an induced generation 2 collection. If the heap is sufficiently large, or there isn't enough memory to scale the eventing buffers, then the events required to reconstruct the heap graph from the trace may be dropped. In this case, to diagnose issues with the heap, it's recommended to collect a dump of the process.

docs/core/diagnostics/microsoft-diagnostics-netcore-client.md:593

  • Docs style in this repo uses "might" (not "may") for possibility. Update this sentence to match the style guidance.
This may be thrown when the command is not supported by either the library or the target process's runtime.

Comment thread docs/core/diagnostics/microsoft-diagnostics-netcore-client.md
Comment thread docs/core/diagnostics/dotnet-trace.md
Comment thread docs/core/diagnostics/eventpipe.md
Comment thread docs/core/diagnostics/dotnet-gcdump.md
@gewarren
gewarren enabled auto-merge (squash) July 30, 2026 19:06

@wadepickett wadepickett left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gewarren: Approved. A clean revert.

@gewarren
gewarren merged commit 6b96e84 into main Jul 30, 2026
13 checks passed
@gewarren
gewarren deleted the revert-54631-eventpipe-non-lossy-buffering-docs branch July 30, 2026 19:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants