Network health checker
US-2018123903-A1 · May 3, 2018 · US
US11188445B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11188445-B2 |
| Application number | US-201816008938-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 14, 2018 |
| Priority date | Aug 18, 2017 |
| Publication date | Nov 30, 2021 |
| Grant date | Nov 30, 2021 |
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.
In a computer-implemented method for generating a temporal topology graph of a computing environment, managed component relationship data is received for a plurality of managed components of a computing environment, the managed component relationship data including parent/child information for a managed component of the plurality of managed components at a moment in time. The managed component relationship data is transformed into graphical data of a temporal topology graph of the computing environment, wherein the temporal topology graph includes the moment in time for each instance of the managed component relationship data within the temporal topology graph. The temporal topology graph including the managed component relationship data is generated based at least in part on the graphical data. The temporal topology graph for the computing environment is maintained at a service provider.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method for generating a temporal topology graph of a computing environment on a graphical user interface (GUI), the method comprising: generating, at a plurality of managed components of the computing environment, managed component relationship data for the plurality of managed components, the managed component relationship data comprising parent/child information for a managed component of the plurality of managed components and temporal information at a moment in time, wherein the managed component relationship data is generated at each managed component of the plurality of managed components; capturing, at a collector virtual appliance of the computing environment, operational data communicated over the computing environment, the operational data comprising the managed component relationship data and other data; filtering, at the collector virtual appliance of the computing environment, the managed component relationship data from the operational data, wherein the filtering is performed according to a manifest; receiving, at a service provider, the managed component relationship data for the plurality of managed components of the computing environment; transforming, by the service provider, the managed component relationship data into graphical data of a temporal topology graph of the computing environment, the graphical data comprising nodes and edges, wherein the nodes comprise information identifying the plurality of managed components and the edges comprises relationship information between the plurality of managed components; generating, by the service provider, the temporal topology graph on the GUI, the temporal topology graph comprising the managed component relationship data based at least in part on the graphical data, wherein the temporal topology graph comprises the moment in time for each instance of the managed component relationship data within the temporal topology graph; maintaining, by the service provider, the temporal topology graph for the computing environment; and receiving a user interaction, at the service provider, with the temporal topology graph via the GUI to incrementally step through the temporal topology graph to view instances of the managed component relationship data at one or more moments in time. 2. The computer-implemented method of claim 1 , wherein the computing environment is a datacenter and the plurality of managed components comprises hardware components and virtual components of the datacenter. 3. The computer-implemented method of claim 1 , wherein the manifest is extensible and configurable by the service provider. 4. The computer-implemented method of claim 1 , further comprising: receiving an update to the manifest, wherein the update comprises a change in the managed component relationship data to be collected at the collector virtual appliance of the computing environment. 5. The computer-implemented method of claim 1 , further comprising: communicating an update of the manifest to the collector virtual appliance. 6. The computer-implemented method of claim 5 , further comprising: receiving a request from the collector virtual appliance for any available updates to the manifest. 7. The computer-implemented method of claim 1 , wherein an instance of the managed component relationship data is generated at the computing environment responsive to a change in topology of the plurality of managed components of the computing environment. 8. The computer-implemented method of claim 1 , further comprising: receiving event data for the plurality of managed components of the computing environment. 9. A non-transitory computer readable storage medium having computer readable program code stored thereon for causing a computer system to perform a method for generating a temporal topology graph of a computing environment on a graphical user interface (GUI), the method comprising: generating, at a plurality of managed components of the computing environment, managed component relationship data for the plurality of managed components, the managed component relationship data comprising parent/child information for a managed component of the plurality of managed components and temporal information at a moment in time, wherein an instance of the managed component relationship data is generated at the computing environment responsive to a change in topology of the plurality of managed components of the computing environment, wherein the managed component relationship data is generated at each managed component of the plurality of managed components; capturing operational data communicated over the computing environment, the operational data comprising the managed component relationship data and other data; filtering the managed component relationship data from the operational data, wherein the filtering is performed according to a manifest; receiving the managed component relationship data for the plurality of managed components of the computing environment at a service provider of the computing environment; transforming the managed component relationship data into graphical data of a temporal topology graph of the computing environment, the graphical data comprising nodes and edges, wherein the nodes comprise information identifying the plurality of managed components and the edges comprises relationship information between the plurality of managed components; generating the temporal topology graph on the GUI, the temporal topology graph comprising the managed component relationship data based at least in part on the graphical data, wherein the temporal topology graph comprises the moment in time for each instance of the managed component relationship data within the temporal topology graph; maintaining the temporal topology graph for the computing environment at the service provider; and receiving a user interaction with the temporal topology graph via the GUI to incrementally step through the temporal topology graph to view instances of the managed component relationship data at one or more moments in time. 10. The non-transitory computer readable storage medium of claim 9 , wherein the computing environment is a datacenter and the plurality of managed components comprises hardware components and virtual components of the datacenter. 11. The non-transitory computer readable storage medium of claim 9 , wherein the manifest is extensible and configurable by the service provider. 12. The non-transitory computer readable storage medium of claim 9 , the method further comprising: receiving an update to the manifest, wherein the update comprises a change in the managed component relationship data to be collected at a collector virtual appliance of the computing environment. 13. The non-transitory computer readable storage medium of claim 9 , the method further comprising: communicating an update of the manifest to a collector virtual appliance of the computing environment. 14. The non-transitory computer readable storage medium of claim 13 , the method further comprising: receiving a request from the collector virtual appliance for any available updates to the manifest. 15. The non-transitory computer readable storage medium of claim 9 , the method further comprising: receiving event data for the plurality of managed components of the computing environment. 16. A system for manifest-driven data collection in a computing environment, the system comprising: a data storage unit; and a processor communicatively coupled with the data storage unit, the processor configured to: generate event data a
for systems · CPC title
using virtualisation of network functions or resources, e.g. SDN or NFV entities · CPC title
Entity relationship models · CPC title
Configuration details thereof, e.g. installation, enabling, spatial arrangement of the probes · CPC title
Network integration; Enabling network access in virtual machine instances · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.