DevOps Event Timeline Visualization for Failure Pattern Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In DevOps management, previous approaches were time-consuming and inefficient in identifying and visualizing events across an application's lifecycle, leading to unnoticed systemic problems and prolonged identification of common failure reasons across multiple releases.

Innovation Solution

A graphical user interface (GUI) with visualization capabilities that allows users to see build failures caused by underlying system failures, automatically identifies patterns and correlations, and provides notifications for improving phases, enabling enhanced DevOps management by modifying the application's lifecycle based on failure patterns.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If manual tracking and record-keeping methods are used to monitor application lifecycle events, then detailed records can be maintained, but the process becomes time-consuming and inefficient for identifying specific events and patterns

Engineering Contradiction:
Improveevent identification accuracyVSAvoidtime to identify events
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent replaces manual mechanical tracking methods with an automated electronic system that uses processors to receive, store, and analyze event data. The system automatically generates visualizations and identifies patterns without human intervention, substituting manual record-keeping with computational automation.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent creates visual representations (copies) of the actual event data through graphical user interface elements such as timeline displays, heat maps, and other visualizations. These visual copies allow users to quickly identify events and patterns without examining raw data directly.

Inventive Principle:
Principle #26Copying

2Reliability

If traditional devops management approaches are used without visualization capabilities, then the system remains simple, but systemic problems and failure patterns remain unnoticed for long periods

Engineering Contradiction:
Improvesystemic problem detectionVSAvoidvisualization system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces visualization components as intermediaries between the raw event data and the users. These visualizations act as a mediating layer that translates complex event data into comprehensible graphical representations, making systemic problems visible without requiring users to directly analyze raw data.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent transforms one-dimensional event data into multi-dimensional visual representations using techniques such as heat maps, timeline displays, and graphical interfaces that show events across multiple dimensions (time, frequency, severity). This dimensional transformation reveals patterns and correlations that are not apparent in raw data.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Productivity

If manual analysis of release records is performed, then detailed examination is possible, but common failure reasons across multiple releases are identified only after prolonged periods

Engineering Contradiction:
Improvefailure pattern identification speedVSAvoidfailure correlation visibility
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent implements feedback mechanisms where the system automatically analyzes event data, identifies patterns and correlations, and provides feedback to users through visualizations and notifications. This continuous feedback loop enables rapid identification of failure patterns across multiple releases by constantly monitoring and analyzing new event data.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent performs preliminary analysis of event data by automatically identifying patterns and correlations before users need to request this information. The system proactively detects potential issues and prepares visualizations in advance, enabling rapid response to failure patterns without requiring manual initiation of analysis.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10127017B2Devops management
Publication Date: 2018.11.13 VMWARE INC
  • US10127017B2 patent drawing
  • US10127017B2 patent drawing
  • US10127017B2 patent drawing

AI summary

The present disclosure is related to devices and methods for devops management. One or more devices can include instructions to receive indications associated with execution events of a release of an application over a period of time, wherein the execution events include positive execution events and negative execution events, and provide a graphical user interface (GUI) configured to display a timeline in a first portion of the GUI corresponding to the release of the application over the period of time, wherein the timeline includes a display element for each of the execution events in a respective portion of the timeline corresponding to an execution time of the execution event, and provide a plurality of selectable options, wherein each option, upon being selected, causes a different section of the timeline to be displayed by a second portion of the GUI.