DERIVING BUSINESS TRANSACTIONS FROM WEB LOGS

• US 20140337069A1
• Filed: 05/08/2013
• Published: 11/13/2014
• Est. Priority Date: 05/08/2013
• Status: Abandoned Application

• Current Assignee: Infosys Limited
• Original Assignee: Infosys Limited
• Inventors: Gawande, Amit
• Application Number:
  US13/890,214
• Publication Number:
  US 20140337069A1
• Time in Patent Office: Days
• US Class Current: 705/7.11
• CPC Class Codes: G06Q 10/063 Operations research, analysis or management

Abstract

Computer-implemented systems, methods, and computer-readable media for deriving probable business transactions from a log file, the log file including a plurality of entries corresponding to traffic on a web server, each entry including a plurality of fields, including: pre-processing the log file to remove one or more fields and one or more entries unrelated to probable business transactions; processing the entries in the log file to identify one or more transactions; and processing the one or more transactions to identify one or more probable business transactions.

Claims

1. A computer-implemented method executed by one or more computing devices for deriving probable business transactions from a log file, the log file including a plurality of entries corresponding to traffic on a web server, each entry including a plurality of fields, the method comprising:

pre-processing, by at least one of the one or more computing devices, the log file to remove one or more fields and one or more entries unrelated to probable business transactions;

processing, by at least one of the one or more computing devices, the entries in the log file to identify one or more transactions; and

processing, by at least one of the one or more computing devices, the one or more transactions to identify one or more probable business transactions.

2. The method of claim 1, where the step of pre-processing the log file to remove one or more fields and one or more entries unrelated to probable business transactions further comprises at least one of:

identifying and purging one or more entries in the log file that were not received and accepted by the web server;

identifying and purging one or more entries mistakenly identified as being from a single user;

identifying and purging one or more entries for supporting resources; and

masking a dynamic portion of one or more entries.

3. The method of claim 2, wherein one or more entries are flagged as mistakenly identified when a date_and_time of the chronologically next entry is less than the sum of a date_and_time of the current entry and a time_taken of the current entry.

4. The method of claim 1, wherein the step of processing the entries in the log file to identify one or more transactions further comprises:

identifying a sequence of uniform resource locators (URLs) traversed by a user;

parsing the sequence of URLs into a set of unique transactions; and

identifying a count of times each transaction is traversed.

5. The method of claim 4, further comprising:

identifying a second sequence of URLs traversed by a second user;

parsing the second sequence of URLs into a set of unique transactions; and

identifying the count of times each transaction is traversed,

wherein the count is a global variable providing a count of times each transaction is traversed independent of the user.

6. The method of claim 1, wherein the step of processing the one or more transactions to identify one or more probable business transactions further comprises at least one of:

discarding one or more transactions having less than a threshold minimum transaction length;

discarding one or more transactions having a user count percentage less than a threshold confidence factor;

discarding one or more transactions occurring less than a threshold percentage in comparison to all of the one or more transactions; and

identifying one or more sub-transactions and merging each sub-transaction into another transactions.

7. The method of claim of claim 1, wherein the step of processing the one or more transactions to identify one or more probable business transactions further comprises:

determining whether each of the one or more transactions is a sub-transaction of another transaction in the one or more transactions,

wherein a sub-transaction of another transaction is a transaction that satisfies at least one of the following;

the transaction starts as the same universal resource locator (URL) sequence as the another transaction and includes an identical partial URL sequence as the another transaction but ends before the another transaction, and

the transaction terminates at the same URL as the another transaction and ends with an identical partial URL sequence as the another transaction but does not start that the beginning URL of the another transaction; and

purging the sub-transaction and incrementing a transaction count of the another transaction if the transaction is identified as a sub-transaction of the another transaction.

8. A system for deriving probable business transactions from a log file, the log file including a plurality of entries corresponding to traffic on a web server, each entry including a plurality of fields, the system comprising:

a memory; and

a processor operatively coupled to the memory, the processor configured to perform the steps of;

pre-processing the log file to remove one or more fields and one or more entries unrelated to probable business transactions;

processing the entries in the log file to identify one or more transactions; and

processing the one or more transactions to identify one or more probable business transactions.

