After switching from app insights to Aspire's opinionated OTEL defaults, x-forwarded-for no longer works

[onionhammer]

After removing app insights telemetry and replacing it with Aspire's OOTB OTEL hookup (plus the azure log exporter) now every single request is "from" whatever ACA region the app is hosted in (in this case Des Moines, Iowa).

Is there some guidance on how to actually configure OTEL to use the X-Forwarded-For header and set the exported value in azure logs?

[davidfowl]

I think the place to file these issues is https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/monitor/Azure.Monitor.OpenTelemetry.Exporter. Have you tried updating the package version? I think there were some changes made to make ACA work better.

[onionhammer]

@davidfowl are you referring to the beta? We're currently using 1.2.0

[davidfowl]

Yes try the beta and see if that fixes it. Then we'll know if there's more work left to do (for the azure team to do 😄)

[onionhammer]

@davidfowl I just confirmed that 1.3.0-beta.1 doesnt fix it

[davidfowl]

OK please open an issue on that repo and I'll get some eyes to look at it.

[onionhammer]

@davidfowl logged Azure/azure-sdk-for-net#42850

[davidfowl]

See #2047

[samsp-msft]

Reading the description in Azure/azure-sdk-for-net#42850, this is not really Aspire related - its about differences between the old dedicated ApplicationInsights SDK and the OTel Exporter.

[davidfowl]

It's not but can you follow up? It affects aspire apps.