Automated server controlled client-side logging

• US 8,239,493 B2
• Filed: 04/21/2009
• Issued: 08/07/2012
• Est. Priority Date: 04/21/2009
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Hepper, Stefan, Lamb, Marshall Allen
• Primary Examiner(s): JAKOVAC, RYAN J
• Application Number:
  US12/427,273
• Publication Number:
  US 20100268759A1
• Time in Patent Office: 1,204 Days
• Field of Search: 709/219
• US Class Current: 709/219
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34

Abstract

A request for web content is received from a web client device at a web content server. At least one of a logging enablement status and a logging level associated with the web content is determined. Client-side logging executable syntax is configured within the web content based upon the determined logging enablement status and logging level associated with the web content. The web content with the configured client-side logging executable syntax is sent to the web client device. This abstract is not to be considered limiting, since other embodiments may deviate from the features described in this abstract.

Claims

1. A method, comprising:

receiving, at a web content server, a request for web content from a web client device, where the web content comprises executable syntax;

determining at least one of a logging enablement status and a logging level associated with the web content, comprising;

assembling markup language (ML) elements of the web content; and

identifying a Java tag reference within the web content, where the Java tag reference identifies a component within a Java taglib configured based upon the at least one of the logging enablement status and the logging level associated with the web content;

configuring client-side web content execution logging executable syntax within the web content based upon the determined at least one of the logging enablement status and the logging level associated with the web content, comprising;

importing the Java taglib into a JavaServer Pages (JSP) component; and

executing the Java taglib;

where the client-side web content execution logging executable syntax provides debugging and diagnostic capabilities for the executable syntax of the web content during execution of the executable syntax of the web content by the web client device; and

sending the web content with the configured client-side web content execution logging executable syntax to the web client device.

2. The method of claim 1, where the request for the web content received from the web client device comprises at least one of an Internet protocol (IP) address associated with the web client device and a user identifier (ID) associated with the web client device and where:

determining the at least one of the logging enablement status and the logging level associated with the web content comprises determining the at least one of the logging enablement status and the logging level associated with the web content based upon the at least one of the Internet protocol (IP) address associated with the web client device and the user ID associated with the web client device; and

configuring the client-side web content execution logging executable syntax within the web content based upon the determined at least one of the logging enablement status and the logging level associated with the web content comprises configuring the client-side web content execution logging executable syntax within the web content based upon the at least one of the Internet protocol (IP) address associated with the web client device and the user identifier (ID) associated with the web client device.

3. The method of claim 1, further comprising:

receiving client-side logging information from the web client device in response to execution of the configured client-side web content execution logging executable syntax by the web client device; and

storing the received client-side logging information within a memory associated with the web content server.

4. The method of claim 3, where the client-side web content execution logging executable syntax comprises at least one Javascript variable associated with the at least one of the logging enablement status and the logging level associated with the web content and where configuring the client-side web content execution logging executable syntax within the web content comprises inserting the at least one Javascript variable associated with the at least one of the logging enablement status and the logging level into the web content.

5. The method of claim 1, where configuring the client-side web content execution logging executable syntax within the web content based upon the determined at least one of the logging enablement status and the logging level associated with the web content comprises:

configuring client-specific web content execution logging executable syntax within the web content that instructs the web client device to generate client-specific logging information distinct from server-specific logging information generated by the web content server.

6. The method of claim 1, further comprising:

receiving client-side logging information from the web client device in response to execution of the configured client-side web content execution logging executable syntax by the web client device; and

combining the client-side logging information received from the web client device with server-side logging information generated by the web content server.

7. The method of claim 1, further comprising receiving a request to enable client-side logging from the web client device and where configuring the client-side web content execution logging executable syntax within the web content is performed in response to receipt of the request to enable client-side logging received from the web client device.

8. A system, comprising:

a memory adapted to store logging information; and

a processor programmed to;

receive, at a web content server, a request for web content from a web client device, where the web content comprises executable syntax;

determine at least one of a logging enablement status and a logging level associated with the web content based upon the logging information stored within the memory, where the processor is programmed to;

assemble markup language (ML) elements of the web content; and

identify a Java tag reference within the web content, where the Java tag reference identifies a component within a Java taglib configured based upon the at least one of the logging enablement status and the logging level associated with the web content;

configure client-side web content execution logging executable syntax within the web content based upon the determined at least one of the logging enablement status and the logging level associated with the web content, where the processor is programmed to;

import the Java taglib into a JavaServer Pages (JSP) component; and

execute the Java taglib;

where the client-side web content execution logging executable syntax provides debugging and diagnostic capabilities for the executable syntax of the web content during execution of the executable syntax of the web content by the web client device; and

send the web content with the configured client-side web content execution logging executable syntax to the web client device.

9. The system of claim 8, where the request for the web content received from the web client device comprises at least one of an Internet protocol (IP) address associated with the web client device and a user identifier (ID) associated with the web client device and where:

in being programmed to determine the at least one of the logging enablement status and the logging level associated with the web content, the processor is programmed to determine the at least one of the logging enablement status and the logging level associated with the web content based upon the at least one of the Internet protocol (IP) address associated with the web client device and the user ID associated with the web client device; and

in being programmed to configure the client-side web content execution logging executable syntax within the web content based upon the determined at least one of the logging enablement status and the logging level associated with the web content, the processor is programmed to configure the client-side web content execution logging executable syntax within the web content based upon the at least one of the Internet protocol (IP) address associated with the web client device and the user identifier (ID) associated with the web client device.

10. The system of claim 8, where the processor is further programmed to:

