Azure 逻辑应用的定价模型Pricing model for Azure Logic Apps

借助 Azure 逻辑应用可以创建和运行可在云中缩放的自动化集成工作流。Azure Logic Apps helps you create and run automated integration workflows that can scale in the cloud. 本文介绍 Azure 逻辑应用的计费和定价方式。This article describes how billing and pricing work for Azure Logic Apps. 有关定价费率,请参阅逻辑应用定价For pricing rates, see Logic Apps Pricing.

消耗量定价模型Consumption pricing model

对于在公共的“全局”多租户 Azure 逻辑应用服务中运行的新逻辑应用,只需根据实际使用的资源付费。For new logic apps that run in the public, "global", multi-tenant Azure Logic Apps service, you pay only for what you use. 这些逻辑应用使用基于消耗量的计划和定价模型。These logic apps use a consumption-based plan and pricing model. 在逻辑应用中,每一步都是操作,而 Azure 逻辑应用会对逻辑应用中运行的所有操作进行计量。In your logic app, each step is an action, and Azure Logic Apps meters all the actions that run in your logic app.

例如,操作包括:For example, actions include:

标准连接器标准连接器价格收费。Standard connectors are charged at the Standard connector price. 正式发布的企业连接器企业连接器价格收费,而公共预览版企业连接器则按标准连接器价格收费。Generally available Enterprise connectors are charged at the Enterprise connector price, while public preview Enterprise connectors are charged at the Standard connector price.

详细了解如何在触发器操作级别计费。Learn more about how billing works at the triggers and actions levels. 或者参阅 Azure 逻辑应用的限制和配置,了解有关限制的信息。Or, for information about limits, see Limits and configuration for Azure Logic Apps.

连接器Connectors

Azure 逻辑应用连接器通过提供触发器和/或操作,帮助逻辑应用访问云中或本地的应用、服务和系统。Azure Logic Apps connectors help your logic app access apps, services, and systems in the cloud or on premises by providing triggers, actions, or both. 连接器分类为“标准”或“企业”连接器。Connectors are classified as either Standard or Enterprise. 有关这些连接器的概述,请参阅适用于 Azure 逻辑应用的连接器For an overview about these connectors, see Connectors for Azure Logic Apps. 如果没有预生成的连接器可用于要在逻辑应用中使用的 REST API,则可以创建自定义连接器,这些连接器只是这些 REST API 的包装器。If no prebuilt connectors are available for the REST APIs that you want to use in your logic apps, you can create custom connectors, which are just wrappers around those REST APIs. 自定义连接器按标准连接器计费。Custom connectors are billed as Standard connectors. 以下部分提供有关触发器和操作的计费方式的详细信息。The following sections provide more information about how billing for triggers and actions work.

触发器Triggers

触发器是发生特定事件时创建逻辑应用实例的特殊操作。Triggers are special actions that create a logic app instance when a specific event happens. 触发器以不同方式起作用,从而影响逻辑应用的计量方式。Triggers act in different ways, which affect how the logic app is metered. 下面是 Azure 逻辑应用中存在的各种触发器:Here are the various kinds of triggers that exist in Azure Logic Apps:

  • 轮询触发器:此触发器持续检查终结点是否收到满足创建逻辑应用实例和启动工作流的条件的消息。Polling trigger: This trigger continually checks an endpoint for messages that satisfy the criteria for creating a logic app instance and starting the workflow. 即使没有创建逻辑应用实例,逻辑应用也会将每个轮询请求计量为执行。Even when no logic app instance gets created, Logic Apps meters each polling request as an execution. 若要指定轮询间隔,请通过逻辑应用程序设计器设置触发器。To specify the polling interval, set up the trigger through the Logic App Designer.

    若要估计更准确的使用成本,请考虑任何给定天可能到达的消息或事件数,而不是仅基于轮询间隔进行计算。To estimate more accurate consumption costs, consider the possible number of messages or events that might arrive on any given day, rather than base your calculations on only the polling interval. 当某个事件或消息满足触发器条件时,许多触发器将立即尝试读取满足条件的任何和所有其他等待事件或消息。When an event or message meets the trigger criteria, many triggers immediately try to read any and all other waiting events or messages that meet the criteria. 此行为意味着,即使你选择较长的轮询间隔,触发器也基于符合启动工作流条件的等待事件或消息的数量进行触发。This behavior means that even when you select a longer polling interval, the trigger fires based on the number of waiting events or messages that qualify for starting workflows. 遵循此行为的触发器包括 Azure 服务总线和 Azure 事件中心。Triggers that follow this behavior include Azure Service Bus and Azure Event Hub.

    因此,例如,假设你设置了一个每天检查终结点的触发器。So, for example, suppose you set up trigger that checks an endpoint every day. 当触发器检查终结点并找到 15 个满足条件的事件时,触发器触发并运行相应工作流 15 次。When the trigger checks the endpoint and finds 15 events that meet the criteria, the trigger fires and runs the corresponding workflow 15 times. 逻辑应用会计量这 15 个工作流执行的所有操作,包括触发器请求。Logic Apps meters all the actions that those 15 workflows perform, including the trigger requests. 若要计算潜在成本,请尝试使用 Azure 定价计算器To calculate your potential costs, try the Azure pricing calculator.

  • Webhook 触发器:此触发器等待客户端向特定的终结点发送请求。Webhook trigger: This trigger waits for a client to send a request to a specific endpoint. 发送到 webhook 终结点的每个请求都会计为操作执行。Each request sent to the webhook endpoint counts as an action execution. 例如,请求和 HTTP Webhook 触发器都是 Webhook 触发器。For example, the Request and HTTP Webhook trigger are both webhook triggers.

  • 重复周期触发器:此触发器基于在触发器中设置的重复间隔创建逻辑应用实例。Recurrence trigger: This trigger creates a logic app instance based on the recurrence interval that you set up in the trigger. 例如,可以设置每隔三天运行的,或者根据更复杂的计划运行的定期触发器。For example, you can set up a Recurrence trigger that runs every three days or on a more complex schedule.

