Graph Query Engine for Topology-Bounded Observability Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Monitoring and logging of web services across distributed systems is challenging due to complex data dependencies and siloed data handling, leading to difficulties in associating logged data and risking software application breakdowns.

Innovation Solution

A graph-based query engine using a Unified Query Language (UQL) for an extensibility platform that allows centralized monitoring and data association, with a declarative language for Metrics, Events, and Logs (MELT) data model, supporting topology-specific queries.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If monitoring is performed in a discrete and non-centralized fashion for each web service, then implementation simplicity is maintained, but data association capability deteriorates and monitoring effectiveness is reduced

Engineering Contradiction:
Improvemonitoring implementation simplicityVSAvoiddata association capability
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent merges discrete monitoring functions into a centralized extensibility platform that collects and associates logged data from multiple web services through a unified graph-based query engine, enabling cross-service data correlation while maintaining implementation simplicity through standardized interfaces

Inventive Principle:
Principle #5Merging (Combining)

2Loss of information

If centralized monitoring is implemented through an extensibility platform, then data association capability is improved, but system complexity increases

Engineering Contradiction:
Improvedata association capabilityVSAvoidmonitoring system complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent segments the centralized monitoring system into modular components: data collection agents, a graph database for storage, and a query engine for analysis. This segmentation allows the system to achieve comprehensive data association while managing complexity through independent, loosely-coupled modules that can be implemented and maintained separately

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a graph-based query engine as an intermediary layer between the extensibility platform and the monitored web services. This intermediary handles the complex tasks of data association and analysis, allowing the platform to achieve centralized monitoring capabilities without directly embedding complex monitoring logic in each service

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If monitoring code is added to web services without accounting for dependencies, then monitoring coverage is improved, but application reliability deteriorates

Engineering Contradiction:
Improvemonitoring coverageVSAvoidapplication stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements preliminary action by establishing a standardized extensibility platform framework before adding monitoring code to web services. This framework pre-defines data collection interfaces, logging formats, and dependency management mechanisms, allowing monitoring to be added systematically without disrupting service dependencies or application stability

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12517907B2Graph-based query engine for an extensibility platform
Publication Date: 2026.01.06 CISCO TECHNOLOGY INC
  • US12517907B2 patent drawing
  • US12517907B2 patent drawing
  • US12517907B2 patent drawing

AI summary

In one embodiment, a method comprises: accessing information from an extensibility platform configured to monitor observability data from a monitored computer network topology; receiving a query regarding the information, the query formatted according to a unified query language for the extensibility platform; determining which specific requested data from the information to return in response to the query based on a fetch block within the query; determining one or more bounding blocks within the query that establish one or more boundaries on the query, wherein one of the one or more bounding blocks comprises a topology boundary block to define a specific topology of the monitored computer network topology, wherein the specific topology identifies one or more entities within the monitored computer network topology to which the query is specifically directed; and returning results of the query as defined by the requested data to return and limited to the specific topology.