Skip to content

feat: set branch in same state as it used to be#27450

Draft
MarioJGMsoft wants to merge 1 commit into
microsoft:mainfrom
MarioJGMsoft:marioja/eventTagging
Draft

feat: set branch in same state as it used to be#27450
MarioJGMsoft wants to merge 1 commit into
microsoft:mainfrom
MarioJGMsoft:marioja/eventTagging

Conversation

@MarioJGMsoft
Copy link
Copy Markdown
Contributor

Description

This PR is a follow up to #27126; it tags high volume FluidFramework telemetry events as LogLevel.info. The goal is to let clients safely filter out info-tagged events without losing the signal needed to diagnose Fluid issues.

Events were selected by observed telemetry volume and span both generic and performance events. For consumers today, the only observable difference is that tagged events now carry logLevel: "info" on their payload - no filtering or delivery behavior changes were made.

Reviewer Guidance

The review process is outlined on this wiki page.

  • Each taggeed event has a PR comment specifying which event is being marked as info. The authors have been identified via git blame and tagged on the corresponding PR comment - please confirm info is correct for events that you have context on. If it is correct, please resolve the comment to know that I can go forward with the change.
  • If you don't have context on the event, please point me to who could know more about the event.
  • If you see an event in the diff you believe should remain untagged, flag it.
  • With the addition of the LogLevel.info parameter the formatting for various pieces of the code was updated. I highly recommend turning on the hide whitespace changes option when reviewing this PR.

Fixes: AB#52417

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 1, 2026

Hi! Thank you for opening this PR. Want me to review it?

Based on the diff (606 lines, 14 files), I've queued these reviewers:

  • Correctness — logic errors, race conditions, lifecycle issues
  • Security — vulnerabilities, secret exposure, injection
  • API Compatibility — breaking changes, release tags, type design
  • Performance — algorithmic regressions, memory leaks
  • Testing — coverage gaps, hollow tests

How this works

  • Adjust the reviewer set by ticking/unticking boxes above. Reviewer toggles alone don't trigger anything.

  • Tick Start review below to dispatch the review fleet.

  • After review finishes, tick Start review again to request another run — it auto-resets after each dispatch.

  • This comment updates as new commits land; your reviewer selections are preserved.

  • Start review

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.

1 participant