Azure AppInsights端到端关联异常：三级API调用层级不符预期

我为遥测关联需求使用Azure AppInsights，搭建了三个依次调用的API：First Api → Middle Api → Another Api。API调用通过服务类使用Typed HttpClient实现，所有API项目均已添加Microsoft.ApplicationInsights.AspNetCore和Microsoft.Extensions.Logging.ApplicationInsights NuGet引用。

当前配置代码如下：

Program.cs #

using Microsoft.ApplicationInsights.Channel;
using Microsoft.ApplicationInsights.WindowsServer.TelemetryChannel;

var builder = WebApplication.CreateBuilder(args);
builder.Services.AddControllers();
...

//App Insights
builder.Services.AddSingleton(typeof(ITelemetryChannel),
    new ServerTelemetryChannel() { StorageFolder = "/tmp/myfolder" });
builder.Services.AddApplicationInsightsTelemetry();

builder.Services.AddSingleton<IConfiguration>(builder.Configuration);
builder.Services.AddScoped<IWeatherService, DummyWeatherService>();
builder.Services.AddHttpClient<IWeatherService, DummyWeatherService>();


var app = builder.Build();

...

app.Run();

Service代码 #

using System.Net.Http.Headers;
using AppInsightsDemo.Api.Models;

namespace AppInsightsDemo.Api.Services;

public class DummyWeatherService : IWeatherService
{
    private readonly IConfiguration _configuration;
    private readonly HttpClient _httpClient;

    public DummyWeatherService(
        IConfiguration configuration,
        HttpClient httpClient)
    {
        _configuration = configuration;
        _httpClient = httpClient;
        _httpClient.BaseAddress = GetMiddleApiBaseUri();
        _httpClient.DefaultRequestHeaders.Accept.Clear();
        _httpClient.DefaultRequestHeaders.Accept.Add(
            new MediaTypeWithQualityHeaderValue("application/json"));
    }

    private Uri GetAnotherApiBaseUri()
    {
        var configurationSection = _configuration.GetRequiredSection("Dependencies");
        var baseUri = configurationSection.GetValue<string>("MiddleApiUri")
                      ?? throw new ArgumentException("Another Api base uri is empty");

        return new Uri(baseUri);
    }
    
    public async Task<Weather?> GetWeatherAsync()
    {
        Weather? weather = null;
        var response = await _httpClient.GetAsync("middle");
        if (response.IsSuccessStatusCode)
        {
            weather = await response.Content.ReadAsAsync<Weather>();
        }

        return weather;
    }
}

目前在AppInsights中，第三个API事件与前两个拥有相同的Operation Id，但父ID不正确。期望第三个事件以中间API（localhost://7290）的ID作为父ID，形成First Api → Middle Api → Another Api的正确层级结构。

问题核心是HttpClient未自动传递AppInsights的遥测关联头，导致跨API调用的父/子关联关系断裂。以下是具体修正步骤：

1. 简化AppInsights基础配置 #

手动注册ITelemetryChannel并非遥测关联的必要配置，默认SDK已提供足够的通道实现。可简化Program.cs中的AppInsights配置：

// 替换原有的ITelemetryChannel注册和AddApplicationInsightsTelemetry
builder.Services.AddApplicationInsightsTelemetry();

2. 确保HttpClient自动注入遥测处理程序 #

当调用AddApplicationInsightsTelemetry()时，SDK会自动为所有DI管理的HttpClient添加TelemetryHandler，该处理程序负责传递Request-Id等关联头。需要确保：

• 所有API项目的Program.cs都正确调用AddApplicationInsightsTelemetry()
• Typed HttpClient通过builder.Services.AddHttpClient<IWeatherService, DummyWeatherService>()注册（你的代码已满足此点）
• 不要手动替换HttpClient的MessageHandlers，避免覆盖SDK自动添加的遥测处理程序

3. 修正服务类中的方法错误 #

你的服务类中GetAnotherApiBaseUri方法名与实际用途不符（用于获取Middle Api地址），修正方法名避免逻辑混淆：

private Uri GetMiddleApiBaseUri()
{
    var configurationSection = _configuration.GetRequiredSection("Dependencies");
    var baseUri = configurationSection.GetValue<string>("MiddleApiUri")
                  ?? throw new ArgumentException("Middle Api base uri is empty");

    return new Uri(baseUri);
}

4. 确保Middle Api调用Another Api时使用同样的规范 #

Middle Api调用Another Api的代码，也需要使用DI注入的Typed HttpClient或普通HttpClient，确保遥测关联头被正确传递到Another Api。

完成以上配置后，AppInsights将自动维护First Api → Middle Api → Another Api的层级关联，第三个API事件的父ID会正确指向Middle Api的请求ID。

内容的提问来源于stack exchange，提问作者Parth Sekar