Dynamic Microservice Mesh Visualization for Request Type Identification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing microservice mesh visualization systems fail to identify specific types of requests causing performance metric decreases, leading to increased latency and inefficiency as users spend additional time and resources trying to address the issues.
Innovation Solution
A dynamic visualization system that includes operation vertices corresponding to different types of requests received by services in a microservice mesh, allowing users to easily identify and address the operations causing performance issues by providing detailed graphical visualizations and performance data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If traditional microservice mesh visualization systems are used, then users can view overall system topology, but users cannot identify specific request types causing performance metric decreases, leading to increased troubleshooting time and resources
Solution Approach 1:
The patent segments the visualization by introducing operation vertices that represent different types of requests (e.g., read operations, write operations, delete operations) within the microservice mesh topology. This segmentation allows users to distinguish which specific operation types are causing performance metric decreases, transforming the inability to identify specific request types into the ability to precisely pinpoint problematic operations through the graphical interface
Solution Approach 2:
The patent introduces operation vertices as intermediary elements between service vertices and performance metrics. These operation vertices act as mediators that connect specific request types to their corresponding performance impacts, enabling users to trace performance issues back to specific operation types without having to manually analyze raw data or spend excessive time troubleshooting
2Productivity
If detailed request type information is added to visualization, then users can identify performance issues faster, but visualization complexity increases
Solution Approach 1:
The visualization is segmented into distinct vertex types (service vertices, operation vertices, and performance metric vertices) connected by edges representing different relationships. This structured segmentation organizes detailed information in a systematic way that enhances issue identification efficiency while maintaining visual clarity through consistent graphical patterns and relationships
Solution Approach 2:
The patent adds an operational dimension to the traditional service mesh visualization by introducing operation vertices that represent different types of requests. This dimensional expansion allows detailed request type information to be displayed without overwhelming the visualization, as the new dimension organizes information hierarchically and relationships are shown through structured edge connections rather than cluttered details
Data Source
AI summary
A method includes, in response to receiving a request for a graphical visualization of a microservice mesh comprising one or more nodes, obtaining information associated with services operating at the one or more nodes and connections between the one or more nodes. The method further includes determining, in view of the information, one or more types of requests associated with each of the services. The method further includes generating the graphical visualization of the microservice mesh. The graphical visualization includes a first vertex corresponding to a particular service and a second vertex corresponding to a type of a request received by the service. The first vertex and second vertex are connected by an edge that corresponds to the request.