Playbook and automation

Active and total playbooks

Displays: Simple counts of playbook availability and activation status.

Business Value: Provides a quick overview of automation resources available in the system.

Metrics Displayed:

  • Total Playbooks: All playbooks that are not disabled

    Count of all playbooks where disabled = false

  • Active Playbooks: Playbooks currently enabled and running

    Count of all playbooks where active = true

Example

CODE 
Total Playbooks: 45
Active Playbooks: 38

In this example, 38 out of 45 available playbooks are currently active and can respond to events.

Time Period: None (current state snapshot)

Filters Applied:

  • Optional data source label

  • Tenant (for multi-tenant environments)

Executed playbooks and actions

Displays: Time-series trends showing automation activity levels over time.

Business Value: Tracks automation adoption and usage patterns.

Metrics Displayed:

  • Total Playbook Runs: Cumulative playbook executions in the period

    Sum of all playbook executions across all time periods

  • Total Action Runs: Cumulative action executions in the period

    Sum of all action executions across all time periods

  • Average per Time Period: Mean executions per selected time unit

    Average = Total Executions ÷ Number of Time Periods

  • Trend Lines: Visual representation over time

Example (7-day view)

CODE 
Playbook Runs:
  - Total: 456 runs over 7 days
  - Average: 456 ÷ 7 = 65.1 runs per day

Action Runs:
  - Total: 1,200 actions over 7 days
  - Average: 1,200 ÷ 7 = 171.4 actions per day

Time Period: Selectable (hourly, daily, or monthly)

Filters Applied:

  • Date range

  • Container labels

  • Tenant (for multi-tenant environments)

Top playbooks and actions

Displays: The 20 most frequently executed playbooks and individual actions, with performance metrics for each.

Business Value: Identifies which automations provide the most value and helps optimize commonly-used workflows.

Metrics Displayed:

For Playbooks:

  • Execution Count: Number of times the playbook ran

  • Total Actions: Sum of all actions executed across all runs

  • Average Actions per Run: Typical number of actions in one execution

    Avg Actions = Total Actions Executed ÷ Number of Playbook Runs

    Example:

    • Playbook ran 245 times

    • Total actions executed: 890

    • Average actions per run = 890 ÷ 245 = 3.6 actions

  • Average Duration: Mean execution time in seconds

    Avg Duration = Sum of all execution times ÷ Number of executions

    Example:

    • Email action ran 1,200 times

    • Total time: 2,760 seconds

    • Average duration = 2,760 ÷ 1,200 = 2.3 seconds per execution

For Actions:

  • Execution Count: Number of times the action ran

  • Average Duration: Mean execution time in seconds

    Avg Duration = Sum of all execution times ÷ Number of executions

    See example in previous section for playbooks.