System, method, and computer program for a microservice lifecycle operator
US-2021365272-A1 · Nov 25, 2021 · US
US2023246919A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2023246919-A1 |
| Application number | US-202118011928-A |
| Country | US |
| Kind code | A1 |
| Filing date | Jun 29, 2021 |
| Priority date | Aug 28, 2020 |
| Publication date | Aug 3, 2023 |
| 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.
The present disclosure discloses a method and system for locating a micro-service fusing anomaly, a device and a medium. The method includes: creating a micro-service application including a plurality of components, and determining whether a component configured with a fusing protection strategy is present in the micro-service application; in response to the presence of the component configured with the fusing protection strategy in the micro-service application, monitoring the component configured with the fusing protection strategy, and collecting data of all nodes under the component; in response to detecting the presence of a node which triggers fusing, in the component, screening out data within a preset time period; and matching a preset anomaly keyword according to the data within the preset time period, and associating the anomaly keyword with the node, so as to locate an anomaly.
Opening claim text (preview).
1 . A method for locating a micro-service fusing anomaly, comprising the following steps: creating a micro-service application comprising a plurality of components, and determining whether a component configured with a fusing protection strategy is present in the micro-service application; in response to the presence of the component configured with the fusing protection strategy in the micro-service application, monitoring the component configured with the fusing protection strategy, and collecting data of all nodes under the component configured with the fusing protection strategy; in response to detecting the presence of a node which triggers fusing, in the component configured with the fusing protection strategy, screening out data within a preset time period; and matching a preset anomaly keyword according to the data within the preset time period, and associating the anomaly keyword with the node, so as to locate an anomaly. 2 . The method according to claim 1 , wherein the step of screening out data within the preset time period comprises: determining a fusing moment, and screening out log information and operation monitoring data within a first time before and after the fusing moment. 3 . The method according to claim 2 , further comprising: acquiring a network condition at the fusing moment according to the operation monitoring data, and adjusting the preset time period on the basis of the network condition. 4 . The method according to claim 1 , further comprising: in response to simultaneous fusing of the plurality of components, determining whether keywords corresponding to the plurality of components are completely consistent. 5 . The method according to claim 4 , further comprising: in response to the keywords corresponding to the plurality of components being completely consistent, restarting the micro-service application. 6 . The method according to claim 1 , wherein the step of determining whether the component configured with the fusing protection strategy is present in the micro-service application comprises: determining whether a component configured with a forwarding strategy is present in the micro-service application; and in response to the presence of the component configured with the forwarding strategy in the micro-service application, determining whether the forwarding strategy is associated with the fusing protection strategy. 7 . The method according to claim 1 , wherein the step of monitoring the component, and collecting data of all nodes under the component comprises: determining, according to component information of the component configured with the fusing protection strategy, all nodes corresponding to the component configured with the fusing protection strategy, and collecting log information and operation monitoring data of all nodes. 8 . (canceled) 9 . A computer device, comprising: at least one processor; and a memory, wherein the memory stores a computer instruction that is executable on the processor, and when executed by the processor, the instruction causes the processor to; create a micro-service application comprising a plurality of components, and determine whether a component configured with a fusing protection strategy is present in the micro-service application; in response to the presence of the component configured with the fusing protection strategy in the micro-service application, monitor the component configured with the fusing protection strategy, and collect data of all nodes under the component configured with the fusing protection strategy; in response to detecting the presence of a node which triggers fusing, in the component configured with the fusing protection strategy, screen out data within a preset time period; and match a preset anomaly keyword according to the data within the preset time period, and associating the anomaly keyword with the node, so as to locate an anomaly. 10 . A non-transitory computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when executed by a processor, the computer program cause the processor to: create a micro-service application comprising a plurality of components, and determine whether a component configured with a fusing protection strategy is present in the micro-service application; in response to the presence of the component configured with the fusing protection strategy in the micro-service application, monitor the component configured with the fusing protection strategy, and collect data of all nodes under the component configured with the fusing protection strategy; in response to detecting the presence of a node which triggers fusing, in the component configured with the fusing protection strategy, screen out data within a preset time period; and match a preset anomaly keyword according to the data within the preset time period, and associating the anomaly keyword with the node, so as to locate an anomaly. 11 . The method according to claim 1 , wherein the micro-service application is created on a cloud management platform to provide cloud computing service management. 12 . The method according to claim 11 , wherein the cloud management platform is a cloud computing platform based on kubernetes service orchestration technology, and the kubernetes service orchestration technology is used for managing containerization applications on a plurality of hosts in the cloud platform. 13 . The method according to claim 11 , wherein the micro-service application comprises a plurality of components, each component comprises a plurality of nodes. 14 . The method according to claim 12 , further comprising: creating a Destination Rule rule resource for a component at a kubernetes bottom layer; recording, by the Destination Rule, a fusing trigger rule, after the fusing protection strategy is configured for a certain component. 15 . The method according to claim 14 , wherein the fusing trigger rule comprises an error occurs in a certain node of the component for preset consecutive times, the error comprises: a 5xx type Hyper Text Transfer Protocol, hyper text transfer protocol response error, Transmission Control Protocol, transmission control protocol connection timeout or failure, and user-defined program anomaly feedback. 16 . The method according to claim 14 , wherein the step of in response to the presence of the component configured with the fusing protection strategy in the micro-service application, monitoring the component configured with the fusing protection strategy, and collecting data of all nodes under the component comprises: in respond to monitoring that the Destination Rule has enabled a fusing configuration, sending, by a monitoring apparatus, a collection request to a data collection apparatus; seeking, by the data collection apparatus, all corresponding service nodes according to component information, and collecting standard control console data of each node, after receiving the collection request. 17 . The method according to claim 1 , wherein the step of in response to detecting the presence of a node which triggers fusing, in the component configured with the fusing protection strategy, screening out data within a preset time period comprises: in response to detecting the component of the micro-service application is abnormal, and fusing is triggered, sending, by the monitoring apparatus, a data filtering request to a anomaly analysis apparatus, which screens out the data within the preset time period after receiving the data filtering request.
Discovery or management of network topologies · CPC title
Discovery or management thereof, e.g. service location protocol [SLP] or web services · CPC title
using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis · CPC title
involving time analysis · CPC title
Localisation of faults · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.