SDK setup ignoring endpoint

[rafagsiqueira]

I believe I might have misunderstood the examples. When using the following code

const appInsights = require("applicationinsights");
appInsights.setup();
const appInsightsClient = appInsights.defaultClient;

with the following connection string: APPLICATIONINSIGHTS_CONNECTION_STRING=InstrumentationKey=xxxxxxxxxxxx;IngestionEndpoint=https://eastus2-3.in.applicationinsights.azure.com/ I keep getting the following error: ApplicationInsights:CorrelationIdManager (1) [Error: getaddrinfo ENOTFOUND westus-0.in.applicationinsights.azure.com at GetAddrInfoReqWrap.on…] Please note that the eastus2 endpoint resolves as expected in our environment, so this is unrelated to the DNS not resolving. Shouldn't the SDK be sending data to the eastus2 endpoint?

nslookup eastus2-3.in.applicationinsights.azure.com
Server:         172.24.224.1
Address:        172.24.224.1#53

Non-authoritative answer:
eastus2-3.in.applicationinsights.azure.com      canonical name = eastus2-3.in.ai.monitor.azure.com.
eastus2-3.in.ai.monitor.azure.com       canonical name = eastus2-3.in.ai.privatelink.monitor.azure.com.
eastus2-3.in.ai.privatelink.monitor.azure.com   canonical name = eus23-breeziest-in.trafficmanager.net.
eus23-breeziest-in.trafficmanager.net   canonical name = eus232-breeziest-in.cloudapp.net.
Name:   eus232-breeziest-in.cloudapp.net
Address: 20.44.17.2