在 Azure 数据工厂中监视集成运行时Monitor an integration runtime in Azure Data Factory

适用于:是 Azure 数据工厂否 Azure Synapse Analytics(预览版)APPLIES TO: yesAzure Data Factory noAzure Synapse Analytics (Preview)

集成运行时是 Azure 数据工厂 (ADF) 用于在不同的网络环境之间提供多种数据集成功能的计算基础结构。Integration runtime is the compute infrastructure used by Azure Data Factory (ADF) to provide various data integration capabilities across different network environments. 数据工厂提供三种类型的集成运行时:There are three types of integration runtimes offered by Data Factory:

  • Azure 集成运行时Azure integration runtime
  • 自承载集成运行时Self-hosted integration runtime
  • Azure SQL Server Integration Services (SSIS) 集成运行时Azure-SQL Server Integration Services (SSIS) integration runtime

备注

本文进行了更新,以便使用新的 Azure PowerShell Az 模块。This article has been updated to use the new Azure PowerShell Az module. 你仍然可以使用 AzureRM 模块,至少在 2020 年 12 月之前,它将继续接收 bug 修补程序。You can still use the AzureRM module, which will continue to receive bug fixes until at least December 2020. 若要详细了解新的 Az 模块和 AzureRM 兼容性,请参阅新 Azure Powershell Az 模块简介To learn more about the new Az module and AzureRM compatibility, see Introducing the new Azure PowerShell Az module. 有关 Az 模块安装说明,请参阅安装 Azure PowerShellFor Az module installation instructions, see Install Azure PowerShell.

若要获取集成运行时 (IR) 实例的状态,请运行以下 PowerShell 命令:To get the status of an instance of integration runtime (IR), run the following PowerShell command:

Get-AzDataFactoryV2IntegrationRuntime -DataFactoryName MyDataFactory -ResourceGroupName MyResourceGroup -Name MyAzureIR -Status

该 cmdlet 返回不同类型的集成运行时的不同信息。The cmdlet returns different information for different types of integration runtime. 本文解释每种类型的集成运行时的属性和状态。This article explains the properties and statuses for each type of integration runtime.

Azure 集成运行时Azure integration runtime

Azure 集成运行时的计算资源在 Azure 中以弹性方式受到完全管理。The compute resource for an Azure integration runtime is fully managed elastically in Azure. 下表提供了 Get-AzDataFactoryV2IntegrationRuntime 命令返回的属性的说明:The following table provides descriptions for properties returned by the Get-AzDataFactoryV2IntegrationRuntime command:

属性Properties

下表说明该 cmdlet 针对 Azure 集成运行时返回的属性:The following table provides descriptions of properties returned by the cmdlet for an Azure integration runtime:

属性Property 说明Description
名称Name Azure 集成运行时的名称。Name of the Azure integration runtime.
状态State Azure 集成运行时的状态。Status of the Azure integration runtime.
位置Location Azure 集成运行时的位置。Location of the Azure integration runtime. 有关 Azure 集成运行时位置的详细信息,请参阅集成运行时简介For details about location of an Azure integration runtime, see Introduction to integration runtime.
DataFactoryNameDataFactoryName Azure 集成运行时所属的数据工厂的名称。Name of the data factory that the Azure integration runtime belongs to.
ResourceGroupNameResourceGroupName 数据工厂所属的资源组的名称。Name of the resource group that the data factory belongs to.
说明Description Azure 集成运行时的说明。Description of the integration runtime.

状态Status

下表提供了 Azure 集成运行时的可能状态:The following table provides possible statuses of an Azure integration runtime:

状态Status 注释/方案Comments/Scenarios
联机Online Azure 集成运行时处于联机状态,可供使用。The Azure integration runtime is online and ready to be used.
OfflineOffline 由于内部错误,Azure 集成运行时处于脱机状态。The Azure integration runtime is offline due to an internal error.

自承载集成运行时Self-hosted integration runtime

以下部分提供了 Get-AzDataFactoryV2IntegrationRuntime cmdlet 返回的属性的说明。This section provides descriptions for properties returned by the Get-AzDataFactoryV2IntegrationRuntime cmdlet.

备注

返回的属性和状态包含有关整个自承载集成运行时和运行时中每个节点的信息。The returned properties and status contain information about overall self-hosted integration runtime and each node in the runtime.

属性Properties

下表提供了每个节点的监视属性的说明:The following table provides descriptions of monitoring Properties for each node:

