Skip to content

Fix/telemetry blank resultcode - #15516

Merged
Harini Malothu (HariniMalothu17) merged 6 commits into
microsoft:mainfrom
ssuraj2504:fix/telemetry-blank-resultcode
Jan 13, 2026
Merged

Fix/telemetry blank resultcode#15516
Harini Malothu (HariniMalothu17) merged 6 commits into
microsoft:mainfrom
ssuraj2504:fix/telemetry-blank-resultcode

Conversation

@ssuraj2504

@ssuraj2504Suraj Raykar (ssuraj2504) commented Jan 3, 2026

Copy link
Copy Markdown
Contributor

Description

This PR fixes an issue where telemetry command events could emit <blank> values for resultCode, which should always be populated.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)

Why

Telemetry dashboards were showing <blank> values for resultCode when the value was missing at runtime. This reduced the usefulness and accuracy of telemetry data. A fallback value ensures consistent reporting.

Resolves#14154

What

  • Added a fallback value ("Unknown") when resultCode is missing in command telemetry events.
  • Ensures telemetry dashboards no longer show <blank> entries for this field.

Screenshots

N/A (no UI changes)

Testing

No new tests were added. This change is limited to telemetry event construction and was validated by ensuring telemetry events always include a non-empty resultCode.

Changelog

Should this change be included in the release notes: Yes

Changelog entry:
Prevent telemetry command events from emitting blank resultCode values.

Microsoft Reviewers: Open in CodeFlow

@ssuraj2504

Copy link
Copy Markdown
ContributorAuthor

@ssuraj2504

Copy link
Copy Markdown
ContributorAuthor

@vineethkuttan

Copy link
Copy Markdown
Contributor

Harini Malothu (@HariniMalothu17) , Please review this change

@HariniMalothu17

Copy link
Copy Markdown
Contributor

Harini Malothu (@HariniMalothu17) , Please review this change

change looks good to me . Suraj Raykar (@ssuraj2504) please link the issue number with pr

@HariniMalothu17

Copy link
Copy Markdown
Contributor

/azp run

@azure-pipelines

Copy link
Copy Markdown
Contributor
Azure Pipelines successfully started running 2 pipeline(s).

@HariniMalothu17

Copy link
Copy Markdown
Contributor

Suraj Raykar (@ssuraj2504) please run yarn change from the root of the repo

@ssuraj2504

Copy link
Copy Markdown
ContributorAuthor

@vineethkuttan

Vineeth (vineethkuttan) commented Jan 7, 2026

Copy link
Copy Markdown
Contributor

Suraj Raykar (@ssuraj2504) update the PR description, with the below one. This important to update it to the release notes.

https://github.com/microsoft/react-native-windows/blob/main/.github/pull_request_template.md

check this PR for reference-> #15522

@ssuraj2504

Copy link
Copy Markdown
ContributorAuthor

Description

This PR fixes an issue where telemetry command events could emit <blank> values for resultCode, which should always be populated.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)

Why

Telemetry dashboards were showing <blank> values for resultCode when the value was missing at runtime. This reduced the usefulness and accuracy of telemetry data. A fallback value ensures consistent reporting.

Resolves #14154

What

  • Added a fallback value ("Unknown") when resultCode is missing in command telemetry events.
  • Ensures telemetry dashboards no longer show <blank> entries for this field.

Screenshots

N/A (no UI changes)

Testing

No new tests were added. This change is limited to telemetry event construction and was validated by ensuring telemetry events always include a non-empty resultCode.

Changelog

Should this change be included in the release notes: Yes

Changelog entry:
Prevent telemetry command events from emitting blank resultCode values.

@vineethkuttan

Copy link
Copy Markdown
Contributor

/azp run

@azure-pipelines

Copy link
Copy Markdown
Contributor
Azure Pipelines successfully started running 2 pipeline(s).

@vineethkuttan

Copy link
Copy Markdown
Contributor

/azp run PR

@azure-pipelines

Copy link
Copy Markdown
Contributor
Azure Pipelines successfully started running 1 pipeline(s).

@ssuraj2504

Copy link
Copy Markdown
ContributorAuthor

Fixed Prettier formatting issues in telemetry.ts.
Linting should now pass.

@vineethkuttan

Copy link
Copy Markdown
Contributor

/azp run PR

@azure-pipelines

Copy link
Copy Markdown
Contributor
Azure Pipelines successfully started running 1 pipeline(s).

@ssuraj2504

Copy link
Copy Markdown
ContributorAuthor

All checks are passing and feedback has been addressed.
Ready for code owner review when convenient. Thanks!

@vineethkuttan

Copy link
Copy Markdown
Contributor

/azp run PR

@azure-pipelines

Copy link
Copy Markdown
Contributor
Azure Pipelines successfully started running 1 pipeline(s).

@HariniMalothu17

Copy link
Copy Markdown
Contributor

/azp run PR

@azure-pipelines

Copy link
Copy Markdown
Contributor
Azure Pipelines successfully started running 1 pipeline(s).

@HariniMalothu17
Harini Malothu (HariniMalothu17) merged commit b0aba40 into microsoft:mainJan 13, 2026
30 checks passed
@ssuraj2504
Suraj Raykar (ssuraj2504) deleted the fix/telemetry-blank-resultcode branch January 14, 2026 11:17
Sign up for freeto 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.

Telemetry instances displaying <blank> in multiple fields

3 participants

@ssuraj2504@vineethkuttan@HariniMalothu17