1
votes

I have all my app services in Azure East US, and I was wondering if I could put the Application Insights related to these in Azure West.

My question whether this imposes any noticeable performance hit.

I wonder if East US fails, would application insights (in West) be able to log something.

Thanks

2

2 Answers

2
votes

As per @ZakiMa metioned, they can be set up in different locations and no impact if one of them fails.

For the performance:

I just got the feedback from MS application insights team, the answer is no performance issue:

Application insights sends data to their backend asynchronously - so the actual network RT time should not matter.

Also, even though the app insights is in East US, the 'ingest' endpoints are globally distributed, and telemetry is always sent to the nearest available 'ingest' point.

Details are here. Hope it helps.

1
votes

Yes, it is possible to point to existing Application Insights resource (which can be in any location).

If East US fails, other data centers should not be impacted. Application Insights should be able to log everything sent to it (assuming the app running in East US is still running).

Update: As Ivan mentioned, ingest endpoints are globally distributed. Though SDK will send data to nearest endpoint, 200 response means that that endpoint persisted data in the right data center.

It will take more time than for the same data center but the performance should not be impacted:

  1. There are direct and fast connections between data centers. So, for East US <=> West US (same region) the latency should be minimal.
  2. SDKs send data in background in batches, so the latency requirements for ingest calls are not strict for optimal performance (we have many high volume apps which upload telemetry data across regions {not even data centers}).