属性Property 说明Description
名称Name 自承载集成运行时的名称及其关联的节点。Name of the self-hosted integration runtime and nodes associated with it. 节点是装有自承载集成运行时的本地 Windows 计算机。Node is an on-premises Windows machine that has the self-hosted integration runtime installed on it.
状态Status 整个自承载集成运行时和每个节点的状态。The status of the overall self-hosted integration runtime and each node. 示例:联机/脱机/受限等。有关这些状态的信息,请参阅下一个部分。Example: Online/Offline/Limited/etc. For information about these statuses, see the next section.
版本Version 自承载集成运行时和每个节点的版本。The version of self-hosted integration runtime and each node. 自承载集成运行时的版本根据组中多数节点的版本确定。The version of the self-hosted integration runtime is determined based on version of majority of nodes in the group. 如果自承载集成运行时设置中包含不同版本的节点,则只有与逻辑自承载集成运行时的版本号相同的节点能正常运行。If there are nodes with different versions in the self-hosted integration runtime setup, only the nodes with the same version number as the logical self-hosted integration runtime function properly. 其他节点将处于受限模式,需要手动进行更新(仅当自动更新失败时)。Others are in the limited mode and need to be manually updated (only in case auto-update fails).
可用内存Available memory 自承载集成运行时节点上的可用内存。Available memory on a self-hosted integration runtime node. 此值为近实时快照。This value is a near real-time snapshot.
CPU 使用率CPU utilization 自承载集成运行时节点的 CPU 利用率。CPU utilization of a self-hosted integration runtime node. 此值为近实时快照。This value is a near real-time snapshot.
网络(进/出)Networking (In/Out) 自承载集成运行时节点的网络利用率。Network utilization of a self-hosted integration runtime node. 此值为近实时快照。This value is a near real-time snapshot.
并发作业数(运行中/上限)Concurrent Jobs (Running/ Limit) 正在运行Running. 每个节点上运行的作业或任务数。Number of jobs or tasks running on each node. 此值为近实时快照。This value is a near real-time snapshot.

上限Limit. 上限表示每个节点的最大并发作业数。Limit signifies the maximum concurrent jobs for each node. 此值根据计算机大小定义而来。This value is defined based on the machine size. 在 CPU、内存或网络未充分利用但活动即将超时的高级方案中,可提高上限来增强并发作业执行。You can increase the limit to scale up concurrent job execution in advanced scenarios, when activities are timing out even when CPU, memory, or network is under-utilized. 此功能也适用于单节点自承载集成运行时。This capability is also available with a single-node self-hosted integration runtime.
角色Role 多节点自承载集成运行时中有两种角色 – 调度程序和辅助角色。There are two types of roles in a multi-node self-hosted integration runtime – dispatcher and worker. 所有节点均为辅助角色,表示它们可用于执行作业。All nodes are workers, which means they can all be used to execute jobs. 只有一个调度程序节点,用于从云服务中拉取任务/作业,并将其调度到不同的辅助角色节点。There is only one dispatcher node, which is used to pull tasks/jobs from cloud services and dispatch them to different worker nodes. 调度程序节点也是一个辅助角色节点。The dispatcher node is also a worker node.

属性的某些设置更适用于自承载集成运行时中包含两个或两个以上节点的情况(即,在横向扩展方案中)。Some settings of the properties make more sense when there are two or more nodes in the self-hosted integration runtime (that is, in a scale out scenario).

并发作业限制Concurrent jobs limit

并发作业限制的默认值是根据计算机大小设置的。The default value of the concurrent jobs limit is set based on the machine size. 用于计算此值的因素取决于计算机的 RAM 量和 CPU 内核数。The factors used to calculate this value depend on the amount of RAM and the number of CPU cores of the machine. 因此,内核越多,内存越多,并发作业的默认限制就越高。So the more cores and the more memory, the higher the default limit of concurrent jobs.

可以通过增加节点数进行横向扩展。You scale out by increasing the number of nodes. 增加节点数时,并发作业限制为所有可用节点的并发作业限制值的总和。When you increase the number of nodes, the concurrent jobs limit is the sum of the concurrent job limit values of all the available nodes. 例如,如果一个节点允许运行最多 12 个并发作业,那么再添加三个类似节点将允许运行最多 48 个并发作业(即 4 x 12)。For example, if one node lets you run a maximum of twelve concurrent jobs, then adding three more similar nodes lets you run a maximum of 48 concurrent jobs (that is, 4 x 12). 建议仅在以下情况下提高并发作业限制:在每个节点上使用默认值时,资源使用率较低。We recommend that you increase the concurrent jobs limit only when you see low resource usage with the default values on each node.

