Context

Let's squeeze out more from existing telemtry and lets improve of what is available to us

onepager: #11013

Suggested areas of investments

• Review telemetry related to MSBuild available to us in clusters today. Create overview documenting which clusters/tables are usable and what can we fetch. Put together some sample views (MSBuild usage stats, etc.)
• Mounting MSBuild telemetry to VS listeners
• Defining and exposing data-points for degraded functionality (exceptions, lags/hangs etc.)
• Defining and exposing data-points for features usage

Completed work

• noted in subissues

VS Telemetry

First iteration (17.14 P2) Completed

• onboarded VS OpenTelemetry Packages
• sending on a opt-in basis lenght of the build, Summary of Targets, Tasks and detailed breakdown of runtime of tasks
  • opt-in can be remotely triggered on VS startup

Note: we had to scale back our efforts due to issues with Perf and reliability in VS (due to taking the new dependencies on VS OTel)

.NET 10/VS 17.15 (optional)

• light-weight telemetry that's sent by default for the volume we require
• degraded functionality datapoints
• feature usage datapoints
• heavy-weight telemetry (e.g. the tasks details)