Use case: eCommerce behavior analysis

This is an example of how you can use Devo to analyze the behavior of an e-commerce website managed through an Apache Web server. Through this process, you can have an overview of the Devo basic functions and learn how to use them. For this analysis, we have built a set of preloaded data from a fictitious online shop called www.logcasts.com. The data contains information related to product inventory, requests for product listing, availability, orders, cancellations, etc. The server logs are sent to the Devo server and stored in the demo.ecommerce.data table.

The data source is a simulated web server log format with the following structure:

Column name	Description
eventdate	Date when the event has arrived to Devo
ClientIpAddress	IP address of the remote host from where the request has been made
Timestamp	Exact time when the event has occurred
Method	HTTP method used (GET or POST)
URI	Requested URI
protocol	HTTP version
statusCode	The status code is the code returned by the server to the client requests, according to the HTTP protocol. These are the main used status codes: 1XX = General request information 2XX = Correct requests 200 = OK 3XX = Redirection 4XX = Client Errors 400 = Bad Request 404 = Not Found 406 = Not Acceptable (data format not accepted by customer) 408 = Request Timeout 5XX = Server Errors 500 = Internal Server Error 503 = Service Unavailable
bytesTransferred	Size in bytes of the object sent to the client
referralUri	The website address that created the requested link
userAgent	Software used by the client (browser, application, etc.)
cookie	Transferred cookie
timeTaken	Time taken to process the request

Read the following articles to get more information on some of the functionalities you can use to manage, analyze and display the information stored in the query window.