APIGOV-31452 - Send New Insights Event Formats#1040
Draft
sbolosan wants to merge 25 commits into
Draft
Conversation
…rom the API server
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
vivekschauhan
previously approved these changes
May 26, 2026
sbolosan
requested review from
alrosca,
dfeldick,
dgghinea and
jcollins-axway
as code owners
Collaborator
|
we should hold this until we get the last piece of the puzzle in the event |
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
3 participants
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.
Delivers the SDK changes needed to produce metric v3 and transaction v2 Insights event formats.
Transaction events now emit the correct versioned InsightsEvent envelope for both leg and summary events, with the right field structure, owner information, and reporter block that analytics expects.
Metric events are updated to v3 —
The AccessRequest cache loading was updated so owner data from embedded references is always present at startup and on watch events, ensuring agents have what they need to populate owner fields correctly.