操作Actions

Azure 逻辑应用将 HTTP 等“内置”操作作为本机操作进行计量。Azure Logic Apps meters "built-in" actions, such as HTTP, as native actions. 例如,内置操作包括 HTTP 调用、来自 Azure Functions 或 API 管理的调用,以及条件、循环和开关语句等控制流步骤。For example, built-in actions include HTTP calls, calls from Azure Functions or API Management, and control flow steps such as conditions, loops, and switch statements. 每个操作具有自身的操作类型。Each action has their own action type. 例如,调用连接器的操作为“ApiConnection”类型。For example, actions that call connectors have the "ApiConnection" type. 这些连接器分类为“标准”或“企业”连接器,根据各自的定价进行计量。These connectors are classified as Standard or Enterprise connectors, which are metered based on their respective pricing. 预览版的企业连接器按标准连接器计费。Enterprise connectors in Preview are charged as Standard connectors.

Azure 逻辑应用将所有成功和不成功的操作作为执行进行计量。Azure Logic Apps meters all successful and unsuccessful actions as executions. 但是,逻辑应用不会计量以下操作:However, Logic Apps doesn't meter these actions:

  • 由于未满足条件而跳过的操作Actions that get skipped due to unmet conditions
  • 由于逻辑应用在完成之前停止而未运行的操作Actions that don't run because the logic app stopped before finishing

对于在循环内部运行的操作,Azure 逻辑应用会对循环中每个周期的每个操作进行计数。For actions that run inside loops, Azure Logic Apps counts each action for each cycle in the loop. 例如,假设有一个处理列表的“每个”循环。For example, suppose you have a "for each" loop that processes a list. 逻辑应用通过将列表项的数量乘以循环中的操作数来计量该循环中的操作,并加上启动循环的操作。Logic Apps meters an action in that loop by multiplying the number of list items with the number of actions in the loop, and adds the action that starts the loop. 因此,包含 10 个项的列表的计算公式为 (10 * 1) + 1,即 11 个操作执行。So, the calculation for a 10-item list is (10 * 1) + 1, which results in 11 action executions.

禁用的逻辑应用Disabled logic apps

禁用的逻辑应用在禁用期间不会产生费用,因为它们无法创建新实例。Disabled logic apps aren't charged because they can't create new instances while they're disabled. 禁用逻辑应用后,当前正在运行的实例可能需要在一段时间之后才会完全停止。After you disable a logic app, any currently running instances might take some time before they completely stop.

集成帐户Integration accounts

