SYSTEMS AND METHODS FOR LOG GENERATION AND LOG OBFUSCATION USING SDKS

• US 20140310679A1
• Filed: 08/19/2013
• Published: 10/16/2014
• 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, Kumble, Ravi Udaya, Aluri, Venu, Muraleedharan Prasad, Krishna, Patel, Vitesh
• Granted Patent: US 9,411,708 B2
• Time in Patent Office: Days
• US Class Current: 717/102
• 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 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.

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

obtaining a developer-specific log obfuscation schema specifying at least a developer-specific set of variables to be obfuscated and associated code line numbers;

obtaining a developer-independent log obfuscation schema specifying at least a developer-independent set of variables to be obfuscated and associated code line numbers;

extracting the specifications of the developer-specific and developer-independent sets of variables to be obfuscated and associated code line numbers;

generating a log obfuscation schema specifying at least a combination of the developer-specific and developer-independent sets of variables to be obfuscated and associated code line numbers; and

storing the log obfuscation schema.

3. The system of claim 2, wherein the application log schema and log obfuscation schema are stored as a single schema.

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

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

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

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

6. 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.

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

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

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

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

9. The system of claim 8, 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.

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

11. An application logging configuration method, 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.

12. The method of claim 11, further comprising:

obtaining a developer-specific log obfuscation schema specifying at least a developer-specific set of variables to be obfuscated and associated code line numbers;

obtaining a developer-independent log obfuscation schema specifying at least a developer-independent set of variables to be obfuscated and associated code line numbers;

extracting the specifications of the developer-specific and developer-independent sets of variables to be obfuscated and associated code line numbers;

generating a log obfuscation schema specifying at least a combination of the developer-specific and developer-independent sets of variables to be obfuscated and associated code line numbers; and

storing the log obfuscation schema.

13. The method of claim 12, wherein the application log schema and log obfuscation schema are stored as a single schema.

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

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

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

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

16. 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.

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

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

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

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

19. The method of claim 18, 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.

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

21. 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 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.

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

obtaining a developer-specific log obfuscation schema specifying at least a developer-specific set of variables to be obfuscated and associated code line numbers;

obtaining a developer-independent log obfuscation schema specifying at least a developer-independent set of variables to be obfuscated and associated code line numbers;

extracting the specifications of the developer-specific and developer-independent sets of variables to be obfuscated and associated code line numbers;

generating a log obfuscation schema specifying at least a combination of the developer-specific and developer-independent sets of variables to be obfuscated and associated code line numbers; and

storing the log obfuscation schema.

23. The medium of claim 22, wherein the application log schema and log obfuscation schema are stored as a single schema.

24. The medium of claim 21, wherein the application is a web service application.

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

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

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

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

27. The medium of claim 22, wherein one of:

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

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

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

29. The medium of claim 28, 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.

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