Error incident fingerprinting with unique static identifiers
AssigneeSap SE
InventorRobert Gaida
Life of this patent
Estimating the term…
Abstract
A wide variety of software support functionality can be improved via error incident fingerprinting with unique static identifiers. Such unique identifiers can originate within an integrated development environment and be propagated to runtime, where they can be harvested from execution context at the time of an error. The fingerprint created from such a unique identifier can then be used for a variety of purposes, including indexing knowledge base records, criticality detection, service innovation, alerting, incident resolution, impacts to the development process, and machine learning.
Claims20
A computer-implemented method comprising:
- upon encountering an error during runtime of an application, collecting an error context of the error, wherein the error context comprises a unique static identifier automatically generated at development time of the application responsive to a developer command to create a new application component, and the unique static identifier identifies an application component definition of an application component in which the error occurred;
- based at least on the unique static identifier, generating an error incident fingerprint of the error;
- generating an error incident record comprising the error incident fingerprint of the error;
- finding a match between the generated error incident record and one or more other error incident records based on the error incident fingerprint generated from the unique static identifier;
- and
- storing an association between the generated error incident record and the one or more matching other error incident records.
A system comprising:
- one or more processors;
- memory coupled to the one or more processors comprising instructions causing the one or more processors to perform the following when executed:
- upon encountering an error during runtime of an application, collecting contextual information of the error, wherein the error contextual information comprises a unique static identifier generated at development time of the application, and the unique static identifier identifies a component location in which the error occurred, the component location comprising a given executable process and a given executable task;
- wherein the unique static identifier comprises:
- a first unique identifier of the given executable process out of a plurality of executable processes and;
- a second unique identifier of the given executable task out of a plurality of executable tasks, wherein the first and second unique identifiers are scraped from an error report of a user interface;
- based at least on the unique static identifier, generating a fingerprint of the error;
- generating an error incident record comprising the fingerprint of the error;
- and
- generating an alert based on the error incident record.
One or more computer-readable media having encoded thereon computer-executable instructions causing one or more processors to perform a method comprising:
- at development time of an application comprising a plurality of executable processes that comprise a collection of a plurality of executable tasks, generating a unique identifier of a given executable process out of the executable processes and generating a unique identifier of a given executable task out of the executable tasks, wherein the given executable task is a member of the collection of the given executable process;
- upon encountering an error during runtime of the application while executing the given executable task of the given executable process, retrieving the unique identifier of the given executable task and the unique identifier of the given executable process from an execution context of the application;
- combining the unique identifier of the given executable task and the unique identifier of the given executable process into a fingerprint of the error;
- based on the fingerprint of the error, locating a document in a knowledge base that describes a solution of the error;
- and
- outputting the document in the knowledge base that describes the solution of the error.
Dependencies are inferred from the claim text.