ServerTelemetryChannel does not respect what is passed via ApplicationInsights.config

[cleberdantas]

<TelemetryChannel Type="Microsoft.ApplicationInsights.WindowsServer.TelemetryChannel.ServerTelemetryChannel, Microsoft.AI.ServerTelemetryChannel">
           <EndpointAddress>http://myendpoint/v2/track</EndpointAddress>
</TelemetryChannel>

Hi,
It seems like when we set via configuration file (ApplicationInsights.config) the EndpointAddress element that this is ignored by ServerTelemetryChannel class.

Bellow we can see that when the Initialize method is called the property is set with the value inside of configuration.EndpointContainer.Ingestion which is not the same source when loaded via configuration file:

ApplicationInsights-dotnet/BASE/src/ServerTelemetryChannel/ServerTelemetryChannel.cs

Line 326 in a26a43f

this.EndpointAddress = new Uri(configuration.EndpointContainer.Ingestion, "v2/track").AbsoluteUri;

ApplicationInsights-dotnet/BASE/src/ServerTelemetryChannel/ServerTelemetryChannel.cs

Lines 118 to 122 in a26a43f

	public string EndpointAddress
	{
	get { return this.TelemetrySerializer.EndpointAddress?.ToString(); }
	set { this.TelemetrySerializer.EndpointAddress = new Uri(value); }
	}

Is my understanding correct? Is it a problem? Is there a way fix it?

[Dmitry-Matveev]

@TimothyMothra can you please look into that?

[TimothyMothra]

This looks like a bug.

This change was introduced in 2.12 when I added support for connection strings.
I added unit tests for as many ways to configure the SDK as I could imagine, but clearly I missed something.

I'm adding this to the top of my todo list, but please give me a couple of days to look at it.
We have some customers already using connection string without issue, so I'll need some time to sit with this and review why I made this change.

2.11

ApplicationInsights-dotnet/src/ServerTelemetryChannel/ServerTelemetryChannel.cs

Lines 303 to 312 in de4e53d

	public void Initialize(TelemetryConfiguration configuration)
	{
	this.Transmitter.Initialize();
	// ApplyPolicies will synchronously get list of file names from disk and calculate size
	// Creating task to improve application startup time
	ExceptionHandler.Start(() => { return Task.Run(() => this.Transmitter.ApplyPolicies()); });
	this.isInitialized = true;
	}

2.12

ApplicationInsights-dotnet/BASE/src/ServerTelemetryChannel/ServerTelemetryChannel.cs

Lines 317 to 333 in b7cc9ff

	public void Initialize(TelemetryConfiguration configuration)
	{
	if (configuration == null)
	{
	throw new ArgumentNullException(nameof(configuration));
	}
	this.Transmitter.Initialize();
	this.EndpointAddress = new Uri(configuration.EndpointContainer.Ingestion, "v2/track").AbsoluteUri;
	// ApplyPolicies will synchronously get list of file names from disk and calculate size
	// Creating task to improve application startup time
	ExceptionHandler.Start(() => { return Task.Run(() => this.Transmitter.ApplyPolicies()); });
	this.isInitialized = true;
	}

Workaround

@cleberdantas I'm sorry for the trouble.
Thank you for opening an issue.
As a workaround, can you downgrade to 2.11 ?

[cleberdantas]

Hi, @TimothyMothra!

Thanks for the quick reply.

As a "workaround" I've just moved the EndpointAddress configuration into a web.config/app.config file and configured this via code with TelemetryConfiguration.Active.TelemetryChannel.EndpointAddress, it worked just fine.

Since the ApplicationInsights.config is the default option and it is the way that the docs state how to configure it, I thought it was a good idea to raise the issue.

Cleber

[TimothyMothra]

@cleberdantas we're releasing 2.12.1 today that contains the fix for this.
It should be available on NuGet within an hour!

2.13-beta2 should get released later this week, also with this fix.

Thanks again for reporting this issue!