9. The system of claim 8, where the step of pre-processing the log file to remove one or more fields and one or more entries unrelated to probable business transactions further comprises at least one of:

identifying and purging one or more entries in the log file that were not received and accepted by the web server;

identifying and purging one or more entries mistakenly identified as being from a single user;

identifying and purging one or more entries for supporting resources; and

masking a dynamic portion of one or more entries.

10. The system of claim 9, wherein one or more entries are flagged as mistakenly identified when a date_and_time of the chronologically next entry is less than the sum of a date_and_time of the current entry and a time_taken of the current entry.

11. The system of claim 8, wherein the step of processing the entries in the log file to identify one or more transactions further comprises:

identifying a sequence of uniform resource locators (URLs) traversed by a user;

parsing the sequence of URLs into a set of unique transactions; and

identifying a count of times each transaction is traversed.

12. The system of claim 11, wherein the processor further performs the steps of:

identifying a second sequence of URLs traversed by a second user;

parsing the second sequence of URLs into a set of unique transactions; and

identifying the count of times each transaction is traversed,

wherein the count is a global variable providing a count of times each transaction is traversed independent of the user.

13. The system of claim 8, wherein the step of processing the one or more transactions to identify one or more probable business transactions further comprises at least one of:

discarding one or more transactions having less than a threshold minimum transaction length;

discarding one or more transactions having a user count percentage less than a threshold confidence factor;

discarding one or more transactions occurring less than a threshold percentage in comparison to all of the one or more transactions; and

identifying one or more sub-transactions and merging each sub-transaction into another transactions.

14. The system of claim of claim 8, wherein the step of processing the one or more transactions to identify one or more probable business transactions further comprises:

determining whether each of the one or more transactions is a sub-transaction of another transaction in the one or more transactions,

wherein a sub-transaction of another transaction is a transaction that satisfies at least one of the following;

the transaction starts as the same universal resource locator (URL) sequence as the another transaction and includes an identical partial URL sequence as the another transaction but ends before the another transaction, and

the transaction terminates at the same URL as the another transaction and ends with an identical partial URL sequence as the another transaction but does not start that the beginning URL of the another transaction; and

purging the sub-transaction and incrementing a transaction count of the another transaction if the transaction is identified as a sub-transaction of the another transaction.

15. A non-transitory computer-readable medium having computer-readable code stored thereon that, when executed by a computing device, performs a method for deriving probable business transactions from a log file, the log file including a plurality of entries corresponding to traffic on a web server, each entry including a plurality of fields, the method comprising:

pre-processing the log file to remove one or more fields and one or more entries unrelated to probable business transactions;

processing the entries in the log file to identify one or more transactions; and

processing the one or more transactions to identify one or more probable business transactions.

16. The medium of claim 15, where the step of pre-processing the log file to remove one or more fields and one or more entries unrelated to probable business transactions further comprises at least one of:

identifying and purging one or more entries in the log file that were not received and accepted by the web server;

identifying and purging one or more entries mistakenly identified as being from a single user;

identifying and purging one or more entries for supporting resources; and

masking a dynamic portion of one or more entries.

17. The medium of claim 16, wherein one or more entries are flagged as mistakenly identified when a date_and_time of the chronologically next entry is less than the sum of a date_and_time of the current entry and a time_taken of the current entry.

18. The medium of claim 15, wherein the step of processing the entries in the log file to identify one or more transactions further comprises:

identifying a sequence of uniform resource locators (URLs) traversed by a user;

parsing the sequence of URLs into a set of unique transactions; and

identifying a count of times each transaction is traversed.

19. The medium of claim 18, wherein the method further comprises:

identifying a second sequence of URLs traversed by a second user;

parsing the second sequence of URLs into a set of unique transactions; and

identifying the count of times each transaction is traversed,

wherein the count is a global variable providing a count of times each transaction is traversed independent of the user.

20. The method of claim 15, wherein the step of processing the one or more transactions to identify one or more probable business transactions further comprises at least one of:

discarding one or more transactions having less than a threshold minimum transaction length;

discarding one or more transactions having a user count percentage less than a threshold confidence factor;

discarding one or more transactions occurring less than a threshold percentage in comparison to all of the one or more transactions; and

identifying one or more sub-transactions and merging each sub-transaction into another transactions.