可以在 Azure 门户中覆盖计算得出的默认值。You can override the calculated default value in the Azure portal. 选择“创建者”>“连接”>“集成运行时”>“编辑”>“节点”>“修改每个节点的并发作业值”。Select Author > Connections > Integration Runtimes > Edit > Nodes > Modify concurrent job value per node. 也可以使用 PowerShell update-Azdatafactoryv2integrationruntimenode 命令。You can also use the PowerShell update-Azdatafactoryv2integrationruntimenode command.

状态(每个节点)Status (per node)

下表提供了自承载集成运行时节点的可能状态:The following table provides possible statuses of a self-hosted integration runtime node:

状态Status 说明Description
联机Online 节点已连接到数据工厂服务。Node is connected to the Data Factory service.
OfflineOffline 节点处于脱机状态。Node is offline.
正在升级Upgrading 节点正在进行自动更新。The node is being auto-updated.
受限制Limited 由于连接问题而受限。Due to a connectivity issue. 可能的原因包括 HTTP 端口 8050 问题、服务总线连接问题或凭据同步问题。May be due to HTTP port 8050 issue, service bus connectivity issue, or a credential sync issue.
非活动Inactive 节点的配置与其他多数节点的配置不同。Node is in a configuration different from the configuration of other majority nodes.

节点在无法与其他节点连接时可能处于非活动状态。A node can be inactive when it cannot connect to other nodes.

状态(整个自承载集成运行时)Status (overall self-hosted integration runtime)

下表提供了自承载集成运行时的可能状态:The following table provides possible statuses of a self-hosted integration runtime. 此状态取决于属于运行时的所有节点的状态。This status depends on statuses of all nodes that belong to the runtime.

状态Status 说明Description
需要注册Need Registration 尚未将任何节点注册到此自承载集成运行时。No node is registered to this self-hosted integration runtime yet.
联机Online 所有节点处于联机状态。All nodes are online.
OfflineOffline 没有任何节点处于联机状态。No node is online.
受限制Limited 此自承载集成运行时中的所有节点并非全都处于正常状态。Not all nodes in this self-hosted integration runtime are in a healthy state. 此状态是一种警告,表示某些节点可能已关闭。This status is a warning that some nodes might be down. 此状态的可能原因是调度程序/辅助角色节点上出现凭据同步问题。This status could be due to a credential sync issue on dispatcher/worker node.

使用 Get-AzDataFactoryV2IntegrationRuntimeMetric cmdlet 提取包含详细自承载集成运行时属性,以及执行该 cmdlet 期间这些属性的快照值的 JSON 有效负载。Use the Get-AzDataFactoryV2IntegrationRuntimeMetric cmdlet to fetch the JSON payload containing the detailed self-hosted integration runtime properties, and their snapshot values during the time of execution of the cmdlet.

Get-AzDataFactoryV2IntegrationRuntimeMetric -name $integrationRuntimeName -ResourceGroupName $resourceGroupName -DataFactoryName $dataFactoryName | ConvertTo-Json 

示例输出(假设有两个节点与此自承载集成运行时关联):Sample output (assumes that there are two nodes associated with this self-hosted integration runtime):

{
    "IntegrationRuntimeName":  "<Name of your integration runtime>",
    "ResourceGroupName":  "<Resource Group Name>",
    "DataFactoryName":  "<Data Factory Name>",
    "Nodes":  [
        {
            "NodeName":  "<Node Name>",
            "AvailableMemoryInMB":  <Value>,
            "CpuUtilization":  <Value>,
            "ConcurrentJobsLimit":  <Value>,
            "ConcurrentJobsRunning":  <Value>,
            "MaxConcurrentJobs":  <Value>,
            "SentBytes":  <Value>,
            "ReceivedBytes":  <Value>
        },
        {
            "NodeName":  "<Node Name>",
            "AvailableMemoryInMB":  <Value>,
            "CpuUtilization":  <Value>,
            "ConcurrentJobsLimit":  <Value>,
            "ConcurrentJobsRunning":  <Value>,
            "MaxConcurrentJobs":  <Value>,
            "SentBytes":  <Value>,
            "ReceivedBytes":  <Value>
        }

    ]
} 

