ixp
latest
false

IXP 概述指南
上次更新日期 2025年9月16日
租户级消耗量
linkThe AI Units tenant consumption dashboard outlines the usage pattern of AI units specific to an individual tenant.
备注:
- 仪表板数据仅限于与组织位于同一区域的信息。
- 数据每 24 小时刷新一次。
- The name of the default tenant may be displayed as Unknown in the following scenarios:
- 租户是在组织使用社区版计划时创建的,但随后转到了企业版计划。
- If the data pertains to a different region than that of the organization.
- If the consumption data pertains to missing transactions, such as those with no job ID.
- If the value for the Orchestrator folder is displayed as Unknown, it means that there is no related data. This could result from using an outdated Robot or activity package version.
- 仪表板显示来自租户的所有数据。
- 仪表板显示来自以下其中一项的消耗数据:
- AI units allocated at the tenant level.
- 在组织级别分配的 AI Unit。 这仅适用于租户未获得分配的 AI Unit,但消耗事件有关联租户的情况。 例如,仪表板上显示的租户使用的 AI Unit 数量将与组织级别仪表板上显示的数字匹配。
筛选条件
linkUse the Date Range filter as follows:
- Presets - Select a specific time period to review the usage of AI Units.
- Custom - Manually enter a specific time period to review the usage of AI Units.
指标
linkThe following table describes the metrics for the AI Units tenant consumption dashboard:
平铺 | 描述 |
---|---|
按产品划分的消耗 | 按产品分组的已使用 AI Unit 总数:
|
按 Orchestrator 文件夹划分的消耗 | Total number of consumed AI units, distributed by the Orchestrator folder the automation is run.
Note: The value could be displayed as Unknown if there are suspended jobs. In this case, the entry is populated after the job resumes and the automation execution finishes.
If the value is displayed as N/A, this indicates that it is not applicable because the operation was carried out outside of an Orchestrator folder. |
按 Orchestrator 文件夹和产品划分的消耗 | Total number of consumed AI units, distributed by the Orchestrator folder the automation is run, and the product consuming these AI units. |
按自动化划分的消耗 | 使用的 AI Unit 总数,按自动化名称分组:
Note: If the value is displayed as Unknown, this means that there is no data for it.
If the value is displayed as N/A, this indicates that it is not applicable because the operation was carried out outside of an automation, Orchestrator folder. |