Standardized Error Schema for Distributed SRE Observability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current SRE observability tools face challenges in efficiently diagnosing failures across distributed applications due to disparate error coding standards and the lack of centralized logging, leading to time-consuming manual processes that are not scalable for large-scale datacenter operations.

Innovation Solution

Implementing a specification, platform, and cloud-agnostic SRE observability improving module that utilizes standardized error codes and distributed error propagation, allowing for real-time error logging and remediation through a graphical user interface, enabling SRE users to pinpoint failing applications and components, and automatically implementing corrective actions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If each application follows its own error coding standards and reports to its own streams, then application-specific error tracking is maintained, but SRE users require considerable effort and time to understand the flow of user business transaction and correlate errors across applications

Engineering Contradiction:
Improveapplication-specific error trackingVSAvoidtime to correlate errors
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements a universal error code schema that can be applied across multiple different applications and services. This schema provides a common language for error representation that works universally across the distributed system, allowing SRE users to correlate errors without learning application-specific formats. The schema includes standardized fields such as error code, error message, timestamp, and stack trace that can be consistently applied across diverse applications while maintaining their individual error characteristics.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent introduces a centralized logging system that acts as an intermediary between multiple applications and SRE users. This intermediary collects error logs from various applications, standardizes them using the common schema, and presents them in a unified view. The intermediary layer translates application-specific error formats into the universal schema, enabling efficient error correlation without requiring SRE users to understand each application's internal error coding standards.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If SRE users review failures and analyze verbose log messages across multiple failing applications to understand the root failing component, then detailed error information is available, but the process is extremely time consuming and not scalable for large scale datacenter events

Engineering Contradiction:
Improvedetailed error informationVSAvoiddiagnosis speed
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent segments error information into structured, standardized fields within the common schema. Instead of presenting verbose, unstructured log messages, the error data is divided into discrete components such as error code, error message, timestamp, stack trace, and contextual information. This segmentation allows SRE users to quickly scan and understand error details without wading through verbose text, significantly improving diagnosis speed while preserving all necessary error information.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent transforms error information from unstructured verbose log messages into structured parameters with standardized formats. By changing the representation from text-heavy logs to parameterized error objects with consistent fields, the system enables rapid parsing, filtering, and analysis of error data. This parameterization allows for efficient querying and correlation of errors across multiple applications without sacrificing detailed error information.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If SRE users do not have access to all the logs for all applications in a centralized place, then application-specific log security is maintained, but automation and intelligent analysis cannot be effectively implemented

Engineering Contradiction:
Improvecentralized log accessVSAvoidautomation capability
Core Design Contradiction:
Ease of operationVSExtent of automation

Solution Approach 1:

The patent implements a centralized logging system that serves as an intermediary between applications and SRE tools. This intermediary collects, standardizes, and stores error logs from all applications in a centralized location with a uniform schema. The centralized system maintains security through controlled access while enabling full automation capabilities. SRE users and automated tools can query and analyze errors across all applications without each application needing to expose its internal logging mechanisms, thus enabling automation while maintaining security boundaries.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12169434B2System, method, and computer program to improve site reliability engineering observability
Publication Date: 2024.12.17 JPMORGAN CHASE BANK NA
  • US12169434B2 patent drawing
  • US12169434B2 patent drawing
  • US12169434B2 patent drawing

AI summary

Various methods, apparatuses/systems, and media for improving SRE observability are disclosed. A processor defines a schema in a common manner; causes any application included across a distributed set of applications to utilize the schema to describe an error associated with a downstream application such that root failing component associated with the error is always at a bottom error frame in a response; implements a common structure for distributed error propagation in a chain of applications across the distributed set of applications in connection with the error message; generates error logs received from the chain of applications; stores the error logs in a centralized location accessible by all SRE users and application owners; calls a corresponding application programing interface (API) to access the error logs from the centralized location for utilizing in remediation.