receive client-side logging information from the web client device in response to execution of the configured client-side web content execution logging executable syntax by the web client device; and

store the received client-side logging information within the memory.

11. The system of claim 10, where the client-side web content execution logging executable syntax comprises at least one Javascript variable associated with the at least one of the logging enablement status and the logging level associated with the web content and where, in being programmed to configure the client-side web content execution logging executable syntax within the web content, the processor is programmed to insert the at least one Javascript variable associated with the at least one of the logging enablement status and the logging level into the web content.

12. The system of claim 8, where, in being programmed to configure the client-side web content execution logging executable syntax within the web content based upon the determined at least one of the logging enablement status and the logging level associated with the web content, the processor is programmed to:

configure client-specific web content execution logging executable syntax within the web content that instructs the web client device to generate client-specific logging information distinct from server-specific logging information generated by the web content server.

13. The system of claim 8, where the processor is further programmed to:

receive client-side logging information from the web client device in response to execution of the configured client-side web content execution logging executable syntax by the web client device; and

combine the client-side logging information received from the web client device with server-side logging information generated by the web content server.

14. The system of claim 8, where the processor is further programmed to:

receive a request to enable client-side logging from the web client device; and

configure the client-side web content execution logging executable syntax within the web content in response to receipt of the request to enable client-side logging received from the web client device.

15. A system, comprising:

a memory adapted to store logging configuration information; and

a processor programmed to;

receive, at a web content server, a request for web content from a web client device;

determine at least one of a logging enablement status and a logging level associated with the web content based upon the logging information stored within the memory;

assemble markup language (ML) elements of the web content;

identify a Java tag reference within the web content, where the Java tag reference identifies a component within a Java taglib configured based upon the at least one of the logging enablement status and the logging level associated with the web content;

import the Java taglib into a JavaServer Pages (JSP) component;

execute the Java taglib;

generate, via the Java taglib component, client-side logging executable syntax comprising at least one Javascript variable associated with the at least one of the logging enablement status and the logging level associated with the web content;

insert the client-side logging executable syntax into the web content;

send the web content with the configured client-side logging executable syntax to the web client device;

receive client-side logging information from the web client device in response to execution of the configured client-side logging executable syntax by the web client device; and

store the received client-side logging information to the memory.

16. A computer program product comprising a computer useable storage device including a computer readable program, wherein the computer readable program when executed on a computer causes the computer to:

receive, at a web content server, a request for web content from a web client device, where the web content comprises executable syntax;

determine at least one of a logging enablement status and a logging level associated with the web content, comprising causing the computer to;

assemble markup language (ML) elements of the web content; and

identify a Java tag reference within the web content, where the Java tag reference identifies a component within a Java taglib configured based upon the at least one of the logging enablement status and the logging level associated with the web content;

configure client-side web content execution logging executable syntax within the web content based upon the determined at least one of the logging enablement status and the logging level associated with the web content, comprising causing the computer to;

import the Java taglib into a JavaServer Pages (JSP) component; and

execute the Java taglib;

where the client-side web content execution logging executable syntax provides debugging and diagnostic capabilities for the executable syntax of the web content during execution of the executable syntax of the web content by the web client device; and

send the web content with the configured client-side web content execution logging executable syntax to the web client device.

17. The computer program product of claim 16, where the request for the web content received from the web client device comprises at least one of an Internet protocol (IP) address associated with the web client device and a user identifier (ID) associated with the web client device and where:

in causing the computer to determine the at least one of the logging enablement status and the logging level associated with the web content, the computer readable program when executed on the computer causes the computer to determine the at least one of the logging enablement status and the logging level associated with the web content based upon the at least one of the Internet protocol (IP) address associated with the web client device and the user ID associated with the web client device; and

in causing the computer to configure the client-side web content execution logging executable syntax within the web content based upon the determined at least one of the logging enablement status and the logging level associated with the web content, the computer readable program when executed on the computer causes the computer to configure the client-side web content execution logging executable syntax within the web content based upon the at least one of the Internet protocol (IP) address associated with the web client device and the user identifier (ID) associated with the web client device.

18. The computer program product of claim 16, where the computer readable program when executed on the computer further causes the computer to:

receive client-side logging information from the web client device in response to execution of the configured client-side web content execution logging executable syntax by the web client device; and

store the received client-side logging information within a memory associated with the web content server.

19. The computer program product of claim 18, where the client-side web content execution logging executable syntax comprises at least one Javascript variable associated with the at least one of the logging enablement status and the logging level associated with the web content and where, in causing the computer to configure the client-side web content execution logging executable syntax within the web content, the computer readable program when executed on the computer causes the computer to insert the at least one Javascript variable associated with the at least one of the logging enablement status and the logging level into the web content.

20. The computer program product of claim 16, where, in causing the computer to configure the client-side web content execution logging executable syntax within the web content based upon the determined at least one of the logging enablement status and the logging level associated with the web content, the computer readable program when executed on the computer causes the computer to:

configure client-specific web content execution logging executable syntax within the web content that instructs the web client device to generate client-specific logging information distinct from server-specific logging information generated by the web content server.

21. The computer program product of claim 16, where the computer readable program when executed on the computer further causes the computer to:

receive client-side logging information from the web client device in response to execution of the configured client-side web content execution logging executable syntax by the web client device; and

combine the client-side logging information received from the web client device with server-side logging information generated by the web content server.

22. The computer program product of claim 16, where the computer readable program when executed on the computer further causes the computer to:

receive a request to enable client-side logging from the web client device; and

configure the client-side web content execution logging executable syntax within the web content in response to receipt of the request to enable client-side logging received from the web client device.