DiagnosticTelemetryModule( and HeartBeat) is not added via DI, hence configuration is differently done

DiagnosticTelemetryModule( and HeartBeat) is added to TelemetryConfiguration by base SDK and not added via DI like other modules. This means it’ll not possible to configure this module via services.ConfigureTelemetryModule<DiagnosticModule>() mechanism. However, this module is part of the TelemetryModules.Instance.Modules singleton, and hence can be retrieved this way for configuration.

Version Info

SDK Version : .NET Version : How Application was onboarded with SDK(VisualStudio/StatusMonitor/Azure Extension) : OS : Hosting Info (IIS/Azure WebApps/ etc) :

[cijothomas]

@TimothyMothra is working on addressing this issue. Expecting to ship with next stable release.

[Taudris]

Is this an adequate upgrade-resistant workaround I can use in production until this gets resolved?

if (!services.Any(o => typeof(IHeartbeatPropertyManager).IsAssignableFrom(o.ImplementationType)))
{
    services.AddSingleton<ITelemetryModule, DiagnosticsTelemetryModule>();
}