Pre-formed instructions for a mobile cloud service
US-2017279928-A1 · Sep 28, 2017 · US
US11023306B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11023306-B2 |
| Application number | US-201916458851-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 1, 2019 |
| Priority date | Jul 31, 2017 |
| Publication date | Jun 1, 2021 |
| Grant date | Jun 1, 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.
User-to-software-application-instance-pairings are created. Each of the pairings is a unique relationship between one of the users and one of the instances of the software applications. Identifiers for the user-to-software-application-instance-pairings are received. There is a separate identifier for each of the user-to-software-application-instance-pairings. One of the log creation facilities is associated with each of the user-to-software-application-instance-pairings. Log files are created at corresponding ones of the log creation facilities in response to detecting errors during execution of the instances of the software applications. The log files are categorized based on error categories. A request for a post error analysis report is received. The request specifies one of the error categories. A subset of the log files is determined based on the specified error category specified in the request. The subset of the log files is displayed. One of the identifiers is displayed for each error described in the post error analysis report.
Opening claim text (preview).
We claim: 1. A non-transitory processor-readable storage device including instructions for a method of implementing a post error analysis system that includes log creation facilities associated with instances of software applications that users interact with, wherein the non-transitory processor-readable storage device includes instructions executable by one or more processors for: creating user-to-software-application-instance-pairings, wherein each of the pairings is a unique relationship between one of the users and one of the instances of the software applications; receiving identifiers for the user-to-software-application-instance-pairings, wherein there is a separate identifier for each of the user-to-software-application-instance-pairings; associating one of the log creation facilities with each of the user-to-software-application-instance-pairings; creating log files at corresponding ones of the log creation facilities in response to detecting errors during execution of the instances of the software applications; categorizing the log files based on error categories, wherein each of the log files includes a corresponding one of the error categories; storing the log files in a log file repository of the post error analysis system; receiving a request for a post error analysis report, wherein the request specifies one of the error categories; determining a subset of the log files based on the specified error category specified in the request; and displaying the subset of the log files in the post error analysis report, wherein the post error analysis report includes one of the identifiers for each error described in the post error analysis report whereby post error analysis is performed on a per user basis. 2. The non-transitory processor-readable storage device of claim 1 , wherein the software applications are conventional software applications that were not modified to provide the post error analysis report. 3. The non-transitory processor-readable storage device of claim 1 , wherein the log file repository is a text file. 4. The non-transitory processor-readable storage device of claim 1 , wherein the non-transitory processor-readable storage device includes instructions executable by one or more processors for: interspersing log files for different software applications and different hosts with each other in the log file repository. 5. The non-transitory processor-readable storage device of claim 1 , wherein the identifiers are created based on one or more of an application instance name, a host name, and a cloud service environment (CSE) name. 6. The non-transitory processor-readable storage device of claim 1 , wherein the non-transitory processor-readable storage device includes instructions executable by one or more processors for: associating each of the user-to-software-application-pairs and each of the associated facilities with a cloud service environment selected from a plurality of cloud service environments. 7. The non-transitory processor-readable storage device of claim 6 , wherein each of the cloud service environments can include instances of the same application software or instances of different application software. 8. The non-transitory processor-readable storage device of claim 1 , wherein the post error analysis system resides in one of a test environment and a production environment. 9. The non-transitory processor-readable storage device of claim 1 , wherein the non-transitory processor-readable storage device includes instructions executable by one or more processors for: determining the subset of the log files based on the specified error category and one of the identifiers. 10. The non-transitory processor-readable storage device of claim 1 , wherein the non-transitory processor-readable storage device includes instructions executable by one or more processors for: comparing log files for a list of product packages; determining exception lines for each of the log files based on the comparing; and categorizing the log files based, at least in part, on respective ones of the exception lines. 11. A method of implementing a post error analysis system that includes log creation facilities associated with instances of software applications that users interact with, wherein the method comprises: creating user-to-software-application-instance-pairings, wherein each of the pairings is a unique relationship between one of the users and one of the instances of the software applications; receiving identifiers for the user-to-software-application-instance-pairings, wherein there is a separate identifier for each of the user-to-software-application-instance-pairings; associating one of the log creation facilities with each of the user-to-software-application-instance-pairings; creating log files at corresponding ones of the log creation facilities in response to detecting errors during execution of the instances of the software applications; categorizing the log files based on error categories, wherein each of the log files includes a corresponding one of the error categories; storing the log files in a log file repository of the post error analysis system; receiving a request for a post error analysis report, wherein the request specifies one of the error categories; determining a subset of the log files based on the specified error category specified in the request; and displaying the subset of the log files in a post error analysis report, wherein the post error analysis report includes one of the identifiers for each error described in the post error analysis report whereby post error analysis is performed on a per user basis. 12. The method of claim 11 , wherein the software applications are conventional software applications that were not modified to provide the post error analysis report. 13. The method of claim 11 , wherein the log file repository is not a database. 14. The method of claim 11 , wherein the non-transitory processor-readable storage device includes instructions executable by one or more processors for: interspersing log files for different software applications and different hosts with each other in the log file repository. 15. The method of claim 11 , wherein the identifiers are created based on one or more of an application instance name, a host name, and a cloud service environment (CSE) name. 16. The method of claim 11 , wherein each of the pairings and each of the associated log creation facilities execute on a separate one of a plurality of hosts and wherein the hosts are servers. 17. The method of claim 16 , wherein each of the hosts executes in one of a plurality of cloud service environments. 18. The method of claim 11 , wherein the post error analysis system resides in one of a test environment and a production environment. 19. The method of claim 11 , wherein the non-transitory processor-readable storage device includes instructions executable by one or more processors for: determining the subset of the log files based on the specified error category and one of the identifiers. 20. An apparatus for implementing a post error analysis system that includes log creation facilities associated with instances of software applications that users interact with comprising: one or more processors; and a non-transitory processor-readable storage device including instructions for: creating user-to-software-application-instance-pairings, wherein each of the pairings is a unique relationship between one of the users and one of the instances o
Content or structure details of the error report, e.g. specific table structure, specific error fields · 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
in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems · CPC title
Routing of error reports, e.g. with a specific transmission path or data flow · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.