feat: integrate Azure Monitor OTel Profiler + Code Optimizations

[BenjaminMichaelis]

Summary

Integrates Azure Monitor Application Insights Profiler (via the modern OpenTelemetry path) into Microsoft.TryDotNet to enable Code Optimizations insights on the CPU-heavy Roslyn compilation workloads in POST /commands.

What changed

File	Change
NuGet.config	Added nuget.org source + Azure.Monitor.* / OpenTelemetry.* package source mapping (was blocked by <clear/>)
Directory.Packages.props	Pinned Azure.Monitor.OpenTelemetry.AspNetCore 1.5.0 + Azure.Monitor.OpenTelemetry.Profiler 1.0.1-beta.1
src/Microsoft.TryDotNet/Microsoft.TryDotNet.csproj	Added two <PackageReference> entries (no version — resolved by CPM)
src/Microsoft.TryDotNet/Program.cs	Wired AddOpenTelemetry().UseAzureMonitor().AddAzureMonitorProfiler(); startup warning when connection string missing
src/Microsoft.TryDotNet/appsettings.json	Added OTel logging provider section with correct category names

SDK path chosen

Azure Monitor OpenTelemetry Distro (Azure.Monitor.OpenTelemetry.AspNetCore + Azure.Monitor.OpenTelemetry.Profiler) — the canonical modern path. Classic Microsoft.ApplicationInsights.Profiler.AspNetCore was rejected (legacy, not on repo feeds).

Key decisions

• No BYOS — Code Optimizations does not work with Bring Your Own Storage
• Runtime image unchanged — SDK image is intentional; CSharpProjectKernel needs full dotnet toolchain
• Connection string via env var — inject APPLICATIONINSIGHTS_CONNECTION_STRING at deploy time; never baked in
• CPU trigger (post-deploy, Azure Portal) — 80% / 30s / 15min cooldown; required to capture Roslyn compilation spikes

Post-deploy steps required

1. Inject APPLICATIONINSIGHTS_CONNECTION_STRING as container env var
2. Azure Portal → Application Insights → Performance → Profiler → Triggers → CPU (80%, 30s, 15min cooldown)
3. Confirm startup in container logs: Starting application insights profiler with connection string: ...

Reviewed by

Three agents (Sonnet, Opus 4.6, GPT-5.5) reviewed against all 5 Microsoft Learn docs. All findings addressed. Unanimous approval after fix to profiler logger category in appsettings.json.

[Copilot]

Pull request overview

This PR integrates Azure Monitor’s modern OpenTelemetry distro (including the Azure Monitor Profiler) into Microsoft.TryDotNet so CPU-heavy Roslyn compilation workloads (notably POST /commands) can be analyzed via Application Insights Profiler / Code Optimizations.

Changes:

• Adds Azure Monitor OpenTelemetry distro + Profiler packages via Central Package Management.
• Wires up AddOpenTelemetry().UseAzureMonitor().AddAzureMonitorProfiler() in Program.cs and emits a startup warning when no AI connection string is present.
• Updates NuGet restore configuration to include nuget.org and source mapping for Azure Monitor / OpenTelemetry packages; updates logging configuration in appsettings.json.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
src/Microsoft.TryDotNet/Program.cs	Registers Azure Monitor OpenTelemetry + Profiler and adds a missing-connection-string startup warning.
src/Microsoft.TryDotNet/Microsoft.TryDotNet.csproj	Adds package references for Azure Monitor OpenTelemetry distro + Profiler (versions resolved via CPM).
src/Microsoft.TryDotNet/appsettings.json	Adds logging configuration intended to surface profiler-related categories.
NuGet.config	Adds nuget.org feed and maps Azure Monitor / OpenTelemetry package IDs to it.
Directory.Packages.props	Pins Azure.Monitor.OpenTelemetry.AspNetCore and prerelease Azure.Monitor.OpenTelemetry.Profiler.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

src/Microsoft.TryDotNet/Program.cs:81

• This repeats the APPLICATIONINSIGHTS_CONNECTION_STRING lookup already done in Main. Consider caching the value (or passing it into CreateWebApplicationAsync) to avoid duplicate env reads and to keep the conditional/warning consistent.

        if (!string.IsNullOrWhiteSpace(Environment.GetEnvironmentVariable("APPLICATIONINSIGHTS_CONNECTION_STRING")))
        {
            builder.Services.AddOpenTelemetry()
                .UseAzureMonitor()
                .AddAzureMonitorProfiler();
        }