将 App Insights 可用性测试部署到英国南部,但奇怪的是 ARM 说是俄罗斯

Deploying App Insights availability test to UK South, but strangely the ARM says Russia

在自动部署 Application Insights 可用性监控资源时,我注意到奇怪的是,在保存英国南部并从门户导出 ARM 模板时,该位置的名称似乎是俄罗斯。

我认为这是我这边的错误,但在深入研究 JavaScript 和网络流量后,我发现了以下返回信息:

https://management.azure.com/batch?api-version=2015-11-01

{
    "DisplayName": "North Central US",
    "Tag": "us-il-ch1-azr"
},
{
    "DisplayName": "West Europe",
    "Tag": "emea-nl-ams-azr"
},
{
    "DisplayName": "Southeast Asia",
    "Tag": "apac-sg-sin-azr"
},
{
    "DisplayName": "West US",
    "Tag": "us-ca-sjc-azr"
},
{
    "DisplayName": "South Central US",
    "Tag": "us-tx-sn1-azr"
},
{
    "DisplayName": "East US",
    "Tag": "us-va-ash-azr"
},
{
    "DisplayName": "East Asia",
    "Tag": "apac-hk-hkn-azr"
},
{
    "DisplayName": "North Europe",
    "Tag": "emea-gb-db3-azr"
},
{
    "DisplayName": "Japan East",
    "Tag": "apac-jp-kaw-edge"
},
{
    "DisplayName": "Australia East",
    "Tag": "emea-au-syd-edge"
},
{
    "DisplayName": "France Central (Formerly France South)",
    "Tag": "emea-ch-zrh-edge"
},
{
    "DisplayName": "France Central",
    "Tag": "emea-fr-pra-edge"
},
{
    "DisplayName": "UK South",
    "Tag": "emea-ru-msa-edge"
},
{
    "DisplayName": "UK West",
    "Tag": "emea-se-sto-edge"
},
{
    "DisplayName": "Brazil South",
    "Tag": "latam-br-gru-edge"
},
{
    "DisplayName": "Central US",
    "Tag": "us-fl-mia-edge"
}

当查看 quick start template 时,它表明这似乎是莫斯科。

运行 availability monitoring is being deprecated, and there's a discussion on the Microsoft docs repo where an overhaul is mentioned 的一些基础设施可以 运行 保留一段时间。莫斯科的名字是否有可能被用作代表英国的变通办法?或者这是一个奇怪的错误?

似乎没有 github 来讨论可用性监视器,只有 SDK 之类的东西,上面的票在文档库中,所以我不确定最好的论坛这个。值得注意的是似乎确实存在 general confusion in the community whether it impacts Availability monitoring,因此似乎值得讨论以防万一它是一个错误(或者如果我是愚蠢而遗漏了什么!)。

我直接联系了一位友善的 Microsoft 项目经理,他友好地回复:

ARM templates must use our internal location IDs, which, due to historical reasons, do not match their actual location. This isn't documented anywhere externally unfortunately. I'll take care of updating the documentation, in the meantime here is a snippet from our repository - Display Name is the actual location, and the Tag is our internal location ID, which is also used in ARM.

DisplayName = "North Central US",
Tag = "us-il-ch1-azr"

DisplayName = "West Europe",
Tag = "emea-nl-ams-azr"

DisplayName = "Southeast Asia",
Tag = "apac-sg-sin-azr"

DisplayName = "West US",
Tag = "us-ca-sjc-azr"

DisplayName = "South Central US",
Tag = "us-tx-sn1-azr"

DisplayName = "East US",
Tag = "us-va-ash-azr"

DisplayName = "East Asia",
Tag = "apac-hk-hkn-azr"

DisplayName = "North Europe",
Tag = "emea-gb-db3-azr"

DisplayName = "Japan East",
Tag = "apac-jp-kaw-edge"

DisplayName = "Australia East",
Tag = "emea-au-syd-edge"

DisplayName = "France Central (Formerly France South)",
Tag = "emea-ch-zrh-edge"

DisplayName = "France Central",
Tag = "emea-fr-pra-edge"

DisplayName = "UK South",
Tag = "emea-ru-msa-edge"

DisplayName = "UK West",
Tag = "emea-se-sto-edge"

DisplayName = "Brazil South",
Tag = "latam-br-gru-edge"

DisplayName = "Central US",
Tag = "us-fl-mia-edge"

(我已经从看起来像 c# 代码的内容中删节了它)

文档将在适当的时候更新,所以如果有人在我之前看到它,请随时将其添加为评论。