您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.

从网络性能监视器迁移到连接监视器Migrate to Connection Monitor from Network Performance Monitor

重要

自 2021 年 7 月 1 日起,你将无法在现有工作区中添加新测试,也无法通过网络性能监视器启用新的工作区。Starting 1 July 2021, you will not be able to add new tests in an existing workspace or enable a new workspace with Network Performance Monitor. 可以继续使用在 2021 年 7 月 1 日之前创建的测试。You can continue to use the tests created prior to 1 July 2021. 为了最大程度地减少当前工作负荷的服务中断,请在 2024 年 2 月 29 日之前,在 Azure 网络观察程序中将测试从网络性能监视器迁移到新连接监视器。To minimize service disruption to your current workloads, migrate your tests from Network Performance Monitor to the new Connection Monitor in Azure Network Watcher before 29 February 2024.

只需单击一下,就可以将测试从网络性能监视器 (NPM) 迁移到经过改进的新连接监视器,并且没有故障时间。You can migrate tests from Network Performance Monitor (NPM) to new, improved Connection Monitor with a single click and with zero downtime. 若要了解有关这些优势的详细信息,请参阅连接监视器To learn more about the benefits, see Connection Monitor.

需要注意的要点Key points to note

迁移将有助于生成以下结果:The migration helps produce the following results:

  • 本地代理和防火墙设置按原样工作。On-premises agents and firewall settings work as is. 不需要进行任何更改。No changes are required. 需要将安装在 Azure 虚拟机上的 Log Analytics 代理替换为网络观察程序扩展Log Analytics agents that are installed on Azure virtual machines need to be replaced with the Network Watcher extension.
  • 现有测试已映射到“连接监视器”>“测试组”>“测试格式”。Existing tests are mapped to Connection Monitor > Test Group > Test format. 通过选择“编辑”,可以查看和修改新连接监视器的属性,下载模板以对其进行更改,然后通过 Azure 资源管理器提交模板。By selecting Edit, you can view and modify the properties of the new Connection Monitor, download a template to make changes to it, and submit the template via Azure Resource Manager.
  • 代理会将数据发送到 Log Analytics 工作区和指标。Agents send data to both the Log Analytics workspace and the metrics.
  • 数据监视:Data monitoring:
    • Log Analytics 中的数据:迁移之前,数据将保留在 NetworkMonitoring 表中配置了 NPM 的工作区中。Data in Log Analytics: Before migration, the data remains in the workspace in which NPM is configured in the NetworkMonitoring table. 迁移后,数据将移动到同一工作区中的 NetworkMonitoring 表、NWConnectionMonitorTestResult 表和 NWConnectionMonitorPathResult 表。After the migration, the data goes to the NetworkMonitoring table, NWConnectionMonitorTestResult table and NWConnectionMonitorPathResult table in the same workspace. 在 NPM 中禁用测试后,数据将仅存储在 NWConnectionMonitorTestResult 表和 NWConnectionMonitorPathResult 表中。After the tests are disabled in NPM, the data is stored only in the NWConnectionMonitorTestResult table and NWConnectionMonitorPathResult table.
    • 基于日志的警报、仪表板和集成:必须基于新的 NWConnectionMonitorTestResult 表和 NWConnectionMonitorPathResult 表手动编辑查询。Log-based alerts, dashboards, and integrations: You must manually edit the queries based on the new NWConnectionMonitorTestResult table and NWConnectionMonitorPathResult table. 若要在指标中重新创建警报,请参阅使用连接监视器进行网络连接监视To re-create the alerts in metrics, see Network connectivity monitoring with Connection Monitor.
  • 对于 ExpressRoute 监视:For ExpressRoute Monitoring:
    • 端到端丢失和延迟:连接监视器支持此功能,并且它比 NPM 更简单,因为用户不需要配置要监视的线路和对等互连。End to end loss and latency: Connection Monitor will power this, and it will easier than NPM as users do not need to configure which circuits and peerings to monitor. 将自动发现路径中的线路,数据将在指标中提供(比 NPM 在其中存储结果的 LA 更快)。Circuits in the path will automatically be discovered , data will be available in metrics (faster than LA which was where NPM stored the results). 拓扑也将按原样工作。Topology will work as is as well.
    • 带宽度量:通过启动与带宽相关的指标,NPM 基于日志分析的方法对 ExpressRoute 客户的带宽监视不起作用。Bandwidth measurements: With the launch of bandwidth related metrics, NPM’s log analytics based approach was not effective in bandwidth monitoring for ExpressRoute customers. 此功能目前在连接监视器中不可用。This capability is now not available in Connection Monitor.

先决条件Prerequisites

  • 确保在订阅和 Log Analytics 工作区的区域中启用了网络观察程序。Ensure that Network Watcher is enabled in your subscription and the region of the Log Analytics workspace.
  • 如果 Azure VM(所属的区域/订阅不同于 Log Analytics 工作区的区域/订阅)用作终结点,请确保已为订阅和区域启用网络观察程序。In case Azure VM belonging to a different region/subscription than that of Log Analytics workspace is used as an endpoint, make sure Network Watcher is enabled for that subscription and region.
  • 必须通过网络观察程序扩展启用安装有 Log Analytics 代理的 Azure 虚拟机。Azure virtual machines with Log Analytics agents installed must be enabled with the Network Watcher extension.

迁移测试Migrate the tests

若要将测试从网络性能监视器迁移到连接监视器,请执行以下操作:To migrate the tests from Network Performance Monitor to Connection Monitor, do the following:

  1. 在网络观察程序中,选择“连接监视器”,然后选择“从 NPM 迁移测试”选项卡 。In Network Watcher, select Connection Monitor, and then select the Migrate tests from NPM tab.

    将测试从网络性能监视器迁移到连接监视器

  2. 在下拉列表中,选择订阅和工作区,然后选择要迁移的 NPM 功能。In the drop-down lists, select your subscription and workspace, and then select the NPM feature you want to migrate.

  3. 选择“导入”以迁移测试。Select Import to migrate the tests.

迁移开始后,将进行以下更改:After the migration begins, the following changes take place:

  • 创建新的连接监视器资源。A new connection monitor resource is created.
    • 每个区域和订阅都创建一个连接监视器。One connection monitor per region and subscription is created. 对于使用本地代理的测试,新连接监视器名称的格式为 <workspaceName>_"workspace_region_name"For tests with on-premises agents, the new connection monitor name is formatted as <workspaceName>_"workspace_region_name". 对于使用 Azure 代理的测试,新连接监视器名称的格式为 <workspaceName>_<Azure_region_name>For tests with Azure agents, the new connection monitor name is formatted as <workspaceName>_<Azure_region_name>.
    • 监视数据现在存储在启用了 NPM 的同一个 Log Analytics 工作区中,在名为 NWConnectionMonitorTestResult 表和 NWConnectionMonitorPathResult 表的新表中。Monitoring data is now stored in the same Log Analytics workspace in which NPM is enabled, in new tables called NWConnectionMonitorTestResult table and NWConnectionMonitorPathResult table.
    • 测试名称将作为测试组名称继续使用。The test name is carried forward as the test group name. 不迁移测试说明。The test description isn't migrated.
    • 将创建源终结点和目标终结点,并在新测试组中使用它们。Source and destination endpoints are created and used in the new test group. 对于本地代理,终结点的格式设置为 <workspaceName>_<FQDN of on-premises machine>。代理说明未迁移。For on-premises agents, the endpoints are formatted as <workspaceName>_<FQDN of on-premises machine>.The Agent description isn't migrated.
    • 目标端口和探测间隔移动到名为 TC_<protocol>_<port>TC_<protocol>_<port>_AppThresholds 的测试配置。Destination port and probing interval are moved to a test configuration called TC_<protocol>_<port> and TC_<protocol>_<port>_AppThresholds. 协议基于端口值设置。The protocol is set based on the port values. 对于 ICMP,测试配置被命名为 TC_<protocol>TC_<protocol>_AppThresholdsFor ICMP, the test configurations are named as TC_<protocol> and TC_<protocol>_AppThresholds. 如果设置了成功阈值和其他可选属性,则将其迁移,否则保留为空。Success thresholds and other optional properties if set are migrated, otherwise are left blank.
    • 如果迁移测试包含未运行的代理,则需要启用代理并再次迁移。If the migrating tests contain agents that aren't running, you need to enable the agents and migrate again.
  • 未禁用 NPM,所以迁移的测试可以继续发送数据到 NetworkMonitoring 表、NWConnectionMonitorTestResult 表和 NWConnectionMonitorPathResult 表。NPM isn't disabled, so the migrated tests can continue to send data to the NetworkMonitoring table, NWConnectionMonitorTestResult table and NWConnectionMonitorPathResult table. 此方法可确保现有基于日志的警报和集成不受影响。This approach ensures that existing log-based alerts and integrations are unaffected.
  • 新创建的连接监视器在连接监视器中可见。The newly created connection monitor is visible in Connection Monitor.

迁移之后,请务必:After the migration, be sure to:

  • 手动禁用 NPM 中的测试。Manually disable the tests in NPM. 在执行此操作之前,你将继续为其付费。Until you do so, you'll continue to be charged for them.
  • 禁用 NPM 时,在 NWConnectionMonitorTestResult 表和 NWConnectionMonitorPathResult 表中重新创建警报或使用指标。While you're disabling NPM, re-create your alerts on the NWConnectionMonitorTestResult and NWConnectionMonitorPathResult tables or use metrics.
  • 将任何外部集成迁移到 NWConnectionMonitorTestResult 表和 NWConnectionMonitorPathResult 表。Migrate any external integrations to the NWConnectionMonitorTestResult and NWConnectionMonitorPathResult tables. 外部集成的示例包括 Power BI 和 Grafana 中的仪表板,以及与安全信息和事件管理 (SIEM) 系统的集成。Examples of external integrations are dashboards in Power BI and Grafana, and integrations with Security Information and Event Management (SIEM) systems.

后续步骤Next steps

若要详细了解连接监视器,请参阅:To learn more about Connection Monitor, see: