Responding To Trigger Events That Threaten An Operability Of A Cloud Infrastructure
US-2024364579-A1 · Oct 31, 2024 · US
US2020366758A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2020366758-A1 |
| Application number | US-201916415084-A |
| Country | US |
| Kind code | A1 |
| Filing date | May 17, 2019 |
| Priority date | May 17, 2019 |
| Publication date | Nov 19, 2020 |
| 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.
Described embodiments provide systems and methods for displaying a service graph of microservices based at least on a namespace. A device assigns each of a plurality of microservices of one or more services to a ring of criticality of a plurality of rings of criticality. Each ring of criticality may identify a level of importance of a microservice to the one or more services. The device receives a request to display a service graph of the plurality of microservices according to a selected ring of criticality of the plurality of rings of criticality. The device generates the service graph comprising one or more of the microservices within the selected ring of criticality. The device displays the service graph identifying the one or more microservices within the selected ring of criticality.
Opening claim text (preview).
1 . A method for displaying a service graph of microservices based on a ring of criticality, the method comprising: (a) assigning, by a device, each of a plurality of microservices of one or more services to a ring of criticality of a plurality of rings of criticality, wherein each ring of criticality is defined by a subset of the plurality of microservices which have a common level of importance to the one or more services; (b) receiving, by the device, a request to display a service graph of the plurality of microservices according to a selected ring of criticality of the plurality of rings of criticality; (c) generating by the device, the service graph comprising one or more of the microservices within the selected ring of criticality; and (d) displaying, by the device, the service graph identifying the one or more microservices within the selected ring of criticality. 2 . The method of claim 1 , wherein the plurality of rings of criticality comprises rings of increasing levels of importance of the microservice to the one or more services. 3 . The method of claim 1 , wherein (a) further comprises configuring a tag of the microservice to identify the ring of criticality assigned to the microservice. 4 . The method of claim 1 , wherein (a) further comprises selecting, by the device, the ring of criticality for one or more of the microservices based at least on metrics on execution of the plurality of microservices. 5 . The method of claim 1 , wherein (b) further comprises receiving, by the device via a user interface, a selection of the ring of criticality from the plurality of rings of criticality. 6 . The method of claim 1 , further comprising receiving a request to change the selected ring of criticality to a second ring of criticality and displaying the service graph based at least on the second criticality. 7 . The method of claim 1 , wherein (b) further comprises receiving a request to display the service graph to include two or more of the plurality of rings of criticality including the selected ring of criticality. 8 . The method of claim 1 , wherein (c) further comprises generating, by the device, the service graph to include the one or more microservices assigned to the selected ring of criticality and any one or more microservices assigned to a ring of criticality with the level of importance above the level of importance of the selected ring of criticality. 9 . The method of claim 1 , wherein (c) further comprises generating, by the device, the service graph to include the one or more microservices assigned to the selected ring of criticality and any one or more microservices assigned to one or more rings of criticality with the level of importance below the level of importance of the selected ring of criticality. 10 . The method of claim 1 , wherein (d) further comprises displaying the service graph identifying the one or more microservices assigned to the selected ring of criticality and one or more microservices assigned to one or more rings of criticality with the level of importance one of below or above the level of importance of the selected ring of criticality. 11 . A system for displaying a service graph of microservices based at least on a namespace, the system comprising: a device comprising one or more processors, coupled to memory, and configured to: assign each of a plurality of microservices of one or more services to a ring of criticality of a plurality of rings of criticality, wherein each ring of criticality is defined by a subset of the plurality of microservices which have a common level of importance to the one or more services; wherein the device is configured to: receive a request to display a service graph of the plurality of microservices according to a selected ring of criticality of the plurality of rings of criticality; generate the service graph comprising one or more of the microservices within the selected ring of criticality; and display the service graph identifying the one or more microservices within the selected ring of criticality. 12 . The system of claim 11 , wherein the plurality of rings of criticality comprises rings of increasing levels of importance of the microservice to the one or more services. 13 . The system of claim 11 , wherein the device is configured to configure a tag of the microservice to identify the ring of criticality assigned to the microservice. 14 . The system of claim 11 , wherein the device is further configured to select the ring of criticality for one or more of the microservices based at least on metrics on execution of the plurality of microservices. 15 . The system of claim 11 , wherein the device is further configured to receive, via a user interface, a selection of the ring of criticality from the plurality of rings of criticality. 16 . The system of claim 11 , wherein the device is further configured to receive a request to change the selected ring of criticality to a second ring of criticality and displaying the service graph based at least on the second criticality. 17 . The system of claim 11 , wherein the device is further configured to receive a request to display the service graph to include two or more of the plurality of rings of criticality including the selected ring of criticality. 18 . The system of claim 11 , wherein the device is further configured to generate the service graph to include the one or more microservices assigned to the selected ring of criticality and any one or more microservices assigned to a ring of criticality with the level of importance above the level of importance of the selected ring of criticality. 19 . The system of claim 11 , wherein the device is further configured to generate the service graph to include the one or more microservices assigned to the selected ring of criticality and any one or more microservices assigned to one or more rings of criticality with the level of importance below the level of importance of the selected ring of criticality. 20 . The system of claim 11 , wherein the device is further configured to generate the service graph identifying the one or more microservices assigned to the selected ring of criticality and one or more microservices assigned to one or more rings of criticality with the level of importance one of below or above the level of importance of the selected ring of criticality.
for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title
based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title
the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV · CPC title
Discovery or management of network topologies · CPC title
using virtualisation of network functions or resources, e.g. SDN or NFV entities · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.