Playbook Run Statistics for Function-Block Performance Visibility

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users of IT and security operations applications lack visibility into the performance statistics of playbook executions, limiting their ability to diagnose runtime issues and inefficiencies in automated security and IT workflows.

Innovation Solution

An IT and security operations application provides users with the ability to collect and display playbook run statistics, enabling comparison of individual function blocks and playbook runs to identify and troubleshoot performance issues.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If playbook executions are automated without monitoring, then productivity is improved through automation, but measurement precision deteriorates due to lack of performance visibility

Engineering Contradiction:
Improveautomation efficiencyVSAvoidperformance statistics visibility
Core Design Contradiction:
ProductivityVSMeasurement precision

Solution Approach 1:

The patent implements feedback mechanisms by collecting execution statistics from playbook runs and presenting them to users through interfaces. The system monitors function block execution metrics, success/failure rates, and runtime performance, then feeds this information back to users via dashboards and reports, enabling data-driven optimization of automated workflows

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent introduces an intermediary statistics collection and presentation layer between the playbook execution engine and users. This intermediary component captures execution data, processes it into meaningful metrics, and presents it through user interfaces, bridging the gap between automated execution and human analysis without interfering with the automation itself

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If detailed monitoring of function blocks is implemented, then measurement precision is improved, but device complexity increases due to additional monitoring infrastructure

Engineering Contradiction:
Improvefunction block performance measurementVSAvoidmonitoring system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent merges the statistics collection functionality directly into the existing playbook execution engine. Rather than adding separate monitoring infrastructure, the system combines execution and measurement functions, with the playbook engine simultaneously executing function blocks and collecting their performance metrics, reducing overall system complexity

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements self-service monitoring where the playbook execution system automatically collects its own performance statistics without external monitoring tools. The execution engine introspects its own operations, gathering metrics on function block execution, resource usage, and performance, eliminating the need for separate monitoring agents or infrastructure

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20250323933A1Generating playbook run statistics for playbooks executed by an information technology and security operations application
Publication Date: 2025.10.16 CISCO TECHNOLOGY INC
  • US20250323933A1 patent drawing
  • US20250323933A1 patent drawing
  • US20250323933A1 patent drawing

AI summary

Techniques provide users of an IT and security operations application with the ability to enable the collection and display of playbook run statistics. Users can selectively enable the generation of playbook run statistics for individual playbooks. Once enabled for a playbook, the IT and security operations application automatically adds source code to the playbook or otherwise enables the collection of function block-level statistics during playbook executions. Users can view the statistics collected for a playbook to compare the performance of individual blocks against one another, to compare the performance of individual playbook runs against other playbook runs or against an average of all playbook runs, and so forth. The ability to obtain playbook run statistics enables users to learn how their playbooks are performing and to troubleshoot potential issues, thereby improving the performance of playbooks and the security and operation of the IT environments in which playbooks are deployed.