Skip to content

Enhance telemetry tracking and data privacy in migration process#3087

Open
sevoku wants to merge 4 commits into
mainfrom
dev/sevoku/fix-migration-telemetry
Open

Enhance telemetry tracking and data privacy in migration process#3087
sevoku wants to merge 4 commits into
mainfrom
dev/sevoku/fix-migration-telemetry

Conversation

@sevoku

@sevoku sevoku commented Jun 1, 2026

Copy link
Copy Markdown
Member

This pull request enhances telemetry and error reporting in the migration panel, with a focus on improved masking of sensitive information, more structured error context, and clearer telemetry for schema conversion steps. It also refines which environment details are logged during provisioning.

Telemetry and error reporting improvements:

  • Expanded masking of sensitive identifiers: Now masks not only tenantId, but also subscriptionId, accountName, and resourceGroup from error messages, while continuing to emit only allowed identifiers in telemetry. (migrationTelemetry.ts)
  • Enriched AI error context: Adds aiErrorCauseType and a bounded aiErrorCauseCode to telemetry, and ensures raw error messages are only included in user-consented issue reports, not telemetry. (migrationTelemetry.ts)

Schema conversion telemetry refinements:

  • Tracks domain index and total domains in telemetry measurements for each schema conversion step, improving progress tracking. (phase3SchemaConversion.ts)
  • Simplifies the lastStep telemetry property to only the sub-step name (e.g., containerDesign), removing domain-specific prefixes for clarity and consistency. (phase3SchemaConversion.ts) [1] [2] [3] [4] [5] [6] [7] [8]

Provisioning telemetry adjustments:

  • Clarifies that only specific OII identifiers (accountName, subscriptionId) are emitted in telemetry, and removes emission of resourceGroup as a separate property. (phase4Provisioning.ts) [1] [2]
  • Removes the sampleDataInserted property from telemetry, streamlining reported metrics. (phase4Provisioning.ts)

sevoku added 3 commits June 1, 2026 13:41
Updated telemetry properties to track the current step in the schema conversion process without including domain labels. This change enhances clarity in telemetry data by focusing on the step type rather than the domain context.
Improves telemetry tracking for AI model errors by adding detailed cause type, cause code, and cause message to the telemetry context. This ensures better insights into error occurrences during migration processes.
Updated the migration telemetry context to mask additional sensitive identifiers including subscriptionId, accountName, and resourceGroup. Improved logging to ensure only predefined OII identifiers are emitted, enhancing data privacy during telemetry reporting.
@github-actions

github-actions Bot commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

🎉 Build Summary

🔗 Source

📦 Package Information

🧪 Test Results

  • Unit Tests: ✅ success
  • Integration Tests: ✅ success

✅ Build Status

All checks completed successfully!

@github-actions

Copy link
Copy Markdown
Contributor

🎭 E2E Tests (Playwright + VS Code)

Commit: ef0cdb4
Pull Request: #3087 Enhance telemetry tracking and data privacy in migration process

🧪 Result

  • E2E Tests: ✅ success

📥 Artifacts (run)

Tip: the HTML report artifact contains a self-contained Playwright report.
Download the zip, extract, and open index.html — or run
npx playwright show-report <extracted-dir> for the interactive view.

@github-code-quality

Copy link
Copy Markdown
Contributor

Code Coverage Overview

Languages: TypeScript

TypeScript / code-coverage/vitest

The overall coverage remains at 73%, unchanged from the branch.


Code Coverage is in Public Preview. Learn more and provide us with your feedback.

@github-actions

Copy link
Copy Markdown
Contributor

🔨 Build, Lint & Test

🔗 Source

📦 Package Information

🧪 Test Results

  • Unit Tests: ✅ success
  • Integration Tests (extension host): ✅ success

📥 Artifacts (run)

✅ Build Status

Build and local tests passed. See sibling comments below for E2E and NoSQL integration results.

@sevoku sevoku marked this pull request as ready for review June 15, 2026 12:42
@sevoku sevoku requested a review from a team as a code owner June 15, 2026 12:42
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