2013-07-27 18:04:43 +00:00
|
|
|
|
2020-05-18 05:23:30 +00:00
|
|
|
.. _ui:
|
|
|
|
|
|
2013-07-27 18:04:43 +00:00
|
|
|
User Interface
|
|
|
|
|
==============
|
|
|
|
|
|
2013-08-26 14:20:01 +00:00
|
|
|
The main part of the display shows the log messages from all files sorted by the
|
|
|
|
|
message time. Status bars at the top and bottom of the screen can given you an
|
|
|
|
|
idea of where you are in the logs. And, the last line is used for entering
|
|
|
|
|
commands. Navigation is controlled by a series of hotkeys, see :ref:`hotkeys`
|
|
|
|
|
for more information.
|
2013-07-29 00:05:09 +00:00
|
|
|
|
2013-08-26 14:20:01 +00:00
|
|
|
.. figure:: lnav-ui.png
|
|
|
|
|
:align: center
|
|
|
|
|
:alt: Screenshot showing syslog messages.
|
|
|
|
|
|
|
|
|
|
Screenshot of **lnav** viewing syslog messages.
|
|
|
|
|
|
|
|
|
|
On color displays, the log messages will be highlighted as follows:
|
2013-07-29 00:05:09 +00:00
|
|
|
|
|
|
|
|
* Errors will be colored in red;
|
|
|
|
|
* warnings will be yellow;
|
2014-03-28 13:55:24 +00:00
|
|
|
* search hits are reverse video;
|
2013-07-29 00:05:09 +00:00
|
|
|
* various color highlights will be applied to: IP addresses, SQL keywords,
|
2013-08-26 14:20:01 +00:00
|
|
|
XML tags, file and line numbers in Java backtraces, and quoted strings;
|
|
|
|
|
* "identifiers" in the messages will be randomly assigned colors based on their
|
|
|
|
|
content (works best on "xterm-256color" terminals).
|
2013-07-29 00:05:09 +00:00
|
|
|
|
2013-08-26 14:20:01 +00:00
|
|
|
The right side of the display has a proportionally sized 'scrollbar' that
|
2014-03-28 13:55:24 +00:00
|
|
|
shows:
|
|
|
|
|
|
|
|
|
|
* your current position in the file;
|
|
|
|
|
* the locations of errors/warnings in the log files by using a red or yellow
|
|
|
|
|
coloring;
|
|
|
|
|
* the locations of search hits by using a tick-mark pointing to the left;
|
|
|
|
|
* the locations of bookmarks by using a tick-mark pointing to the right.
|
2013-07-29 00:05:09 +00:00
|
|
|
|
|
|
|
|
Above and below the main body are status lines that display:
|
|
|
|
|
|
|
|
|
|
* the current time;
|
|
|
|
|
* the name of the file the top line was pulled from;
|
|
|
|
|
* the log format for the top line;
|
|
|
|
|
* the current view;
|
|
|
|
|
* the line number for the top line in the display;
|
2019-02-05 15:30:57 +00:00
|
|
|
* the current search hit, the total number of hits, and the search term;
|
2018-11-11 06:55:08 +00:00
|
|
|
|
|
|
|
|
If the view supports filtering, there will be a status line showing the
|
|
|
|
|
following:
|
|
|
|
|
|
2020-05-07 14:08:59 +00:00
|
|
|
* the number of enabled filters and the total number of filters;
|
|
|
|
|
* the number of lines that are **not** displayed because of filtering.
|
2018-11-11 06:55:08 +00:00
|
|
|
|
|
|
|
|
To edit the filters, you can press TAB to change the focus from the main
|
|
|
|
|
view to the filter editor. The editor allows you to create, enable/disable,
|
|
|
|
|
and delete filters easily.
|
2013-07-29 00:05:09 +00:00
|
|
|
|
|
|
|
|
Finally, the last line on the display is where you can enter search
|
|
|
|
|
patterns and execute internal commands, such as converting a
|
|
|
|
|
unix-timestamp into a human-readable date. The command-line is by
|
|
|
|
|
the readline library, so the usual set of keyboard shortcuts can
|
|
|
|
|
be used.
|
|
|
|
|
|
|
|
|
|
The body of the display is also used to display other content, such
|
|
|
|
|
as: the help file, histograms of the log messages over time, and
|
|
|
|
|
SQL results. The views are organized into a stack so that any time
|
|
|
|
|
you activate a new view with a key press or command, the new view
|
|
|
|
|
is pushed onto the stack. Pressing the same key again will pop the
|
|
|
|
|
view off of the stack and return you to the previous view. Note
|
|
|
|
|
that you can always use 'q' to pop the top view off of the stack.
|
