Error list and bug report analysis for configuring an application tracer
US-2016266998-A1 · Sep 15, 2016 · US
US9772927B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9772927-B2 |
| Application number | US-201415036325-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 27, 2014 |
| Priority date | Nov 13, 2013 |
| Publication date | Sep 26, 2017 |
| Grant date | Sep 26, 2017 |
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 tracing system may define an origin for consolidating and comparing trace paths within a traced application. A tracer may define an identifier that may be passed through a tracing route, and the identifier may be defined to capture specific instances or groups of instances of traces. The traces may be consolidated into a graphical representation of the program flow. The identifier may be passed across various boundaries, including function boundaries, library boundaries, application boundaries, device boundaries. An analysis system may consolidate or aggregate trace results having the same identifier, and may render such data graphically or provide statistics using the identified datasets.
Opening claim text (preview).
What is claimed is: 1. A method performed on at least one processor, said method comprising: receiving trace data of an application, said application comprising a plurality of components; analyzing said trace data of said application to generate a first topology graph of said application, said first topology graph of said application comprising representations of said plurality of components; displaying said first topology graph of said application in an interactive user interface; receiving a first selection from a user input device, said first selection comprising a first component within said first topology graph of said application; receiving a second selection from said user input device, said second selection comprising a first condition for tracing execution paths passing through said first component within said first topology graph of said application; and creating a tracer rule associated with said first component within said first topology graph of said application to store said first condition for tracing said execution paths passing through said first component within said first topology graph of said application. 2. The method of claim 1 , said first topology graph of said application being generated from trace data gathered by monitoring said application and identifying said plurality of components within said trace data. 3. The method of claim 2 further comprising: displaying a second topology graph of said application in said interactive user interface, said second topology graph comprising trace data organized at least in part by said tracer rule. 4. The method of claim 3 , said tracer rule being consumed by a tracer to classify at least one execution path of said application. 5. The method of claim 4 , said tracer rule being consumed by a tracer to classify execution paths into a plurality of classifications. 6. The method of claim 1 further comprising: presenting a user selection interface comprising a plurality of classification suggestions, said second selection from said user input device being selected from said plurality of classification suggestions. 7. The method of claim 6 further comprising: analyzing tracer data for said application to determine a plurality of input values for said first component within said first topology graph of said application; and presenting at least a subset of said plurality of input values as said plurality of classification suggestions. 8. The method of claim 6 further comprising: analyzing tracer data for said application to determine a plurality of execution paths organized by frequency of use; and presenting at least a subset of said plurality of execution paths as said plurality of classification suggestions. 9. The method of claim 6 further comprising: analyzing tracer data for said application to determine a plurality of execution paths organized by errors detected; and presenting at least a subset of said plurality of execution paths as said plurality of classification suggestions. 10. The method of claim 6 further comprising: analyzing tracer data for said application to determine a plurality of execution paths organized by a performance metric; and presenting at least a subset of said plurality of execution paths as said plurality of classification suggestions. 11. A system comprising: at least one processor; a trace database comprising trace data gathered from tracing an application; an analysis engine that: receives trace data of said application, said application comprising a plurality of components; and analyzes said trace data of said application to generate a first topology graph of said application, said first topology graph of said application comprising representations of said plurality of components; and an interactive user interface presented on a device comprising said at least one processor, said interactive user interface that: displays said first topology graph of said application; receives a first selection from a user input device, said first selection comprising a first component within said first topology graph of said application; receives a second selection from said user input device, said second selection comprising a first condition for tracing execution paths passing through said first component within said first topology graph of said application; and creates a tracer rule associated with said first component within said first topology graph of said application to store said first condition for tracing said execution paths passing through said first component within said first topology graph of said application. 12. The system of claim 11 , said interactive user interface that further: presents a user selection interface comprising a plurality of classification suggestions, said second selection from said user input device being selected from said plurality of classification suggestions. 13. The system of claim 12 , said analysis engine that further: analyzes tracer data for said application to determine a plurality of input values for said first component within said first topology graph of said application; said interactive user interface that further: presents at least a subset of said plurality of input values as said plurality of classification suggestions. 14. The system of claim 13 , said analysis engine that further determines said plurality of input values from a plurality of execution paths classified by frequency of use. 15. The system of claim 13 , said analysis engine that further determines said plurality of input values from a plurality of execution paths classified by errors detected. 16. The system of claim 13 , said analysis engine that further determines said plurality of input values from a plurality of execution paths classified by a performance metric.
Drawing of charts or graphs · CPC title
Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36) · CPC title
Data logging (G06F11/14, G06F11/2205 take precedence) · CPC title
for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range · CPC title
Digital computing or data processing equipment or methods, specially adapted for specific functions (information retrieval, database structures or file system structures therefor G06F16/00) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.