Releases: tstack/lnav
Releases · tstack/lnav
v0.11.2
lnav v0.11.2
Features:
- A "cursor" mode has been added to the main view that can
be toggled by pressing CTRL-X. While in cursor mode, any
operations that would normally work on the "top" line will
now operate on the focused line instead. - Added CTRL-D and CTRL-U hotkeys to move down/up by half
a page. - Added an
auto-widthflag to the elements of the
line-formatarray that indicates that the width of the
field should automatically be determined by the observed
values. - Added bunyan log format from Tobias Gruetzmacher.
- Added cloudlare log format from @minusf.
- Number fields used in a JSON log format
line-format
array now default to being right-aligned. Also, added
prefixandsuffixtoline-formatelements so a
string can optionally be prepended/appended if the value
is not empty. - JSON log format detection has been improved to not rely
on matching the file name. All possible formats are
tried and the one with the most available fields for a
givenline-formatis used. For example, if the first
log message has 8 fields and format A contains 5 of
those fields in itsline-formatwhile format B only
contains 2 of those fields in itsline-format, format
A will be used for the file.
Changes:
- For JSON-lines logs, line-feeds at the end of a value are
automatically stripped.
Bug Fixes:
- Hidden values in JSON logs are now hidden by default.
- Text with ANSI-escapes is now filtered properly.
v0.11.2-rc6
lnav v0.11.2
Features:
- A "cursor" mode has been added to the main view that can
be toggled by pressing CTRL-X. While in cursor mode, any
operations that would normally work on the "top" line will
now operate on the focused line instead. - Added CTRL-D and CTRL-U hotkeys to move down/up by half
a page. - Added an
auto-widthflag to the elements of the
line-formatarray that indicates that the width of the
field should automatically be determined by the observed
values. - Added bunyan log format from Tobias Gruetzmacher.
- Added cloudlare log format from @minusf.
- Number fields used in a JSON log format
line-format
array now default to being right-aligned. Also, added
prefixandsuffixtoline-formatelements so a
string can optionally be prepended/appended if the value
is not empty. - JSON log format detection has been improved to not rely
on matching the file name. All possible formats are
tried and the one with the most available fields for a
givenline-formatis used. For example, if the first
log message has 8 fields and format A contains 5 of
those fields in itsline-formatwhile format B only
contains 2 of those fields in itsline-format, format
A will be used for the file.
Changes:
- For JSON-lines logs, line-feeds at the end of a value are
automatically stripped.
Bug Fixes:
- Hidden values in JSON logs are now hidden by default.
- Text with ANSI-escapes is now filtered properly.
v0.11.2-rc5
lnav v0.11.2
Features:
- A "cursor" mode has been added to the main view that can
be toggled by pressing CTRL-X. While in cursor mode, any
operations that would normally work on the "top" line will
now operate on the focused line instead. - Added CTRL-D and CTRL-U hotkeys to move down/up by half
a page. - Added an
auto-widthflag to the elements of the
line-formatarray that indicates that the width of the
field should automatically be determined by the observed
values. - Added bunyan log format from Tobias Gruetzmacher.
- Added cloudlare log format from @minusf.
- Number fields used in a JSON log format
line-format
array now default to being right-aligned. Also, added
prefixandsuffixtoline-formatelements so a
string can optionally be prepended/appended if the value
is not empty.
Changes:
- For JSON-lines logs, line-feeds at the end of a value are
automatically stripped.
Bug Fixes:
- Hidden values in JSON logs are now hidden by default.
- Text with ANSI-escapes is now filtered properly.
v0.11.2-rc3
lnav v0.11.2
Features:
- A "cursor" mode has been added to the main view that can
be toggled by pressing CTRL-X. While in cursor mode, any
operations that would normally work on the "top" line will
now operate on the focused line instead. - Added CTRL-D and CTRL-U hotkeys to move down/up by half
a page. - Added an
auto-widthflag to the elements of the
line-formatarray that indicates that the width of the
field should automatically be determined by the observed
values. - Added bunyan log format from Tobias Gruetzmacher.
- Number fields used in a JSON log format
line-format
array now default to being right-aligned. Also, added
prefixandsuffixtoline-formatelements so a
string can optionally be prepended/appended if the value
is not empty.
Bug Fixes:
- Hidden values in JSON logs are now hidden by default.
- Text with ANSI-escapes is now filtered properly.
v0.11.2-rc2
lnav v0.11.2
Features:
- A "cursor" mode has been added to the main view that can
be toggled by pressing CTRL-X. While in cursor mode, any
operations that would normally work on the "top" line will
now operate on the focused line instead. - Added CTRL-D and CTRL-U hotkeys to move down/up by half
a page. - Added an
auto-widthflag to the elements of the
line-formatarray that indicates that the width of the
field should automatically be determined by the observed
values. - Number fields used in a
line-formatnow default to
being right-aligned.
Bug Fixes:
- Hidden values in JSON logs are now hidden by default.
- Text with ANSI-escapes is now filtered properly.
v0.11.2-rc1
lnav v0.11.2
Features:
- A "cursor" mode has been added to the main view that can
be toggled by pressing CTRL-X. While in cursor mode, any
operations that would normally work on the "top" line now
operate on the selected line instead. - Added CTRL-D and CTRL-U hotkeys to move down/up by half
a page. - Added an
auto-widthflag to the elements of the
line-formatarray that indicates that the width of the
field should automatically be determined by the observed
values. - Number fields used in a
line-formatnow default to
being right-aligned.
Bug Fixes:
- Hidden values in JSON logs are now hidden by default.
- Text with ANSI-escapes is now filtered properly.
lnav v0.11.1
lnav v0.11.1
Features:
- Additional validation checks for log formats have been
added and will result in warnings. Pass-Won the
command-line to view the warnings. The following new
check have been added:- Each regex must have a corresponding sample log message
that it matches. - Each sample must be matched by only one regex.
- Each regex must have a corresponding sample log message
- Added built-in support for anonymizing content. The
:write-*commands now accept an--anonymizeoption
and there is ananonymize()SQL function. The
anonymization process will try to replace identifying
information with random data. For example, IPv4 addresses
are replaced with addresses in the 10.0.0.0/8 range.
(This feature is mainly intended to help with providing
information to lnav support that does not have sensitive
values.) - Added
parse_url()andunparse_url()SQL functions for
parsing URLs into a JSON object and then back again. Note
that the implementation relies on libcurl which has some
limitations, like not supporting all types of schemes
(e.g.mailto:). - Added the
subsecond-fieldandsubsecond-unitslog
format properties to allow for specifying a separate
field for the sub-second portion of a timestamp. - Added a keymap for Swedish keyboards.
Breaking changes:
- The
regexp_capture()table-valued-function now returns NULL
instead of an empty string for thecapture_namecolumn if
the capture is not named.
Fixes:
- Reduce the "no patterns have a capture" error to a warning
so that it doesn't block lnav from starting up. - Some ANSI escape sequences will now be removed before testing
regexes against a log message. - If a line in a JSON-lines log file does not start with a
{, it will now be shown as-is and will not have the JSON
parse error.
Cost of Doing Business:
- Migrated from pcre to pcre2.
lnav v0.11.1-rc1
lnav v0.11.1
Features:
- Additional validation checks for log formats have been
added and will result in warnings. Pass-Won the
command-line to view the warnings. The following new
check have been added:- Each regex must have a corresponding sample log message
that it matches. - Each sample must be matched by only one regex.
- Each regex must have a corresponding sample log message
- Added built-in support for anonymizing content. The
:write-*commands now accept an--anonymizeoption
and there is ananonymize()SQL function. The
anonymization process will try to replace identifying
information with random data. For example, IPv4 addresses
are replaced with addresses in the 10.0.0.0/8 range.
(This feature is mainly intended to help with providing
information to lnav support that does not have sensitive
values.) - Added
parse_url()andunparse_url()SQL functions for
parsing URLs into a JSON object and then back again. Note
that the implementation relies on libcurl which has some
limitations, like not supporting all types of schemes
(e.g.mailto:). - Added the
subsecond-fieldandsubsecond-unitslog
format properties to allow for specifying a separate
field for the sub-second portion of a timestamp. - Added a keymap for Swedish keyboards.
Breaking changes:
- The
regexp_capture()table-valued-function now returns NULL
instead of an empty string for thecapture_namecolumn if
the capture is not named.
Fixes:
- Reduce the "no patterns have a capture" error to a warning
so that it doesn't block lnav from starting up. - Some ANSI escape sequences will now be removed before testing
regexes against a log message. - If a line in a JSON-lines log file does not start with a
{, it will now be shown as-is and will not have the JSON
parse error.
Cost of Doing Business:
- Migrated from pcre to pcre2.
lnav v0.11.1-beta1
lnav v0.11.1
Features:
- Additional validation checks for log formats have been
added and will result in warnings. Pass-Won the
command-line to view the warnings. The following new
check have been added:- Each regex must have a corresponding sample log message
that it matches. - Each sample must be matched by only one regex.
- Each regex must have a corresponding sample log message
- Added built-in support for anonymizing content. The
:write-*commands now accept an--anonymizeoption
and there is ananonymize()SQL function. The
anonymization process will try to replace identifying
information with random data. For example, IPv4 addresses
are replaced with addresses in the 10.0.0.0/8 range.
(This feature is mainly intended to help with providing
information to lnav support that does not have sensitive
values.) - Added
parse_url()andunparse_url()SQL functions for
parsing URLs into a JSON object and then back again. Note
that the implementation relies on libcurl which has some
limitations, like not supporting all types of schemes
(e.g.mailto:).
Breaking changes:
- The
regexp_capture()table-valued-function now returns NULL
instead of an empty string for thecapture_namecolumn if
the capture is not named.
Fixes:
- Reduce the "no patterns have a capture" error to a warning
so that it doesn't block lnav from starting up. - Some ANSI escape sequences will now be removed before testing
regexes against a log message.
Cost of Doing Business:
- Migrated from pcre to pcre2.
lnav v0.11.1
lnav v0.11.1
Features:
- Additional validation checks for log formats have been
added and will result in warnings. Pass-Won the
command-line to view the warnings. The following new
check have been added:- Each regex must have a corresponding sample log message
that it matches. - Each sample must be matched by only one regex.
- Each regex must have a corresponding sample log message
- Added built-in support for anonymizing content. The
:write-*commands now accept an--anonymizeoption
and there is ananonymize()SQL function. The
anonymization process will try to replace identifying
information with random data. For example, IPv4 addresses
are replaced with addresses in the 10.0.0.0/8 range.
(This feature is mainly intended to help with providing
information to lnav support that does not have sensitive
values.) - Added
parse_url()andunparse_url()SQL functions for
parsing URLs into a JSON object and then back again. Note
that the implementation relies on libcurl which has some
limitations, like not supporting all types of schemes
(e.g.mailto:).
Breaking changes:
- The
regexp_capture()table-valued-function now returns NULL
instead of an empty string for thecapture_namecolumn if
the capture is not named.
Fixes:
- Reduce the "no patterns have a capture" error to a warning
so that it doesn't block lnav from starting up.
Cost of Doing Business:
- Migrated from pcre to pcre2.