Azure-SSIS 集成运行时Azure-SSIS integration runtime

Azure-SSIS IR 是完全托管的 Azure 虚拟机(VM 或节点)群集,专用于运行 SSIS 包。Azure-SSIS IR is a fully managed cluster of Azure virtual machines (VMs or nodes) dedicated to run your SSIS packages. 你可以使用各种方法对 Azure-SSIS IR 调用 SSIS 包执行:例如通过启用了 Azure 的 SQL Server Data Tools (SSDT)、AzureDTExec 命令行实用工具、SQL Server Management Studio (SSMS)/SQL Server 代理上的 T-SQL,以及 ADF 管道中的执行 SSIS 包活动。You can invoke SSIS package executions on Azure-SSIS IR using various methods, for example via Azure-enabled SQL Server Data Tools (SSDT), AzureDTExec command line utility, T-SQL on SQL Server Management Studio (SSMS)/SQL Server Agent, and Execute SSIS Package activities in ADF pipelines. Azure-SSIS IR 不会运行任何其他 ADF 活动。Azure-SSIS IR doesn't run any other ADF activities. 预配后,可以通过 Azure PowerShell、Azure 门户和 Azure Monitor 监视其总体/特定于节点的属性和状态。Once provisioned, you can monitor its overall/node-specific properties and statuses via Azure PowerShell, Azure portal, and Azure Monitor.

使用 Azure PowerShell 监视 Azure-SSIS 集成运行时Monitor the Azure-SSIS integration runtime with Azure PowerShell

使用以下 Azure PowerShell cmdlet 监视 Azure-SSIS IR 的总体/特定于节点的属性和状态。Use the following Azure PowerShell cmdlet to monitor the overall/node-specific properties and statuses of Azure-SSIS IR.

Get-AzDataFactoryV2IntegrationRuntime -DataFactoryName $DataFactoryName -Name $AzureSSISName -ResourceGroupName $ResourceGroupName -Status

属性Properties

下表说明上述 cmdlet 针对 Azure-SSIS IR 返回的属性。The following table provides descriptions of properties returned by the above cmdlet for an Azure-SSIS IR.

属性/状态Property/Status 说明Description
CreateTimeCreateTime Azure-SSIS IR 的创建时间(UTC 时间)。The UTC time when your Azure-SSIS IR was created.
NodesNodes Azure-SSIS IR 的已分配/可用节点,带有特定于节点的状态(正在启动/可用/正在回收/不可用)和可采取措施的错误。The allocated/available nodes of your Azure-SSIS IR with node-specific statuses (starting/available/recycling/unavailable) and actionable errors.
OtherErrorsOtherErrors Azure-SSIS IR 上发生的非特定于节点且可采取措施的错误。The non-node-specific actionable errors on your Azure-SSIS IR.
LastOperationLastOperation 上次对 Azure-SSIS IR 执行的启动/停止操作的结果;如果失败,将出现可采取措施的错误。The result of last start/stop operation on your Azure-SSIS IR with actionable error(s) if it failed.
状态State Azure-SSIS IR 的总体状态(初始化/正在启动/已启动/正在停止/已停止)。The overall status (initial/starting/started/stopping/stopped) of your Azure-SSIS IR.
位置Location Azure-SSIS IR 的位置。The location of your Azure-SSIS IR.
NodeSizeNodeSize Azure-SSIS IR 中每个节点的大小。The size of each node in your Azure-SSIS IR.
NodeCountNodeCount Azure-SSIS IR 中的节点数目。The number of nodes in your Azure-SSIS IR.
MaxParallelExecutionsPerNodeMaxParallelExecutionsPerNode Azure-SSIS IR 中每个节点的最大并行执行数。The maximum number of parallel executions per node in your Azure-SSIS IR.
CatalogServerEndpointCatalogServerEndpoint 用于托管 SSIS 目录 (SSISDB) 的现有 Azure SQL Database 服务器或托管实例的终结点。The endpoint of your existing Azure SQL Database server or managed instance to host SSIS catalog (SSISDB).
CatalogAdminUserNameCatalogAdminUserName 现有 Azure SQL Database 服务器或托管实例的管理员用户名。The admin username for your existing Azure SQL Database server or managed instance. ADF 使用此信息来代你准备和管理 SSISDB。ADF uses this information to prepare and manage SSISDB on your behalf.
CatalogAdminPasswordCatalogAdminPassword 现有 Azure SQL Database 服务器或托管实例的管理员密码。The admin password for your existing Azure SQL Database server or managed instance.
CatalogPricingTierCatalogPricingTier Azure SQL Database 服务器托管的 SSISDB 的定价层。The pricing tier for SSISDB hosted by Azure SQL Database server. 不适用于 Azure SQL 托管实例承载 SSISDB。Not applicable to Azure SQL Managed Instance hosting SSISDB.
VNetIdVNetId Azure-SSIS IR 要加入的虚拟网络资源 ID。The virtual network resource ID for your Azure-SSIS IR to join.
子网Subnet Azure-SSIS IR 要加入的子网名称。The subnet name for your Azure-SSIS IR to join.
IDID Azure-SSIS IR 的资源 ID。The resource ID of your Azure-SSIS IR.
类型Type Azure-SSIS IR 的 IR 类型(托管/自承载)。The IR type (Managed/Self-Hosted) of your Azure-SSIS IR.
ResourceGroupNameResourceGroupName 在其中创建了 ADF 和 Azure-SSIS IR 的 Azure 资源组的名称。The name of your Azure Resource Group, in which your ADF and Azure-SSIS IR were created.
DataFactoryNameDataFactoryName ADF 的名称。The name of your ADF.
名称Name Azure-SSIS IR 的名称。The name of your Azure-SSIS IR.
说明Description Azure-SSIS IR 的说明。The description of your Azure-SSIS IR.

