Systems and methods for web logging of trace data in a multi-core system

• US 8,219,676 B2
• Filed: 06/22/2010
• Issued: 07/10/2012
• Est. Priority Date: 06/22/2009
• Status: Active Grant

• Current Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Original Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Inventors: Chauhan, Abhishek, Jagadish, Ashwin, Joshi, Rajesh, Annamalaisami, Saravana
• Primary Examiner(s): Gillis, Brian J
• Application Number:
  US12/820,736
• Publication Number:
  US 20100325371A1
• Time in Patent Office: 749 Days
• Field of Search: 709/213, 709/216, 709/224, 711/150, 711/151
• US Class Current: 709/224
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 2201/875 Monitoring of systems including the internet
• CPC Class Codes: H04L 43/0852 Delays
• CPC Class Codes: H04L 43/0876 Network utilisation, e.g. volume of load or congestion level
• CPC Class Codes: H04L 43/106 using time related information in packets, e.g. by adding timestamps

Abstract

A method and system for generating a web log that includes transaction entries from transaction queues of one or more cores of a multi-core system. A transaction queue is maintained for each core so that either a packet engine or web logging client executing on the core can write transaction entries to the transaction queue. In some embodiments, a timestamp value obtained from a synchronized timestamp variable can be assigned to the transaction entries. When a new transaction entry is added to the transaction queue, the earliest transaction entry is removed from the transaction queue and added to a heap. Periodically the earliest entry in the heap is removed from the heap and written to a web log. When an entry is removed from the heap, the earliest entry in a transaction queue corresponding to the removed entry is removed from the transaction queue and added to the heap.

Claims

1. A method for storing transaction entries generated by packet engines of cores of a multi-core system to a heap, the method comprising:

writing, by a first core of a multi-core system to a first transaction queue of the first core, a first transaction entry having a first timestamp;

extracting, by a logging client executing on the multi-core system responsive to determining the first core wrote to the first transaction queue, the first transaction entry from the first transaction queue;

chronologically storing, by the logging client, the extracted first transaction entry in a heap comprising a chronological list of transaction entries;

writing, by a second core of the multi-core system to a second transaction queue of the second core, a second transaction entry having a second timestamp later than the first timestamp of the first transaction entry;

extracting, by the logging client responsive to determining the second core wrote to the second transaction queue, the second transaction entry from the second transaction queue; and

chronologically storing, by the logging client, the extracted second transaction entry after the first transaction entry.

2. The method of claim 1, wherein:

writing the first transaction entry to the first transaction queue further comprises writing a first transaction entry generated by a first packet engine of the first core; and

wherein writing the second transaction entry to the second transaction queue further comprises writing a second transaction entry generated by a second packet engine of the second core.

3. The method of claim 1, wherein:

chronologically storing the first transaction entry further comprises storing the first transaction entry responsive to determining the first transaction entry does not reside in the heap; and

wherein chronologically storing the second transaction entry further comprises storing the second transaction entry responsive to determining the second transaction entry does not reside in the heap.

4. The method of claim 1, further comprising:

extracting, by the logging client, the first transaction entry from the heap;

identifying, by the logging client, a log file corresponding to the first transaction entry; and

updating, by the logging client, the log file with the first transaction entry.

5. The method of claim 4, further comprising:

extracting, by the logging client, another transaction entry from the first transaction queue; and

chronologically storing, by the logging client responsive to extracting the other transaction entry, the other transaction entry in the heap.

6. The method of claim 1, wherein:

extracting the first transaction entry further comprises identifying a transaction entry in the first transaction queue having an earliest timestamp, and extracting the identified transaction entry; and

wherein extracting the second transaction entry further comprises identifying a transaction entry in the second transaction queue having an earliest timestamp, and extracting the identified transaction entry.

7. The method of claim 1, wherein chronologically storing the extracted first transaction entry further comprises chronologically storing the first transaction entry after a transaction entry having an earlier timestamp.

8. A method for logging transaction entries generated by packet engines executing on cores of a multi-core system and stored in a heap, the method comprising:

identifying, by a logging client executing on a multi-core system, a first transaction entry stored in a heap comprising chronologically ordered transaction entries, the identified first transaction entry having an earlier timestamp than each additional transaction entry stored in the heap;

extracting, by the logging client, the first transaction entry from the heap, the first transaction entry corresponding to a transaction queue of a core in the multi-core system;

identifying, by the logging client responsive to extracting the first transaction entry, a log file corresponding to a filter corresponding to the first transaction entry;

updating, by the logging client, the log file with the first transaction entry;

extracting, by the logging client responsive to updating the log file, a second transaction entry from the transaction queue; and

storing, by the logging client, the second transaction entry in the heap.

9. The method of claim 8, wherein extracting the second transaction entry from the transaction queue further comprises extracting a transaction entry having an earliest timestamp.

10. The method of claim 8, wherein storing the second transaction entry in the heap further comprises storing the second transaction entry responsive to determining the second transaction entry does not reside in the heap.

11. The method of claim 8, wherein identifying the log file further comprises identifying a log file corresponding to a filter based on a tuple corresponding to the transaction entry.

12. The method of claim 8, further comprising generating, by a packet engine executing on the core, the first transaction entry and the second transaction entry.

13. The method of claim 12, further comprising writing the first transaction entry and the second transaction entry to the transaction queue of the core.