Conversation
…as target org username
mshanemc
approved these changes
Feb 23, 2026
| const eventName = asString(event.eventName) ?? 'UNKNOWN'; | ||
| const enableO11y = asBoolean(event.enableO11y) ?? false; | ||
| const productFeatureId = asString(event.productFeatureId) ?? 'aJCEE0000000mHP4AY'; | ||
| const targetOrgUsername = asString(event.targetOrgUsername) ?? undefined; |
Contributor
There was a problem hiding this comment.
if you need them to eventually be string|undefined,
I'd use string? and undefined un the commandExecution stuff (instead of null) just to save some steps
mshanemc
approved these changes
Feb 24, 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.
create O11yReporter with getOrgConnection function when event has target org username so that PDP events are sent to the org's o11y endpoint.
Also, the o11y reporter that sends PDP events no longer batches since the 30 second interval would prevent node processes from exiting in short lived processes such as the CLI telemetry uploader.
Should address these issues:
forcedotcom/cli#3505
forcedotcom/cli#3506
@W-21306700@
NOTE: This requires forcedotcom/telemetry#476