Skip to content

Conversation

HariniMalothu17
Copy link
Contributor

@HariniMalothu17 HariniMalothu17 commented Sep 13, 2025

Description

Changed telemetry test property key from deviceId to localId to align with telemetry transmission naming conventions.

  • In telemetry envelopes, the device identifier is transmitted as localId (in envelope.ext.device.localId)
  • Using localId as the property key creates consistency between storage and transmission naming

Type of Change

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

Why

Our telemetry was populating device identifier as deviceId

  • However, telemetry transmission protocol requires ext.device.localId to be populated
  • Missing localId field prevented Collector from properly inferring device.id
  • Result: Kusto database receives telemetry events with no device identification

Resolves [Add Relevant Issue Here]

What

Changed telemetry test property key from deviceId to localId to align with telemetry transmission naming conventions.

Screenshots

Add any relevant screen captures here from before or after your changes.

Testing

image

Changelog

Should this change be included in the release notes: no

Add a brief summary of the change to use in the release notes for the next release.

Microsoft Reviewers: Open in CodeFlow

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: Author Feedback The issue/PR needs activity from its author (label drives bot activity) label Sep 16, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot removed the Needs: Author Feedback The issue/PR needs activity from its author (label drives bot activity) label Sep 17, 2025
@HariniMalothu17
Copy link
Contributor Author

@jonthysell I have resolved all your comments.Please review

Sign up for free to 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.

2 participants