22## lnav v0.14.0
33
44Features:
5- * Log formats can now specify source file/line and thread
6- ID with the ` src-file-field ` , ` src-line-field ` , and
7- ` thread-id-field ` properties. These fields can then be
8- accessed in the SQL vtables as ` log_src_file ` ,
9- ` log_src_line ` , and ` log_thread_id ` .
5+ * Introducing "Log-Oriented Debugging", a collection of
6+ features to streamline mapping log messages back to
7+ the source code that generated them. For example,
8+ given the log message "Hello, Steve!" and the source
9+ directory containing the log statement. lnav can
10+ find the line of code that generated the message,
11+ such as ` logging.info("Hello, %s!", name) ` , and
12+ determine the value of the substituted variables
13+ (` name ` => ` Steve ` ). This functionality is
14+ implemented using the
15+ [ log2src] ( https://github.com/ttiimm/log2src ) project.
16+ The following features have been added in support of
17+ this functionality:
18+ - The ` :add-source-path ` command was added to specify
19+ the source directories to be scanned for log
20+ statements.
21+ - Log formats can now specify source file/line and
22+ thread ID with the ` src-file-field ` , ` src-line-field ` ,
23+ and ` thread-id-field ` properties. These fields can
24+ then be accessed in the SQL vtables as ` log_src_file ` ,
25+ ` log_src_line ` , and ` log_thread_id ` .
26+ - The ` :breakpoint ` , ` :toggle-breakpoint ` , and
27+ ` :clear-breakpoints ` commands have been added to
28+ support setting/clearing breakpoints for log messages.
29+ The ` CTRL-B ` shortcut toggles a breakpoint on the
30+ focused line in the LOG view. Also, if the log
31+ format specifies source file/line fields, the first
32+ character of the source file will be underlined and
33+ can be clicked to toggle a breakpoint. Once
34+ breakpoints have been added, you can press ` F7 ` /` F8 `
35+ to move to the previous/next log message that
36+ matches a breakpoint.
1037* The ` all_opids ` and ` all_thread_ids ` virtual tables
1138 have been added to make it simple to discover all of
1239 the operations and threads across all log files.
@@ -28,21 +55,17 @@ Features:
2855 - The ` prefers ` property is a regular expression that
2956 will be tested against the full path to be opened.
3057 If matched, that editor will be chosen.
31- * The ` :breakpoint ` , ` :toggle-breakpoint ` , and
32- ` :clear-breakpoints ` commands have been added to support
33- setting/clearing breakpoints for log messages. The
34- ` CTRL-B ` shortcut toggles a breakpoint on the focused
35- line in the LOG view. Also, if the log format specifies
36- source file/line fields, the first character of the
37- source file will be underlined and can be clicked to
38- toggle a breakpoint. Once breakpoints have been added,
39- you can press ` F7 ` /` F8 ` to move to the previous/next log
40- message that matches a breakpoint.
4158* The ` :external-access ` command has been added to open a
4259 localhost HTTP port that can be used to remotely control
4360 lnav. Requests can be sent to execute commands and poll
4461 for changes in the view state.
4562
63+ Interface changes:
64+ * If there are background tasks, like the processing done
65+ by ` :add-source-path ` , a panel with progress bars for
66+ each operation will be shown just above the bottom
67+ status bar.
68+
4669## lnav v0.13.2
4770
4871Bug Fixes:
0 commit comments