Monitor Orchestrate Usage
The Orchestrate Usage page provides a comprehensive view of your Orchestrate plan, tenant details, action execution metrics, usage trend graphs, and more. These insights help you monitor consumption, identify patterns, and optimize resource planning. To view Orchestrate usage, from the Cyware Central home page, go to Admin Settings > Account Management > Usage.
You can view the following details in Orchestrate Usage:
Plan & Usage Details
You can view the following details in Plan & Usage Details:
Current Plan: View your current Orchestrate plan. For example, Cyware Free Tier.
Current Month Usage: View the total number of actions executed in the current month and the monthly execution limit. Running a node in a playbook is considered one action execution. Similarly, executing an action directly from an app is also considered an action execution. For example, a playbook with 5 nodes looping 3 times results in 15 executions.
Note
In the Cyware Free Tier plan, you can run up to 75,000 action executions per month.
Tenant Details
You can view the following details in Tenant Details:
Tenant ID: View the Unique identifier of your Orchestrate account.
Tenant Name: View the tenant name of your Orchestrate account.
Tenant Version: View the current version of your Orchestrate application. For example, 3.12.4.
Usage Trend
The Usage Trend chart provides a visual overview of action executions, triggered either by playbooks or as direct actions. You can search and filter by specific playbooks or actions to analyze their execution trends. Note that all calculations are based on Coordinated Universal Time (UTC).
You can customize the usage trend chart using the following options:
Chart Type: Click the Change Chart Type icon to switch between Stack and Line charts.
Date Range: Click the calendar icon to choose from Current Month, Past Month, Past 3 Months, or Past 6 Months. By default, the data for the Current Month is selected.
In the table view, you can view playbooks and actions with their corresponding action execution counts. Sort the list in ascending or descending order, and click a playbook or action name to open it in a new tab.
Running a node in a playbook is considered one action execution. Similarly, executing an action directly from an app is also considered an action execution. For example, if you run a playbook with 3 nodes and each node loops 2 times, the total usage will be 6 action executions.
Each loop iteration is counted separately. So, running one node in a loop 5 times will consume 5 action executions.
Action executions are counted at the node level. When a sub-playbook node runs, it triggers all nodes inside it. So, if the sub-playbook has 10 nodes, the total count will be 10 action executions, not 1.
In the Free Tier plan, your account includes a monthly quota of 75,000 executions. After you exceed this limit, action executions will continue without interruption, and the Cyware Support team will contact you to discuss next steps.