Investigate Adding Telemetry for Renames + Back Compat Done By the Generator

[jorgerangel-msft]

We can possibly create some metadata file that lists the renames that occurred. Possibly use a schema.

[github-actions]

🎯 Issue Triage

This is a feature investigation request to add telemetry tracking for renames and backward-compatibility changes performed by the C# generator, potentially via a metadata/schema file.

Category: Feature Request
Area: emitter:client:csharp

🔍 Analysis

• Affected component: @typespec/http-client-csharp generator
• Request: Investigate adding a telemetry mechanism (possibly a metadata file with a schema) to record renames and back-compat transformations applied by the generator
• Use case: Tracking what renames/back-compat changes the generator performs would improve observability and debugging for generated SDK consumers
• No reproduction code needed — this is an investigative/design task

📝 Suggested next steps

• Define what data should be captured (e.g., original name → renamed name, reason for rename)
• Evaluate metadata file format options (JSON with schema, etc.)
• Consider how consumers would access/use this telemetry
• Prototype and validate the approach

Generated by Agentic Triage

[jorgerangel-msft]

We might be able to use the existing metadata.json file - though I suppose that is currently Azure-only

[jorgerangel-msft]

Another possible solution is to upload the metadata.json file as a build artifact on CI merge builds. Then using cloudmine to extract the json data.