固定定价模型适用于集成帐户,此类帐户可用于免费浏览、开发和测试 Azure 逻辑应用中的 B2B 和 EDIXML 处理功能。A fixed pricing model applies to integration accounts where you can explore, develop, and test the B2B and EDI and XML processing features in Azure Logic Apps at no additional cost. 每个 Azure 订阅最多可以有一项集成帐户的特定限制Each Azure subscription can have up to a specific limit of integration accounts. 每个集成帐户的存储受到特定的项目限制,其中包含贸易合作伙伴、协议、映射、架构、程序集、证书、批处理配置等。Each integration account can store up to specific limit of artifacts, which include trading partners, agreements, maps, schemas, assemblies, certificates, batch configurations, and so on.

Azure 逻辑应用提供“基本”和“标准”集成帐户。Azure Logic Apps offers Basic, and Standard integration accounts. 逻辑应用服务级别协议 (SLA) 支持“基本”和“标准”层级,而“免费”层级则不受 SLA 支持并有区域可用性、吞吐量和使用方面的限制。The Basic and Standard tiers are supported by the Logic Apps service-level agreement (SLA), while the Free tier is not supported by an SLA and has limits on region availability, throughput, and usage. 每个 Azure 区域中可以有多个集成帐户,“免费”层级集成帐户除外。Except for Free tier integration accounts, you can have more than one integration account in each Azure region. 有关定价费率,请参阅逻辑应用定价For pricing rates, see Logic Apps pricing.

若要在“基本”或“标准”集成帐户之间进行选择,请查看以下用例说明:To choose between a Basic, or Standard integration account, review these use case descriptions:

  • 基本:适用于只需处理消息或充当与大型企业实体建立贸易合作关系的小型企业合作伙伴的情况Basic: For when you want only message handling or to act as a small business partner that has a trading partner relationship with a larger business entity

  • 标准:适用于 B2B 关系更复杂且需要管理的实体数增加的情况Standard: For when you have more complex B2B relationships and increased numbers of entities that you must manage

数据保留Data retention

存储在逻辑应用的运行历史记录中的所有输入和输出都将根据逻辑应用的运行保留期进行计费,在集成服务环境 (ISE) 中运行的逻辑应用除外。Except for logic apps that run in an integration service environment (ISE), all the inputs and outputs that are stored in your logic app's run history get billed based on a logic app's run retention period. 在 ISE 中运行的逻辑应用不会产生数据保留成本。Logic apps that run in an ISE don't incur data retention costs. 有关定价费率,请参阅逻辑应用定价For pricing rates, see Logic Apps pricing.

若要更好地监视逻辑应用的存储消耗,可以执行以下操作:To help you monitor your logic app's storage consumption, you can:

  • 查看逻辑应用每月使用的存储单元数(以 GB 为单位)。View the number of storage units in GB that your logic app uses monthly.
  • 在逻辑应用的运行历史记录中查看特定操作的输入和输出的大小。View the sizes for a specific action's inputs and outputs in your logic app's run history.

查看逻辑应用存储消耗View logic app storage consumption

  1. 在 Azure 门户中,查找并打开逻辑应用。In the Azure portal, find and open your logic app.

  2. 在逻辑应用的菜单中的“监视”下,选择“指标”。 From your logic app's menu, under Monitoring, select Metrics.

  3. 从右侧窗格的“图表标题”下的“指标”列表中,选择“按消耗存储的执行操作的使用情况计费”。 In the right-hand pane, under Chart Title, from the Metric list, select Billing Usage for Storage Consumption Executions.

    此指标表示每月计费的存储消耗单元数 (GB)。This metric gives you the number of storage consumption units in GB per month that are getting billed.

查看操作输入和输出大小View action input and output sizes

  1. 在 Azure 门户中,查找并打开逻辑应用。In the Azure portal, find and open your logic app.

  2. 在逻辑应用的菜单中,选择“概述”。On your logic app's menu, select Overview.

  3. 在右侧窗格的“运行历史记录”下,选择具有要检查的输入和输出的运行。In the right-hand pane, under Runs history, select the run that has the inputs and outputs you want to check.

  4. 在“逻辑应用运行”下,选择“运行详细信息”。Under Logic app run, choose Run Details.

  5. 在“逻辑应用运行详细信息”窗格的“操作表”中(其中列出了每个操作的状态和持续时间),选择要查看的操作。In the Logic app run details pane, in the actions table, which lists each action's status and duration, select the action you want to view.

  6. 在“逻辑应用操作”窗格中,找到该操作的输入和输出的大小(分别显示在“输入链接”和“输出链接”下)。In the Logic app action pane, find the sizes for that action's inputs and outputs appear respectively under Inputs link and Outputs link.

后续步骤Next steps