Contextualized notifications for verbose application errors

Patent metadata

Field	Value
Publication number	US-11314619-B2
Application number	US-202016997215-A
Country	US
Kind code	B2
Filing date	Aug 19, 2020
Priority date	Jun 16, 2017
Publication date	Apr 26, 2022
Grant date	Apr 26, 2022

Abstract

Errors encountered by executing applications can be recorded in one or more logs. A search engine can be configured to retrieve error data from the one or more logs using pre-specified rules. A portion of the error data can be included in a small portable message (e.g., SMS text message) and sent to the developers or administrators of the applications. An administrative console can generate different visualizations based upon what errors the search engine retrieved.

First claim

What is claimed is:

1. A method comprising:
receiving a stack trace log including a first set of programming code being executed when a first error was encountered in relation to execution of a first network application;
extracting a first portion of the first set of programming code that includes at least an application name of the first network application and an error type of the first error;
generating a notification message including the first portion of the first set of programming code and a link to an administrative user interface displaying the first set of programming code, including a non-extracted portion of the first set of programming code that is not included in the first portion; and
transmitting the notification to at least one electronic message address associated with the first network application.

2. The method of claim 1 , further comprising:
searching the stack trace log for pre-specified error data using a search engine, the search engine configured to search for the errors using pre-specified error terms.

3. The method of claim 1 , wherein the stack trace log includes a network request log and an execution log, the network request log comprising network request data describing network requests performed by the one or more network servers, the execution log comprising programming code executed by the one or more network servers during execution of the first network application.

4. The method of claim 3 , wherein the first portion includes data from the network request log and the non-extracted portion includes data from the execution log.

5. The method of claim 1 , further comprising:
determining, based on the stack trace log, a number of errors of a second error type encountered in relation to execution of the first network application;
comparing the number of errors of the second error type to a pre-specified threshold number; and
responsive to determining that the number of errors of the second error type do not surpass the pre-specified threshold number, determining that a notification related to the errors of the second error type should not be sent to the one or more users corresponding to the first network application.

6. The method of claim 1 , further comprising:
generating a visualization that indicates that errors of the first error type were encountered in relation to execution of the first network application and at least a second network application; and
including the visualization in the administrative user interface.

7. The method of claim 1 , further comprising:
determining that a number of errors of the first error type that were encountered in relation to execution of the first network application exceeds a threshold number, the threshold number being based on statistical normal error activity;
responsive to determining that the number of errors of the first error type exceeds the threshold number, generating a visualization that indicates a quantity of the errors of the first error type which surpasses the statistical normal error activity; and
including the visualization in the administrative user interface.

8. The method of claim 1 , wherein the at least one electronic message address is a short message service (SMS) address, and a number of characters included in the first portion of the first set of programming code is no greater than a maximum number of characters specified in an SMS protocol.

9. The method of claim 8 , wherein the non-extracted portion includes stack trace data from programming methods called when the first error was encountered.

10. A system comprising:
one or more computer processors; and
one or more computer-readable mediums storing instructions that, when executed by the one or more computer processors, cause the system to perform operations comprising:
receiving a stack trace log including a first set of programming code being executed when a first error was encountered in relation to execution of a first network application;
extracting a first portion of the first set of programming code that includes at least an application name of the first network application and an error type of the first error;
generating a notification message including the first portion of the first set of programming code and a link to an administrative user interface displaying the first set of programming code, including a non-extracted portion of the first set of programming code that is not included in the first portion; and
transmitting the notification to at least one electronic message address associated with the first network application.

11. The system of claim 10 , the operations further comprising:
searching the stack trace log for pre-specified error data using a search engine, the search engine configured to search for the errors using pre-specified error terms.

12. The system of claim 10 , wherein the stack trace log includes a network request log and an execution log, the network request log comprising network request data describing network requests performed by the one or more network servers, the execution log comprising programming code executed by the one or more network servers during execution of the first network application.

13. The system of claim 12 , wherein the first portion includes data from the network request log and the non-extracted portion includes data from the execution log.

14. The system of claim 10 , the operations further comprising:
determining, based on the stack trace log, a number of errors of a second error type encountered in relation to execution of the first network application;
comparing the number of errors of the second error type to a pre-specified threshold number; and
responsive to determining that the number of errors of the second error type do not surpass the pre-specified threshold number, determining that a notification related to the errors of the second error type should not be sent to the one or more users corresponding to the first network application.

15. The system of claim 10 , the operations further comprising:
generating a visualization that indicates that errors of the first error type were encountered in relation to execution of the first network application and at least a second network application; and
including the visualization in the administrative user interface.

16. The system of claim 10 , the operations further comprising:
determining that a number of errors of the first error type that were encountered in relation to execution of the first network application exceeds a threshold number, the threshold number being based on statistical normal error activity;
responsive to determining that the number of errors of the first error type exceeds the threshold number, generating a visualization that indicates a quantity of the errors of the first error type which surpasses the statistical normal error activity; and
including the visualization in the administrative user interface.

17. The system of claim 10 , wherein the at least one electronic message address is a short message service (SMS) address, and a number of characters included in the first portion of the first set of programming code is no greater than a maximum number of characters specified in an SMS protocol.

18. The system of claim 17 , wherein the non-extracted portion includes stack trace data from programming methods called when the first error was encountered.

19. A non-transitory computer-readable medium storing instructions that, when executed by one or more computer processors of one or more computing devices, caus

Assignees

• Palantir Technologies Inc

Inventors

• Demeuse Lauren
• Wu Grant
• Riechel Garren
• Mair Ian
• Nazario Michael

Classifications

• G06F11/3476 Primary

  Data logging (G06F11/14, G06F11/2205 take precedence) · CPC title

• G06F11/0781 Primary

  Error filtering or prioritizing based on a policy defined by the user or on a policy defined by a hardware/software module, e.g. according to a severity level · CPC title

• G06F11/0772

  Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers · CPC title

• G06F11/0769

  Readable error formats, e.g. cross-platform generic formats, human understandable formats · CPC title

• G06F11/079

  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