fix: @W-21215399 - send only caller attributes in sendTelemetryEventWithSchema#472
Merged
smuduganti-sf merged 1 commit intomainfrom Feb 10, 2026
Merged
Conversation
shetzel
approved these changes
Feb 9, 2026
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
2 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.
What does this PR do?
Update the existing sendTelemetryEventWithSchema implementation so it sends only the caller-provided attributes. The reporter must not add eventName, common properties, or any other properties to the payload.
scope :
This method doesn’t appear to have consumers yet, so this is treated as additive.
The schema is the O11y encoding schema (e.g. from the o11y_schema package), not JSON Schema,
so this library does not derive or run validation here. Callers should validate attributes (e.g. with zod) before calling, using the same schema context they use when importing the schema.
What issues does this PR fix or reference?
@W-21215399@