High speed logging system

• US 9,570,124 B2
• Filed: 01/09/2013
• Issued: 02/14/2017
• Est. Priority Date: 01/11/2012
• Status: Active Grant

• Current Assignee: Viavi Solutions, Inc. (Lumentum Holdings Inc.)
• Original Assignee: Viavi Solutions, Inc. (Lumentum Holdings Inc.)
• Inventors: Bauer, Samuel M.
• Primary Examiner(s): Bhatia, Ajay
• Assistant Examiner(s): KLICOS, NICHOLAS GEORGE
• Application Number:
  US13/737,206
• Publication Number:
  US 20130179821A1
• Time in Patent Office: 1,497 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1448 Management of the data involved in backup or backup restore
• CPC Class Codes: G06F 11/1458 Management of the backup or restore process
• CPC Class Codes: G06F 3/0481 based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
• CPC Class Codes: G06F 3/061 Improving I/O performance
• CPC Class Codes: G06F 3/0631 by allocating resources to storage systems
• CPC Class Codes: G06F 3/0656 Data buffering arrangements
• CPC Class Codes: G06F 3/0685 Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays
• CPC Class Codes: G11C 7/1072 for memories with random access ports synchronised on clock signal pulse trains, e.g. synchronous memories, self timed memories
• CPC Class Codes: H04L 41/0686 Additional information in the notification, e.g. enhancement of specific meta-data
• CPC Class Codes: H04L 41/069 using logs of notifications; Post-processing of notifications
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]

Abstract

A method of storing log entries of events from a plurality of network elements in a communication network, comprising the steps of: a) receiving log entries at a control processor of events from a plurality of different elements positioned, the log entries grouped into threads based on a common purpose; b) converting each log entry into a compact log record in a logging module, and c) storing the compact log records in a first memory buffer in random access memory (RAM) forming a first log file.

Claims

1. A method comprising:

receiving, by a device, log entries of events from a plurality of network elements,

the log entries being grouped by thread based on a particular purpose;

converting, by the device, each log entry into a log record of log records,

each log record comprising at least one of;

information associated with a record length of the log record,

information associated with a time stamp of data collection at a network element of the plurality of network elements,

information associated with a thread ID of a thread that logged each event of the events,

information associated with a category of each event,

information associated with a message ID code corresponding to a log message, or

information associated with a network element ID for identifying a respective network element associated with each event;

storing, by the device, a first plurality of the log records in a first memory buffer to form a log file;

allocating, by the device and based on an amount of data stored in the first memory buffer, a second memory buffer for a second plurality of the log records;

queuing, by the device and based on the amount of data stored in the first memory buffer, the first memory buffer to a background thread to write the first plurality of the log records to a disk file,

the background thread writing the first plurality of the log records to the disk file when one or more processing cycles are not needed by another thread that has a higher priority than the background thread;

associating, by the device and after the background thread writes the first plurality of the log records to the disk file, the first memory buffer with a free pool; and

storing, by the device and based on associating the first memory buffer with the free pool, a third plurality of the log records in the first memory buffer.

2. The method according to claim 1, further comprising:

storing a mapping file of text message strings corresponding to a plurality of different message ID codes.

3. The method according to claim 2,

where the first plurality of the log records are compact log records, and

where the method includes:

converting, using the mapping file, the compact log records to full log entries,

the full log entries including message ID codes and log messages; and

providing, for display, the full log entries on a graphic user interface (GUI).

4. The method according to claim 3, where the full log entries are provided, for display, on the GUI by time vs element ID for each thread.

5. The method according to claim 4, further comprising:

providing a separate line on the GUI for errors.

6. The method according to claim 1,

where the first plurality of the log records are compact log records, and

where the method includes:

converting the compact log records to full log entries utilizing a remote computer processor and a mapping file,

the mapping file including message ID codes and log messages; and

providing, for display, the full log entries on a graphic user interface (GUI).

7. The method according to claim 6, where the full log entries are provided, for display, on the GUI by time vs element ID for each thread.

8. The method according to claim 7, further comprising:

providing a separate line on the GUI for errors.

9. The method according to claim 1, where each network element, of the plurality of network elements, includes a test probe.

