[Spike] Investigate the handling of DB redirects inside of Azure App Services

[jbedell-newrelic]

Description

When running in app inside of Azure App Services, the instrumentation to identify the database server.address does not work. It works fine when talking to an Azure SQL DB from outside, but when inside App Services, the driver is being redirected away from the known address (something like my-database.database.windows.net) and is instead sent to a worker server (something like abc12.xyz890.westus2-a.worker.database.windows.net). This causes our DB spans to be sent up with unknown instead of the actual value because we can't identify which is correct.

This causes the following log message:
Two different addresses detected: {0} and {1}. Invalidating previously detected address.

Which is an indication that we have ceased connection address detection for that connection.

Note: This does NOT happen when talking to the same database from outside Azure App Services.

We need to investigate if we can resolve this issue.

[Newrelic-Boomi]

https://new-relic.atlassian.net/browse/NR-465550