Systems and methods for log generation and log obfuscation using SDKs

• US 9,411,708 B2
• Filed: 08/19/2013
• Issued: 08/09/2016
• Est. Priority Date: 04/12/2013
• Status: Active Grant

• Current Assignee: Wipro Limited
• Original Assignee: Wipro Limited
• Inventors: Bhattacharya, Sourav S., Bhattacharya, Anirban, Shetty, Kuldip, Muraleedharan Prasad, Krishna, Kumble, Ravi Udaya, Aluri, Venu, Patel, Vitesh
• Primary Examiner(s): Bullock, Jr., Lewis A
• Assistant Examiner(s): Ashley, Bruce S
• Application Number:
  US13/970,203
• Publication Number:
  US 20140310679A1
• Time in Patent Office: 1,086 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 11/362 Software debugging
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program
• CPC Class Codes: G06F 2201/865 Monitoring of software

Abstract

This disclosure generally relates to application development platforms, and more particularly to systems and methods for log generation and log obfuscation using software development kits (SDKs). In one embodiment, an application logging configuration method is disclosed, comprising: obtaining, for an application, a developer-specific log generation schema specifying at least a developer-specific set of variables to be logged and associated code line numbers; obtaining a developer-independent log generation schema specifying at least a developer-independent set of variables to be logged and associated code line numbers; extracting the specifications of the developer-specific and developer-independent sets of variables to be logged and associated code line numbers; generating an application logging schema specifying at least a combination of the developer-specific and developer-independent sets of variables to be logged and associated code line numbers; and storing the application logging schema.

Claims

1. An application logging configuration system, comprising:

a processor; and

a memory device operatively connected to the processor and storing processor-executable instructions for;

obtaining, for an application, a developer-specific log generation schema specifying at least a first developer-specific set of variables of which values during an execution of the application are to be logged and code line numbers associated with code lines of the application that include the first developer-specific set of variables;

obtaining a developer-independent log generation schema specifying at least a first developer-independent set of variables of which values during an execution of the application are to be logged and code line numbers associated with code lines of the application that include the first developer-independent set of variables;

extracting the first developer-specific and developer-independent sets of variables from respectively the obtained developer-specific log generation schema and the obtained developer-independent log generation schema;

generating an application logging schema specifying, for each code line of at least part of the application, a first set of variables of which values during an execution of the application are to be logged, the first set of variables including a combination of at least some of the extracted first developer-specific set of variables and at least some of the extracted first developer-independent set of variables;

generating a log obfuscation schema specifying, for each code line of at least part of the application, a second set of variables of which values during an execution of the application are to be obfuscated from logging;

generating a single schema to include the application logging schema and log obfuscation schema;

storing the single schema; and

providing the single schema for log generation during an execution of the application.

2. The system of claim 1, the memory device further storing instructions for:

obtaining a developer-specific log obfuscation schema specifying at least a second developer-specific set of variables of which values during an execution of the application are to be obfuscated from logging and code line numbers associated with code lines that include the second developer-specific set of variables;

obtaining a developer-independent log obfuscation schema specifying at least a second developer-independent set of variables of which values during an execution of the application are to be obfuscated from logging and code line numbers associated with code lines that include the second developer-independent set of variables; and

extracting the second developer-specific and developer-independent sets of variables from respectively the obtained developer-specific log obfuscation schema and the obtained developer-independent log generation schema;

wherein the second set of variables of the log obfuscation schema include a combination of at least some of the extracted second developer-specific set of variables and at least some of the extracted second developer-independent sets of variables.

3. The system of claim 1, wherein the application is a web service application.

4. The system of claim 1, wherein one of:

the first developer-specific set of variables to be logged and associated code line numbers; and

the first developer-independent set of variables to be logged and associated code line numbers, is a null set.

5. The method of claim 1, wherein the developer-independent log generation schema is utilized to generate application logging schemas for all developers of the application.

6. The system of claim 2, wherein one of:

the second developer-specific set of variables to be obfuscated and associated code line numbers; and

the second developer-independent set of variables to be obfuscated and associated code line numbers, is a null set.

7. The system of claim 2, wherein the log obfuscation schema specifies an obfuscation method associated with a variable to be obfuscated.

8. The system of claim 7, wherein the obfuscation method associated with the variable to be obfuscated includes one of:

replacing a variable name with a numeric code;

replacing personally identifiable information with a token;

or replacing a data attachment with metadata.

9. The system of claim 7, wherein the obfuscation method includes encryption using an application-specific key.

10. The system of claim 1, wherein the application logging schema is associated with a timestamp configured to indicate a time when the application logging schema expires.

11. An application logging configuration method, comprising:

obtaining, for an application, a developer-specific log generation schema specifying at least a first developer-specific set of variables of which values during an execution of the application are to be logged and code line numbers associated with code lines of the application that include the first developer-specific set of variables;

obtaining a developer-independent log generation schema specifying at least a first developer-independent set of variables of which values during an execution of the application are to be logged and code line numbers associated with code lines of the application that include the first developer-independent set of variables;

extracting the first developer-specific and developer-independent sets of variables from respectively the obtained developer-specific log generation schema and the obtained developer-independent log generation schema;

