Tracking data throughout an asset lifecycle
US-12166894-B2 · Dec 10, 2024 · US
US2016149786A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016149786-A1 |
| Application number | US-201615004113-A |
| Country | US |
| Kind code | A1 |
| Filing date | Jan 22, 2016 |
| Priority date | Jun 29, 2010 |
| Publication date | May 26, 2016 |
| 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 is a server monitoring technology that is scalable to large numbers of servers, e.g., in a datacenter. Agents on servers run queries to monitor data sources for that server, such as performance counters and other events. The agents monitor their resource usage and those of monitored events to stay within an administrator-specified resource budget (policy), e.g., by modifying the running queries and/or monitoring parameters. A controller receives results of the monitoring, analyzes the results, and takes action as needed with respect to server operation and monitoring. The controller may dynamically update an agent's queries, monitoring parameters and/or monitored data post-processing operations. The controller may issue alerts and reports, including alerts indicative of inter-server problems between two or more servers.
Opening claim text (preview).
1 .- 20 . (canceled) 21 . In a computing environment, a system comprising: a computing machine; a dynamic query engine, implemented on the computing machine, operating to monitor its own resource consumption as it monitors the computing machine using one or more queries and collects monitoring data from one or more data sources via one or more input adapters. 22 . The system of claim 21 , wherein the collected monitoring data from the one or more data sources includes at least one of event data, trace data, log data, performance data, provider data, instrumentation data, network data, or network traffic data. 23 . The system of claim 21 , wherein the dynamic query engine uses output of one query as input of another query to collect the monitoring data. 24 . The system of claim 21 , wherein the dynamic query engine receives the monitoring data from the one or more data sources as directed by the one or more queries running inside the dynamic query engine. 25 . The system of claim 21 , wherein the one or more data sources include at least one of tracing channels, network packet traces, event logs, provider events, instrumentation events, a network sniffer, or a performance counter. 26 . The system of claim 21 , wherein the dynamic query engine further comprises: a scheduler that monitors resource usage of the dynamic query engine with respect to a resource budget and dynamically modifies at least one of the one or more queries based on the resource usage of the dynamic query engine in order to remain within the policy-specified resource budget as the dynamic query engine continues to collect the monitoring data. 27 . The system of claim 26 , wherein dynamically modifying at least one query dynamically modifies the use of the one or more data sources by the dynamic query engine to collect the monitoring data. 28 . The system of claim 27 , wherein dynamically modifying the use of the one or more data sources includes at least one of modifying a rate at which the monitoring data is pulled from a data source, modifying one or more calculations performed on the monitoring data, modifying a method for saving or transferring the monitoring data, modifying a number of data sources used, or modifying a type of data source used by the dynamic query engine. 29 . The system of claim 21 , wherein the dynamic query engine receives one or more new queries or one or more new monitoring parameters, or both, from a controller that obtains and analyzes the collected monitoring data, and in response, changes one or more of the data sources, one or more of the queries being run, one or more of the monitoring parameters, or one or more post-processing operations on the data, or any combination of one or more of the data sources, one or more of the queries being run, one or more of the monitoring parameters, or one or more post-processing operations on the data. 30 . The system of claim 21 , wherein the dynamic query engine further operates to estimate a resource requirement of creating an event corresponding to the one or more queries and includes the estimate in monitoring its own resource consumption relative to the one or more queries. 31 . In a computing environment, a system comprising: one or more servers; one or more agents implemented on the one or more servers, an individual agent operating to: collect data via one or more data sources of a server using one or more queries related to monitoring the server on which the individual agent is implemented; monitor resource usage of the individual agent during the data collection; enforce a resource consumption budget relative to the individual agent during the data collection; and process the collected data into monitoring results for the server on which the individual agent is implemented. 32 . The system of claim 31 , wherein the one or more data sources include at least one of tracing channels, network packet traces, event logs, provider events, instrumentation events, a network sniffer, or a performance counter. 33 . The system of claim 31 , further comprising: an aggregation agent implemented on another server other than the one or more servers, the aggregation agent operating to: receive the monitoring results from the one or more agents; and aggregate the received monitoring results for analysis by a controller. 34 . The system of claim 33 , wherein the controller receives monitoring results associated with the server from the agent implemented on that server, analyzes the monitoring results associated with that server, and uses the analysis associated with that server to configure another server running a similar or same application as that server, or having similar or the same machine configuration parameters, or both to configure the other server running the similar or same application as that server and having the similar or the same machine configuration parameters. 35 . The system of claim 31 , wherein the one or more agents receive the data from the one or more data sources as directed by the one or more queries running inside the one or more agents. 36 . The system of claim 31 , wherein the individual agent of the one or more agents further comprises: a scheduler that monitors the resource usage of the individual agent with respect to a resource budget and dynamically modifies at least one of the one or more queries based on the resource usage of the individual agent in order to remain within the policy-specified resource budget as the individual agent continues to collect the data related to monitoring the server on which the individual agent is implemented. 37 . In a computing environment, a method performed on at least one processor comprising: running, by a dynamic query engine, one or more queries on a server to collect monitoring data from one or more data sources associated with the server, the monitoring data including at least one of event data, trace data, log data, performance data, provider data, instrumentation data, network data, or network traffic data; and monitoring resource usage of the dynamic query engine with respect to a policy-specified resource budget during the monitoring data collection. 38 . The method of claim 37 , further comprising: modifying at least one of the one or more queries during the monitoring data collection based on the monitored resource usage of the dynamic query engine in order to remain within the policy-specified resource budget as the dynamic query engine continues to collect the monitoring data from the one or more data sources. 39 . The method of claim 37 , further comprising: logging at least some of the collected monitoring data from at least one data source for later processing as more resources become available. 40 . The method of claim 37 , wherein at least one of the one or more queries is directed to detect an anomaly and, in response to detecting the anomaly, obtain data related to logs corresponding to a time period relative to the detection of the anomaly.
where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50) · CPC title
Network utilisation, e.g. volume of load or congestion level · CPC title
Physics · mapped topic
where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting · CPC title
for systems · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.