IDENTIFYING AN ANALYSIS REPORTING MESSAGE IN NETWORK TRAFFIC

• US 20150333985A1
• Filed: 01/03/2013
• Published: 11/19/2015
• Est. Priority Date: 01/03/2013
• Status: Active Grant

• Current Assignee: Micro Focus LLC (Open Text Corporation)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Gopshtein, Michael, Kenigsberg, Eyal, Offer, Guy
• Granted Patent: US 10,305,760 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 43/028 by filtering
• CPC Class Codes: H04L 43/04 Processing captured monitoring data, e.g. for logfile generation
• CPC Class Codes: H04L 43/062 related to network traffic
• CPC Class Codes: H04L 43/12 Network monitoring probes
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/562 Brokering proxy services

Abstract

Examples disclosed herein relate to identifying an analysis reporting message in network traffic. Examples include accessing network traffic exchanged with a web server application and identifying, in the network traffic, an analysis reporting message. In examples described herein, the analysis reporting message may include information representing a client system analysis of at least one prior transaction of the client system.

Claims

1. A non-transitory machine-readable storage medium encoded with instructions executable by a processing resource of a computing device to:

access network traffic exchanged with a web server application;

identify, in the accessed network traffic, an analysis reporting message of a client system; and

extract, from the analysis reporting message, information representing a client system analysis of at least one prior transaction between the client system and at least one of the web server application and a proxy server associated with the web server application.

2. The storage medium of claim 1, wherein the instructions to identify the analysis reporting message comprise instructions to:

identify, as the analysis reporting message, a message in the accessed network traffic sent to an analysis reporting uniform resource locator (URL) of the web server application.

3. The storage medium of claim 2, further comprising instructions to:

identify another message in the accessed network traffic sent to another URL of the web server application as a non-reporting message; and

analyze the non-reporting message in relation to other messages of the accessed network traffic to generate information representing network traffic analysis.

4. The storage medium of claim 1, wherein:

the at least one prior transaction comprises at least one prior transaction between the client system and the proxy server; and

the information representing the client system analysis comprises information describing an experience of the client system in relation to the at least one prior transaction between the client system and the proxy server.

5. The storage medium of claim 4, wherein the information describing the experience comprises an indication of an amount of time taken by the at least one prior transaction between the client system and the proxy server.

6. The storage medium of claim 4, wherein:

the at least one prior transaction between the client system and the proxy server comprises downloading, from the proxy server to the client system, content of a website implemented by the web server application, wherein the content is cached at the proxy server; and

the information describing the experience comprises an indication of an amount of time taken to download the content from the proxy server to the client system.

7. A system comprising:

a traffic engine to access network traffic exchanged with a web server application;

an identification engine to identify, as an analysis reporting message of a client system, a message in the accessed network traffic sent to an analysis reporting uniform resource locator (URL) of the web server application; and

an extraction engine to extract, from the analysis reporting message, information representing a client system analysis of at least one prior transaction associated with a request of the client system targeting another URL of the web server application.

8. The system of claim 7, wherein the at least one prior transaction comprises at least one prior transaction between the client system and a proxy server associated with the web server application.

9. The system of claim 8, wherein the proxy server is at least one server of a content delivery network (CDN).

10. The system of claim 9, wherein the identification engine is to:

identify the message in accessed network traffic exchanged between the web server application and the proxy server.

11. The system of claim 7, further comprising:

an analysis engine, wherein;

the identification engine is further to identify another message in the accessed network traffic sent to another URL of the web server application as a non-reporting message; and

the analysis engine is to analyze the non-reporting message in relation to other messages of the accessed network traffic to generate information representing network traffic analysis.

12. The system of c aim 7, wherein the information representing the client system analysis comprises information describing the subject matter of the at least one prior transaction.

13. A method comprising:

sniffing, with a probe system, network traffic exchanged with a web server application;

identifying, in the network traffic, an analysis reporting message of a client system;

parsing the analysis reporting message with the probe system, the analysis reporting message including information representing a client system analysis of at least one prior transaction between the client system and at least one of the web server application and a proxy server associated with the web server application; and

providing the information representing the client system analysis from the probe system to a data aggregator.

14. The method of claim 13, wherein the identifying comprises:

determining whether a message in the network traffic is targeting an analysis reporting uniform resource locator (URL) of the web server application; and

if the message is targeting the analysis reporting URL, identifying the message as the analysis reporting message.

15. The method of claim 14, further comprising:

if the message is not targeting the analysis reporting URL, analyzing the message in association with other messages of the network traffic to generate information representing a network traffic analysis; and

providing the information representing the network traffic analysis from the probe system to the data aggregator.