Micro-firewalls in a microservice mesh environment
US-11323418-B2 · May 3, 2022 · US
US2024330152A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2024330152-A1 |
| Application number | US-202318128395-A |
| Country | US |
| Kind code | A1 |
| Filing date | Mar 30, 2023 |
| Priority date | Mar 30, 2023 |
| Publication date | Oct 3, 2024 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method, system, and computer program product are configured to: create a link tracing data structure in response to receiving a request from a user interface (UI), wherein the link tracing data structure includes a synchronization identifier and information about user actions in the UI; handle the request by calling plural microservices; add respective synchronization content for each one of the plural microservices to the link tracing data structure, wherein the respective synchronization content for a respective one of the plural microservices comprises: the synchronization identifier; a respective step identifier that identifies the respective one of the plural microservices; and a respective synchronization message that describes an execution status of the respective one of the plural microservices; store the link tracing data structure; and provide the link tracing data structure to a requesting user.
Opening claim text (preview).
1 . A method, comprising: creating, by a processor set, a link tracing data structure in response to receiving a request from a user interface (UI), wherein the link tracing data structure includes a synchronization identifier and information about user actions in the UI; handling, by the processor set, the request by calling plural microservices; adding, by the processor set, respective synchronization content for each one of the plural microservices to the link tracing data structure, wherein the respective synchronization content for a respective one of the plural microservices comprises: the synchronization identifier; a respective step identifier that identifies the respective one of the plural microservices; and a respective synchronization message that describes an execution status of the respective one of the plural microservices; storing, by the processor set, the link tracing data structure; and providing, by the processor set, the link tracing data structure to a requesting user. 2 . The method of claim 1 , wherein the link tracing data structure that is transmitted to the user device includes the synchronization identifier, the information about the user actions in the UI, and the respective synchronization content for each one of the plural microservices. 3 . The method of claim 1 , wherein the information about the user actions in the UI comprises request event information and request path information generated by a web client associated with the UI. 4 . The method of claim 1 , wherein, in the respective synchronization content for a respective one of the plural microservices, the synchronization content message indicates that the respective one of the plural microservices executed successfully or failed to execute. 5 . The method of claim 1 , further comprising creating the respective step identifier in the respective synchronization content for a respective one of the plural microservices, wherein the respective step identifier is based on a server IP address, a generation time of the step identifier, an increment sequence, and a process number. 6 . The method of claim 1 , further comprising creating the synchronization identifier based on a request identifier of the request and a generation time of the synchronization identifier. 7 . The method of claim 1 , wherein the respective synchronization content for a respective one of the plural microservices includes a data field that identifies a parent of the respective one of the plural microservices. 8 . The method of claim 1 , wherein, in the respective synchronization content for a respective one of the plural microservices, a main container of the respective one of the plural microservices creates the respective synchronization message, and an agent of the respective one of the plural microservices creates the respective step identifier. 9 . The method of claim 8 , wherein the agent comprises a sidecar in a same pod as the main container. 10 . The method of claim 1 , wherein a management module in a control plane of the computing cluster creates the link tracing data structure, creates the synchronization identifier, and adds the respective synchronization content for each one of the plural microservices to the link tracing data structure. 11 . A computer program product comprising one or more computer readable storage media having program instructions collectively stored on the one or more computer readable storage media, the program instructions executable to: create a link tracing data structure in response to receiving a request from a user interface (UI), wherein the link tracing data structure includes a synchronization identifier and information about user actions in the UI; handle the request by calling plural microservices; add respective synchronization content for each one of the plural microservices to the link tracing data structure, wherein the respective synchronization content for a respective one of the plural microservices comprises: the synchronization identifier; a respective step identifier that identifies the respective one of the plural microservices; and a respective synchronization message that describes an execution status of the respective one of the plural microservices; store the link tracing data structure; and provide the link tracing data structure to a requesting user. 12 . The computer program product of claim 11 , wherein the link tracing data structure that is transmitted to the user device includes the synchronization identifier, the information about the user actions in the UI, and the respective synchronization content for each one of the plural microservices. 13 . The computer program product of claim 11 , wherein the information about the user actions in the UI comprises request event information and request path information generated by a web client associated with the UI. 14 . The computer program product of claim 11 , wherein, in the respective synchronization content for a respective one of the plural microservices, the synchronization content message indicates that the respective one of the plural microservices executed successfully or failed to execute. 15 . The computer program product of claim 11 , wherein the program instructions are executable to create the respective step identifier in the respective synchronization content for a respective one of the plural microservices, wherein the respective step identifier is based on a server IP address, a generation time of the step identifier, an increment sequence, and a process number. 16 . A system comprising: a processor set, one or more computer readable storage media, and program instructions collectively stored on the one or more computer readable storage media, the program instructions executable to: create a link tracing data structure in response to receiving a request from a user interface (UI), wherein the link tracing data structure includes a synchronization identifier and information about user actions in the UI; handle the request by calling plural microservices; add respective synchronization content for each one of the plural microservices to the link tracing data structure, wherein the respective synchronization content for a respective one of the plural microservices comprises: the synchronization identifier; a respective step identifier that identifies the respective one of the plural microservices; and a respective synchronization message that describes an execution status of the respective one of the plural microservices; store the link tracing data structure; and provide the link tracing data structure to a requesting user. 17 . The system of claim 16 , wherein the program instructions are executable to create the synchronization identifier based on a request identifier of the request and a generation time of the synchronization identifier. 18 . The system of claim 16 , wherein the respective synchronization content for a respective one of the plural microservices includes a data field that identifies a parent of the respective one of the plural microservices. 19 . The system of claim 16 , wherein, in the respective synchronization content for a respective one of the plural microservices, a main container of the respective one of the plural microservices creates the respective synchronization message, and an agent of the respective one of the plural microservices creates the respective step identifier. 20 . The system of claim 16 , wherein a management module in a control plane of the computing cluster cr
where the computing system component is a software system · CPC title
for systems · CPC title
Visualisation of programs or trace data · CPC title
Data logging (G06F11/14, G06F11/2205 take precedence) · CPC title
Performance evaluation by tracing or monitoring · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.