Microservice Notification Standardization via Code-Based Schema
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing notification monitoring tools are inadequate in handling the volume, complexity, and diversity of notifications generated by software applications, particularly microservices, which leads to difficulties in tracking and addressing issues due to varying formats and high volumes of notifications, making it challenging for Site Reliability Engineering (SRE) teams to identify critical alerts amidst less important ones.
Innovation Solution
Standardizing notification formats across microservices and centralizing their management by defining a format that includes code indicating the microservice's identity, version, and execution issues, allowing for translation and comparison of notifications to generate summarized alerts that can be transmitted to monitoring tools.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple software applications are used to monitor notifications from different microservices, then the ability to handle diverse notification formats is improved, but the complexity of the monitoring system increases
Solution Approach 1:
The patent implements a universal notification processing system that can handle multiple notification formats through a single standardized interface. The system defines a common notification schema that all microservices adhere to, allowing one monitoring system to universally process notifications from diverse sources without requiring separate tools for each format.
Solution Approach 2:
The patent introduces a notification service as an intermediary layer between microservices and monitoring tools. This mediator receives notifications in various formats, standardizes them according to a defined schema, and then forwards them to monitoring systems, thereby decoupling the complexity of format handling from the monitoring tools themselves.
2Quantity of substance
If the volume of notifications from microservices increases, then the monitoring capability is improved, but the difficulty of identifying critical alerts increases
Solution Approach 1:
The patent applies local quality by assigning different priorities and classifications to different types of notifications based on their criticality. Critical alerts are marked with higher priority levels and distinct identifiers, allowing monitoring systems to differentiate and focus attention on important notifications amidst the volume of less critical ones.
Solution Approach 2:
The patent uses visual differentiation through color-coding and status indicators to represent different notification priorities and types. Critical alerts are highlighted with distinctive colors and markings, making them easily distinguishable from routine notifications in the monitoring interface, thereby reducing the difficulty of identification.
3Adaptability or versatility
If new microservices are deployed with different notification formats, then the versatility of the system is improved, but the consistency of the monitoring workflow is worsened
Solution Approach 1:
The patent implements preliminary action by establishing a standardized notification schema and format definitions before new microservices are deployed. The notification service is pre-configured with the ability to parse and standardize notifications according to the defined schema, ensuring that new microservices with different formats will be automatically handled consistently without disrupting the monitoring workflow.
Data Source
AI summary
Methods and systems for managing notifications relating to execution of microservices are described herein. A format of notifications relating to execution of a plurality of microservices may be defined. The format may provide that all notifications generated based on the format comprise code. The code may indicate, for example, an identity of one of a plurality of microservices, a version of the code, an occurrence of an issue in execution of the one of the plurality of microservices, and/or one or more scripts which may be executed to address an issue of the notification. Two or more notifications may be received, and the one or more notifications may be formatted based on the defined format. A third notification may be generated based on a comparison of the two or more notifications. The third notification may be transmitted to a computing device.