Microservice Event Tracing Using Correlation IDs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Microservice architectures in prescription drug fill processing systems often involve complex monitoring and lengthy troubleshooting due to non-integrated applications, requiring administrators to know the exact location of each microservice for issue identification.
Innovation Solution
A computer system with structured microservice configuration data and event log data analyzes messages to identify microservices, builds a configuration file, and transforms user interfaces for non-intrusive event tracing, using correlation identifiers and API calls to manage message fields and sensitive data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple microservice applications are used in prescription drug fill processing, then processing capability is improved, but monitoring complexity and troubleshooting difficulty increase
Solution Approach 1:
The patent introduces an event monitoring system as an intermediary component that sits between microservice applications and administrators. This system automatically collects, correlates, and tracks events across multiple microservices through correlation identifiers, eliminating the need for administrators to directly monitor each microservice individually and reducing troubleshooting complexity while maintaining high processing capability.
Solution Approach 2:
The system enables self-service monitoring where the microservice applications automatically generate and transmit their own event logs to the monitoring system. The correlation identifier mechanism allows the system to automatically trace and correlate events across different microservices without requiring manual intervention or complex administrator involvement in the monitoring process.
2Measurement precision
If administrators manually track microservice location, then troubleshooting precision is improved, but time consumption increases
Solution Approach 1:
The patent implements a feedback mechanism where the event monitoring system continuously collects event data from microservices and automatically correlates it using correlation identifiers. When an issue occurs, the system provides real-time feedback by tracing the event history and current location of requests across microservices, enabling administrators to quickly identify problems without manual tracking while maintaining precise location identification.
Solution Approach 2:
The system performs preliminary action by pre-establishing correlation identifiers and event tracking mechanisms before issues occur. Event logs are continuously collected and correlated in advance, so when a problem arises, the trajectory and location of requests are already mapped out, eliminating the need for administrators to manually trace issues while maintaining precise identification.
3Loss of information
If event data is collected from all microservices, then system visibility is improved, but data management complexity increases
Solution Approach 1:
The patent segments event data management by organizing collected event logs into distinct request data structures grouped by correlation identifiers. Each correlation identifier represents a specific request trajectory, and events are segmented and stored according to their associated microservices and request contexts. This segmentation maintains comprehensive system visibility while organizing data in a manageable, structured manner that reduces complexity.
Data Source
AI summary
A computer system includes memory hardware configured to store structured microservice configuration data having multiple microservice entries each associated with one of multiple microservice applications of a request processing architecture. The system includes processor hardware configured to access structured microservice configuration data to identify the microservice applications of the request processing architecture, subscribing to messages transmitted by the identified microservice applications for event monitoring, and receiving multiple messages transmitted by the identified microservice applications. For each of the multiple received messages, the instructions include analyzing one or more fields of the received message to determine a correlation identifier associated with the received message, identifying one of the multiple request data structures, storing an event message entry in the identified request data structure, and transforming a user interface of a user device to display at least a portion of the multiple event message entries.