Add V3 streaming event ingestion pipeline#2370
Draft
ejsmith wants to merge 11 commits into
Draft
Conversation
ejsmith
force-pushed
the
feature/v3-event-ingestion
branch
from
July 13, 2026 22:48
1a60290 to
b3ce174
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
HttpRequest.BodyReaderusing source-generated System.Text.Json metadataMicrosoft.OpenApi 2.7.5to remediate CVE-2026-49451 discovered during dependency validationAPI and compatibility
V3 is a new breaking-contract surface:
POST /api/v3/eventsPOST /api/v3/projects/{projectId}/eventsContent-Type: application/x-ndjsonThe V2 controller, payload formats, queued handoff, and response contract remain available and unchanged. V3 is disabled by default and can be rolled out by project or organization allowlist.
Verification
dotnet build Exceptionless.slnx --no-restore --disable-build-servers -m:1 -v:minimal— 0 warnings, 0 errorsgit diff --check— cleanRollout
Keep this PR in draft while reviewing the architecture and running the documented one-, two-, four-, and eight-instance load matrix against the intended Redis/Elasticsearch topology. Production activation remains a configuration-only, reversible step.
Closes #2368