10. A device comprising:

a processor, implemented at least partially in hardware, to;

receive log entries of events from a plurality of network elements,

the log entries being grouped by thread based on a particular purpose;

convert each log entry into a log record of log records,

each log record comprising at least one of;

information associated with a record length of the log record,

information associated with a time stamp of data collection at a network element of the plurality of network elements,

information associated with a thread ID of a thread that logged each event of the events,

information associated with a category of each event,

information associated with a message ID code corresponding to a log message, or

information associated with a network element ID for identifying a respective network element associated with each event;

store a first plurality of the log records in a first memory buffer to form a log file;

allocate, based on an amount of data stored in the first memory buffer, a second memory buffer for a second plurality of the log records;

queue, based on the amount of data stored in the first memory buffer, the first memory buffer to a background thread to write the first plurality of the log records to a disk file,

the background thread writing the first plurality of the log records to the disk file when one or more processing cycles are not needed by another thread that has a higher priority than the background thread;

associate, after the background thread writes the first plurality of the log records to the disk file, the first memory buffer with a free pool; and

store, based on associating the first memory buffer with the free pool, a third plurality of the log records in the first memory buffer.

11. The device of claim 10, where the processor is further to:

store a mapping file of text message strings corresponding to a plurality of different message ID codes.

12. The device of claim 11,

where the first plurality of the log records are compact log records, and

where the processor is further to:

convert, using the mapping file, the compact log records to full log entries,

the full log entries including message ID codes and log messages; and

provide, for display, the full log entries on a graphic user interface (GUI).

13. The device of claim 12,

where the full log entries are provided, for display, on the GUI by time vs element ID for each thread, and

where the processor is further to:

provide a line on the GUI for errors.

14. The device of claim 10,

where the first plurality of the log records are compact log records, and

where the processor is further to:

convert the compact log records to full log entries utilizing a remote computer processor and a mapping file,

the mapping file including message ID codes and log messages; and

provide, for display, the full log entries on a graphic user interface (GUI).

15. The device of claim 14,

where the full log entries are provided, for display, on the GUI by time vs element ID for each thread, and

where the processor is further to:

provide a line on the GUI for errors.

16. A system comprising:

a device to;

receive log entries of events from a plurality of network elements,

the log entries being grouped by thread based on a particular purpose;

convert each log entry into a log record of log records,

each log record comprising at least one of;

information associated with a record length of the log record,

information associated with a time stamp of data collection at a network element of the plurality of network elements,

information associated with a thread ID of a thread that logged each event of the events,

information associated with a category of each event,

information associated with a message ID code corresponding to a log message, or

information associated with a network element ID for identifying a respective network element associated with each event;

store a first plurality of the log records in a first memory buffer to form a log file;

determine, based on an amount of data stored in the first memory buffer, that a second plurality of the log records should be stored in a second memory buffer;

queue, based on the amount of data stored in the first memory buffer, the first memory buffer to a background thread to write the first plurality of the log records to a disk file,

the background thread writing the first plurality of the log records to the disk file when one or more processing cycles are not needed by another thread that has a higher priority than the background thread;

associate, after the background thread writes the first plurality of the log records to the disk file, the first memory buffer with a free pool; and

store, based on associating the first memory buffer with the free pool, a third plurality of the log records in the first memory buffer.

17. The system of claim 16, where the device is further to:

store a mapping file of text message strings corresponding to a plurality of different message ID codes.

18. The system of claim 17,

where the first plurality of the log records are compact log records, and

where the device is further to:

convert, using the mapping file, the compact log records to full log entries,

the full log entries including message ID codes and log messages; and

provide, for display, the full log entries on a graphic user interface (GUI).

19. The system of claim 18,

where the full log entries are provided, for display, on the GUI by time vs element ID for each thread, and

where the device is further to:

provide a line on the GUI for errors.

20. The system of claim 16,

where the first plurality of the log records are compact log records, and

where the device is further to:

convert the compact log records to full log entries utilizing a remote computer processor and a mapping file,

the mapping file including message ID codes and log messages; and

provide, for display, the full log entries on a graphic user interface (GUI).