状态(每个 Azure-SSIS IR 节点)Status (per Azure-SSIS IR node)

下表提供了 Azure-SSIS IR 节点的可能状态:The following table provides possible statuses of an Azure-SSIS IR node:

特定于节点的状态Node-specific status 说明Description
正在启动Starting 正在准备此节点。This node is being prepared.
可用Available 此节点已准备就绪,可在其中部署/执行 SSIS 包。This node is ready for you to deploy/execute SSIS packages.
RecyclingRecycling 正在修复/重启此节点。This node is being repaired/restarting.
不可用Unavailable 此节点未准备就绪,不能在其中部署/执行 SSIS 包,并出现了可采取措施解决的错误/问题。This node isn't ready for you to deploy/execute SSIS packages and has actionable errors/issues that you could resolve.

状态(整个 Azure-SSIS IR)Status (overall Azure-SSIS IR)

下表提供了 Azure-SSIS IR 的可能整体状态。The following table provides possible overall statuses of an Azure-SSIS IR. 整体状态又取决于属于 Azure-SSIS IR 的所有节点的组合状态。The overall status in turn depends on the combined statuses of all nodes that belong to the Azure-SSIS IR.

总体状态Overall status 说明Description
初始Initial 尚未分配/准备 Azure-SSIS IR 的节点。The nodes of your Azure-SSIS IR haven't been allocated/prepared.
正在启动Starting 正在分配/准备 Azure-SSIS IR 的节点,计费已开始。The nodes of your Azure-SSIS IR are being allocated/prepared and billing has started.
StartedStarted 已分配/准备 Azure-SSIS IR 的节点,并可以在其中部署/执行 SSIS 包。The nodes of your Azure-SSIS IR have been allocated/prepared and they are ready for you to deploy/execute SSIS packages.
正在停止Stopping 正在释放 Azure-SSIS IR 的节点。The nodes of your Azure-SSIS IR are being released.
已停止Stopped 已释放 Azure-SSIS IR 的节点,计费已停止。The nodes of your Azure-SSIS IR have been released and billing has stopped.

在 Azure 门户中监视 Azure-SSIS 集成运行时Monitor the Azure-SSIS integration runtime in Azure portal

若要在 Azure 门户中监视 Azure-SSIS IR,请转到 ADF UI 上“监视”中心的“集成运行时”页,在其中可以看到所有集成运行时 。To monitor your Azure-SSIS IR in Azure portal, go to the Integration runtimes page of Monitor hub on ADF UI, where you can see all of your integration runtimes.

监视所有集成运行时

