Can I setup application insights in another region?
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
azure azure-application-insights
add a comment |
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
azure azure-application-insights
add a comment |
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
azure azure-application-insights
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
azure azure-application-insights
azure azure-application-insights
asked Nov 21 '18 at 20:29
Kat Lim RuizKat Lim Ruiz
1,28611323
1,28611323
add a comment |
add a comment |
2 Answers
2
active
oldest
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.
add a comment |
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:
- There are direct and fast connections between data centers. So, for East US <=> West US (same region) the latency should be minimal.
- 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}).
Is performance good? Since network latency could now be larger? Say east us and west us.
– Kat Lim Ruiz
Nov 22 '18 at 7:23
Covered this question as well.
– ZakiMa
Nov 27 '18 at 6:53
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53420033%2fcan-i-setup-application-insights-in-another-region%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
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.
add a comment |
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.
add a comment |
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.
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.
answered Nov 27 '18 at 5:33
Ivan YangIvan Yang
2,969126
2,969126
add a comment |
add a comment |
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:
- There are direct and fast connections between data centers. So, for East US <=> West US (same region) the latency should be minimal.
- 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}).
Is performance good? Since network latency could now be larger? Say east us and west us.
– Kat Lim Ruiz
Nov 22 '18 at 7:23
Covered this question as well.
– ZakiMa
Nov 27 '18 at 6:53
add a comment |
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:
- There are direct and fast connections between data centers. So, for East US <=> West US (same region) the latency should be minimal.
- 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}).
Is performance good? Since network latency could now be larger? Say east us and west us.
– Kat Lim Ruiz
Nov 22 '18 at 7:23
Covered this question as well.
– ZakiMa
Nov 27 '18 at 6:53
add a comment |
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:
- There are direct and fast connections between data centers. So, for East US <=> West US (same region) the latency should be minimal.
- 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}).
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:
- There are direct and fast connections between data centers. So, for East US <=> West US (same region) the latency should be minimal.
- 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}).
edited Nov 27 '18 at 6:52
answered Nov 22 '18 at 1:41
ZakiMaZakiMa
1,768822
1,768822
Is performance good? Since network latency could now be larger? Say east us and west us.
– Kat Lim Ruiz
Nov 22 '18 at 7:23
Covered this question as well.
– ZakiMa
Nov 27 '18 at 6:53
add a comment |
Is performance good? Since network latency could now be larger? Say east us and west us.
– Kat Lim Ruiz
Nov 22 '18 at 7:23
Covered this question as well.
– ZakiMa
Nov 27 '18 at 6:53
Is performance good? Since network latency could now be larger? Say east us and west us.
– Kat Lim Ruiz
Nov 22 '18 at 7:23
Is performance good? Since network latency could now be larger? Say east us and west us.
– Kat Lim Ruiz
Nov 22 '18 at 7:23
Covered this question as well.
– ZakiMa
Nov 27 '18 at 6:53
Covered this question as well.
– ZakiMa
Nov 27 '18 at 6:53
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53420033%2fcan-i-setup-application-insights-in-another-region%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown