Dynamic Compute Node Scaling for Continuous Alert Grouping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing operations computing systems face inefficiencies in managing incident response alerts due to static compute node configurations, leading to slow grouping, inefficient resource allocation, and interruptions when changes occur in the compute node setup.

Innovation Solution

An operations computing system dynamically manages compute nodes using a clustering algorithm and machine learning models to group alerts, scaling resources based on demand, and reallocating services to optimize alert grouping by adding or removing compute nodes as needed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If compute nodes are statically configured to group alerts, then system simplicity is maintained, but alert grouping efficiency deteriorates and resource allocation becomes inefficient

Engineering Contradiction:
Improvealert grouping efficiencyVSAvoidcompute node management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system implements dynamic compute node configuration where compute nodes are added, removed, or reassigned based on real-time alert volume and system demand. This allows the infrastructure to adapt flexibly to changing workloads, improving alert grouping efficiency without permanent complexity increases.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system employs machine learning models and clustering algorithms that automatically analyze alert contexts and perform grouping without manual intervention. This self-service capability handles the complexity internally while presenting simple alert grouping outcomes to users.

Inventive Principle:
Principle #25Self-service

2Adaptability or versatility

If compute nodes are dynamically added and removed, then resource allocation efficiency is improved, but system stability deteriorates due to reassignment interruptions

Engineering Contradiction:
Improveresource scaling flexibilityVSAvoidalert grouping continuity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system shares alert group contexts to new compute nodes before they become active, ensuring continuity of alert grouping functionality. This preliminary action prevents interruptions by pre-configuring nodes with necessary context information.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system monitors compute node performance and alert patterns, using this feedback to determine optimal times for adding or removing nodes. This feedback mechanism ensures changes are made when they will have minimal impact on reliability.

Inventive Principle:
Principle #23Feedback

3Productivity

If more compute nodes are deployed to handle growing services, then alert grouping capacity increases, but storage requirements and infrastructure complexity increase

Engineering Contradiction:
Improvealert grouping capacityVSAvoidstorage requirements
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The system consolidates alert group contexts across compute nodes, allowing multiple nodes to share and reuse the same context data. This merging approach increases alert grouping capacity through parallel processing while minimizing duplicate storage requirements.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

Instead of storing complete alert group contexts on every compute node, the system creates lightweight copies or references to shared context data. This allows rapid node scaling while keeping individual node storage requirements minimal.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20250247314A1Managing alerts for incident response
Publication Date: 2025.07.31 PAGERDUTY INC
  • US20250247314A1 patent drawing
  • US20250247314A1 patent drawing
  • US20250247314A1 patent drawing

AI summary

Techniques are described for a system configured to assign one or more services to a first compute node of a set of compute nodes. The system may obtain an alert for a service. The system may determine an alert context for the alert. The system may add the alert to an alert group of a plurality of alert groups. The system may generate an updated alert group context for the alert group. The system may add a second compute node to the set of compute nodes. The system may provide a plurality of alert group contexts including the updated alert group context to the second compute node. The system may reassign at least one service to the second compute node based on an updated set of compute nodes, wherein the updated set of compute nodes is determined based on a change to the set of compute nodes.