接下来,选择 Azure-SSIS IR 的名称以打开其监视页,可以在其中查看其整体/特定于节点的属性和状态。Next, select the name of your Azure-SSIS IR to open its monitoring page, where you can see its overall/node-specific properties and statuses. 在本页上,你将看到各种信息/功能磁贴,具体取决于你如何配置 Azure-SSIS IR 的“常规”、“部署”和“高级设置”。On this page, depending on how you configure the general, deployment, and advanced settings of your Azure-SSIS IR, you'll find various informational/functional tiles. “类型”和“区域”信息磁贴分别显示 Azure-SSIS IR 的类型和区域 。The TYPE and REGION informational tiles show the type and region of your Azure-SSIS IR, respectively. “节点大小”信息磁贴显示了 SKU(SSIS 版本/VM 层/VM 系列)、CPU 内核数以及 Azure-SSIS IR 每个节点的 RAM 大小。The NODE SIZE informational tile shows the SKU (SSIS edition_VM tier_VM series), number of CPU cores, and size of RAM per node for your Azure-SSIS IR. “正在运行/已请求的节点”信息磁贴比较当前正在运行的节点数与先前为 Azure-SSIS IR 请求的节点总数。The RUNNING / REQUESTED NODE(S) informational tile compares the number of nodes currently running to the total number of nodes previously requested for your Azure-SSIS IR. 下面将更详细地介绍功能磁贴。The functional tiles are described in more details below.

监视 Azure-SSIS IR

“状态”磁贴STATUS tile

在 Azure-SSIS IR 监视页的“状态”磁贴上,可以查看其总体状态,例如“正在运行”或“已停止” 。On the STATUS tile of your Azure-SSIS IR monitoring page, you can see its overall status, for example Running or Stopped. 选择“正在运行”状态会弹出一个窗口,窗口中有实时“停止”按钮以停止 Azure-SSIS IR 。Selecting the Running status pops up a window with live Stop button to stop your Azure-SSIS IR. 选择“已停止”状态会弹出一个窗口,窗口中有实时“启动”按钮以启动 Azure-SSIS IR 。Selecting the Stopped status pops up a window with live Start button to start your Azure-SSIS IR. 弹出窗口还有一个“执行 SSIS 包”按钮和一个“资源 ID”文本框,前者用于使用在 Azure-SSIS IR 上运行的“执行 SSIS 包”活动自动生成一个 ADF 管道(请参阅在 ADF 管道中以“执行 SSIS 包”活动形式运行 SSIS 包),后者用于复制 Azure-SSIS IR 资源 ID (/subscriptions/YourAzureSubscripton/resourcegroups/YourResourceGroup/providers/Microsoft.DataFactory/factories/YourADF/integrationruntimes/YourAzureSSISIR) 。The pop-up window also has an Execute SSIS package button to auto-generate an ADF pipeline with Execute SSIS Package activity that runs on your Azure-SSIS IR (see Running SSIS packages as Execute SSIS Package activities in ADF pipelines) and a Resource ID text box, from which you can copy your Azure-SSIS IR resource ID (/subscriptions/YourAzureSubscripton/resourcegroups/YourResourceGroup/providers/Microsoft.DataFactory/factories/YourADF/integrationruntimes/YourAzureSSISIR). 包含 ADF 和 Azure-SSIS IR 名称的 Azure-SSIS IR 资源 ID 的后缀构成一个群集 ID,可使用该 ID 从独立软件供应商 (ISV) 购买其他高级/已许可的 SSIS 组件,并将它们绑定到 Azure-SSIS IR(请参阅在 Azure-SSIS IR 上安装高级/已许可的组件)。The suffix of your Azure-SSIS IR resource ID that contains your ADF and Azure-SSIS IR names forms a cluster ID that can be used to purchase additional premium/licensed SSIS components from independent software vendors (ISVs) and bind them to your Azure-SSIS IR (see Installing premium/licensed components on your Azure-SSIS IR).

监视 Azure-SSIS IR - 状态磁贴

“SSISDB 服务器终结点”磁贴SSISDB SERVER ENDPOINT tile

如果你使用项目部署模型,其中包存储在由 Azure SQL Database 服务器或托管实例托管的 SSISDB 中,则可在 Azure-SSIS IR 监视页上看到“SSISDB 服务终结点”磁贴(请参阅配置 Azure-SSIS IR 部署设置)。If you use Project Deployment Model where packages are stored in SSISDB hosted by your Azure SQL Database server or managed instance, you'll see the SSISDB SERVER ENDPOINT tile on your Azure-SSIS IR monitoring page (see Configuring your Azure-SSIS IR deployment settings). 在此磁贴上,你可以选择一个指定 Azure SQL Database 服务器或托管实例的链接以弹出一个窗口,你可以在其中从一个文本框中复制服务器终结点,并在从 SSMS 连接时使用它来部署、配置、运行和管理包。On this tile, you can select a link designating your Azure SQL Database server or managed instance to pop up a window, where you can copy the server endpoint from a text box and use it when connecting from SSMS to deploy, configure, run, and manage your packages. 在该弹出窗口中,你还可以选择“查看 Azure SQL 数据库或托管实例设置”链接以在 Azure 门户中重新配置 SSISDB/重设 SSISDB 的大小。On the pop-up window, you can also select the See your Azure SQL Database or managed instance settings link to reconfigure/resize your SSISDB in Azure portal.

监视 Azure-SSIS IR - SSISDB 磁贴

“代理/暂存”磁贴PROXY / STAGING tile

如果下载、安装和配置自承载 IR (SHIR) 作为 Azure-SSIS IR 的代理来访问本地数据,你将在 Azure-SSIS IR 监视页面上看到“代理/暂存”磁贴(请参阅将 SHIR 配置为 Azure-SSIS IR 的代理)。If you download, install, and configure Self-Hosted IR (SHIR) as a proxy for your Azure-SSIS IR to access data on premises, you'll see the PROXY / STAGING tile on your Azure-SSIS IR monitoring page (see Configuring SHIR as a proxy for your Azure-SSIS IR). 在此磁贴上,你可以选择一个指定 SHIR 的链接,以打开其监视页面。On this tile, you can select a link designating your SHIR to open its monitoring page. 还可以选择另一个指定用于暂存的 Azure Blob 存储的链接,以重新配置其链接服务。You can also select another link designating your Azure Blob Storage for staging to reconfigure its linked service.

“验证 VNET/子网”磁贴VALIDATE VNET / SUBNET tile

如果你将 Azure-SSIS IR 加入 VNet,可在 Azure-SSIS IR 监视页上看到“验证 VNET/子网”磁贴(请参阅将 Azure-SSIS IR 加入 VNet)。If you join your Azure-SSIS IR to a VNet, you'll see the VALIDATE VNET / SUBNET tile on your Azure-SSIS IR monitoring page (see Joining your Azure-SSIS IR to a VNet). 在此磁贴上,你可以选择一个指定 VNet 和子网的链接以弹出一个窗口,你可以在其中从文本框中复制 VNet 资源 ID (/subscriptions/YourAzureSubscripton/resourceGroups/YourResourceGroup/providers/Microsoft.Network/virtualNetworks/YourARMVNet) 和子网名称,还可以验证 VNet 和子网配置,以确保所需的入站/出站网络流量和 Azure-SSIS IR 的管理不受阻碍。On this tile, you can select a link designating your VNet and subnet to pop up a window, where you can copy your VNet resource ID (/subscriptions/YourAzureSubscripton/resourceGroups/YourResourceGroup/providers/Microsoft.Network/virtualNetworks/YourARMVNet) and subnet name from text boxes, as well as validate your VNet and subnet configurations to ensure that the required inbound/outbound network traffics and management of your Azure-SSIS IR aren't obstructed.

监视 Azure-SSIS IR - 验证磁贴

“诊断连接”磁贴DIAGNOSE CONNECTIVITY tile

在 Azure-SSIS IR 监视页的“诊断连接”磁贴上,可以选择“测试连接”链接以弹出一个窗口,你可以在其中通过完全限定的域名 (FQDN)/IP 地址和指定端口检查 Azure-SSIS IR 和相关的包/配置/数据存储以及管理服务之间的连接(请参阅测试来自 Azure-SSIS 的连接) 。On the DIAGNOSE CONNECTIVITY tile of your Azure-SSIS IR monitoring page, you can select the Test connection link to pop up a window, where you can check the connections between your Azure-SSIS IR and relevant package/configuration/data stores, as well as management services, via their fully qualified domain name (FQDN)/IP address and designated port (see Testing connections from your Azure-SSIS IR).

监视 Azure-SSIS IR - 诊断磁贴

“静态公共 IP 地址”磁贴STATIC PUBLIC IP ADDRESSES tile