generating an application logging schema specifying, for each code line of at least part of the application, a first set of variables of which values during an execution of the application are to be logged, the first set of variables including a combination of at least some of the extracted first developer-specific set of variables and at least some of the extracted first developer-independent set of variables;

generating a log obfuscation schema specifying, for each code line of at least part of the application, a second set of variables of which values during an execution of the application are to be obfuscated from logging;

generating a single schema to include the application logging schema and log obfuscation schema;

storing the single schema; and

providing the single schema for log generation during an execution of the application.

12. The method of claim 11, further comprising:

obtaining a developer-specific log obfuscation schema specifying at least a second developer-specific set of variables of which values during an execution of the application are to be obfuscated from logging and code line numbers associated with code lines that include the second developer-specific set of variables;

obtaining a developer-independent log obfuscation schema specifying at least a second developer-independent set of variables of which values during an execution of the application are to be obfuscated from logging and code line numbers associated with code lines that include the second developer-independent set of variables; and

extracting the second developer-specific and developer-independent sets of variables from respectively the obtained developer-specific log obfuscation schema and the obtained developer-independent log obfuscation schema;

wherein the second set of variables of the log obfuscation schema include a combination of at least some of the extracted second developer-specific set of variables and at least some of the extracted second developer-independent sets of variables.

13. The method of claim 11, wherein the application is a web service application.

14. The method of claim 11, wherein one of:

the first developer-specific set of variables to be logged and associated code line numbers; and

the first developer-independent set of variables to be logged and associated code line numbers, is a null set.

15. The method of claim 11, wherein the developer-independent log generation schema is utilized to generate application logging schemas for all developers of the application.

16. The method of claim 12, wherein one of:

the second developer-specific set of variables to be obfuscated and associated code line numbers; and

the second developer-independent set of variables to be obfuscated and associated code line numbers, is a null set.

17. The method of claim 12, wherein the log obfuscation schema specifies an obfuscation method associated with a variable to be obfuscated.

18. The method of claim 17, wherein the obfuscation method associated with the variable to be obfuscated includes one of:

replacing a variable name with a numeric code;

replacing personally identifiable information with a token;

or replacing a data attachment with metadata.

19. The method of claim 17, wherein the obfuscation method includes encryption using an application-specific key.

20. A non-transitory computer-readable medium storing computer-executable application logging configuration instructions, comprising instructions for:

obtaining, for an application, a developer-specific log generation schema specifying at least a first developer-specific set of variables of which values during an execution of the application are to be logged and code line numbers associated with code lines of the application that include the first developer-specific set of variables;

obtaining a developer-independent log generation schema specifying at least a first developer-independent set of variables of which values during an execution of the application are to be logged and code line numbers associated with code lines of the application that include the first developer-independent set of variables;

extracting the first developer-specific and developer-independent sets of variables from respectively the obtained developer-specific log generation schema and the obtained developer-independent log generation schema;

generating an application logging schema specifying, for each code line of at least part of the application, a first set of variables of which values during an execution of the application are to be logged, the first set of variables including a combination of at least some of the first developer-specific set of variables and at least some of the first developer-independent set of variables;

generating a log obfuscation schema specifying, for each code line of at least part of the application, a second set of variables of which values during an execution of the application are to be obfuscated from logging;

generating a single schema to include the application logging schema and log obfuscation schema;

storing the single schema; and

providing the single schema for log generation during an execution of the application.

21. The medium of claim 20, further storing instructions for:

obtaining a developer-specific log obfuscation schema specifying at least a second developer-specific set of variables of which values during an execution of the application are to be obfuscated from logging and code line numbers associated with code lines of the application that include the second developer-specific set of variables;

obtaining a developer-independent log obfuscation schema specifying at least a second developer-independent set of variables of which values during an execution of the application are to be obfuscated from logging and code line numbers associated with code lines of the application that include the second developer-independent set of variables; and

extracting the second developer-specific and developer-independent sets of variables and associated code line numbers from respectively the obtained developer-specific log obfuscation schema and the obtained developer-independent log obfuscation schema;

wherein the first set of variables of the log obfuscation schema include a combination of at least some of the extracted second developer-specific variables and at least some of the extracted second developer-independent sets of variables.

22. The medium of claim 20, wherein the application is a web service application.

23. The medium of claim 20, wherein one of:

the first developer-specific set of variables to be logged and associated code line numbers; and

the first developer-independent set of variables to be logged and associated code line numbers, is a null set.

24. The medium of claim 20, wherein the developer-independent log generation schema is utilized to generate application logging schemas for all developers of the application.

25. The medium of claim 21, wherein one of:

the second developer-specific set of variables to be obfuscated and associated code line numbers; and

the second developer-independent set of variables to be obfuscated and associated code line numbers, is a null set.

26. The medium of claim 21, wherein the log obfuscation schema specifies an obfuscation method associated with a variable to be obfuscated.

27. The medium of claim 26, wherein the obfuscation method associated with the variable to be obfuscated includes one of:

replacing a variable name with a numeric code;

replacing personally identifiable information with a token;

or replacing a data attachment with metadata.

28. The medium of claim 26, wherein the obfuscation method includes encryption using an application-specific key.