如果为 Azure-SSIS IR 提供了自己的静态公共 IP 地址,则会在 Azure-SSIS IR 监视页面上看到“静态公共 IP 地址”磁贴(请参阅为 Azure-SSIS IR 提供自己的静态公共 IP 地址)。If you bring your own static public IP addresses for Azure-SSIS IR, you'll see the STATIC PUBLIC IP ADDRESSES tile on your Azure-SSIS IR monitoring page (see Bringing your own static public IP addresses for Azure-SSIS IR). 在此磁贴上,你可以选择为 Azure-SSIS IR 指定第一个/第二个静态公共 IP 地址的链接,以弹出一个窗口,并可在窗口的文本框中复制其资源 ID (/subscriptions/YourAzureSubscripton/resourceGroups/YourResourceGroup/providers/Microsoft.Network/publicIPAddresses/YourPublicIPAddress)。On this tile, you can select links designating your first/second static public IP addresses for Azure-SSIS IR to pop up a window, where you can copy their resource ID (/subscriptions/YourAzureSubscripton/resourceGroups/YourResourceGroup/providers/Microsoft.Network/publicIPAddresses/YourPublicIPAddress) from a text box. 在弹出窗口中,你还可以选择“查看第一个/第二个静态公共 IP 地址设置”链接,以管理 Azure 门户中的第一个/第二个静态公共 IP 地址。On the pop-up window, you can also select the See your first/second static public IP address settings link to manage your first/second static public IP address in Azure portal.

监视 Azure-SSIS IR - 诊断磁贴

“包存储”磁贴PACKAGE STORES tile

如果你使用包部署模型,其中包存储在由 Azure SQL 托管实例托管并通过 Azure-SSIS IR 包存储进行管理的文件系统/Azure 文件/SQL Server 数据库 (MSDB) 中,则可在 Azure-SSIS IR 监视页上看到“包存储”磁贴(请参阅配置 Azure-SSIS IR 部署设置)。If you use Package Deployment Model where packages are stored in file system/Azure Files/SQL Server database (MSDB) hosted by your Azure SQL Managed Instance and managed via Azure-SSIS IR package stores, you'll see the PACKAGE STORES tile on your Azure-SSIS IR monitoring page (see Configuring your Azure-SSIS IR deployment settings). 在此磁贴上,可以选择一个指定附加到 Azure-SSIS IR 的包存储数的链接以弹出一个窗口,你可以在其中在由 Azure SQL 托管实例托管的文件系统/Azure 文件/MSDB 上为 Azure-SSIS IR 包存储重新配置相关的链接服务。On this tile, you can select a link designating the number of package stores attached to your Azure-SSIS IR to pop up a window, where you can reconfigure the relevant linked services for your Azure-SSIS IR package stores on top of file system/Azure Files/MSDB hosted by your Azure SQL Managed Instance.

监视 Azure-SSIS IR - 包磁贴

“错误”磁贴ERROR(S) tile

如果 Azure-SSIS IR 的启动/停止/维护/升级存在问题,可在 Azure-SSIS IR 监视页上看到一个附加的“错误”磁贴。If there are issues with the starting/stopping/maintenance/upgrade of your Azure-SSIS IR, you'll see an additional ERROR(S) tile on your Azure-SSIS IR monitoring page. 在此磁贴上,你可以选择一个指定由 Azure-SSIS IR 生成的错误数的链接以弹出一个窗口,你可以在其中详细了解这些错误并进行复制,以在我们的疑难解答指南中找到推荐的解决方案(请参阅对 Azure-SSIS IR 进行故障排除)。On this tile, you can select a link designating the number of errors generated by your Azure-SSIS IR to pop up a window, where you can see those errors in more details and copy them to find the recommended solutions in our troubleshooting guide (see Troubleshooting your Azure-SSIS IR).

监视 Azure-SSIS IR - 诊断磁贴

使用 Azure Monitor 监视 Azure-SSIS 集成运行时Monitor the Azure-SSIS integration runtime with Azure Monitor

若要使用 Azure Monitor 监视 Azure-SSIS IR,请参阅使用 Azure Monitor 监视 SSIS 操作To monitor your Azure-SSIS IR with Azure Monitor, see Monitoring SSIS operations with Azure Monitor.

有关 Azure-SSIS 集成运行时的详细信息More info about the Azure-SSIS integration runtime

请参阅以下文章了解有关 Azure-SSIS 集成运行时的详细信息:See the following articles to learn more about Azure-SSIS integration runtime:

后续步骤Next steps

参阅以下文章,了解不同的管道监视方法:See the following articles for monitoring pipelines in different ways: