| > But if some log message uses an attribute you haven't anticipated in the format definition, there's no way to see it in the pretty-printed output Properties in the log message that are not in the "line-format" are displayed below the message as key-value pairs. As an example, the bunyan[1] log format[2] has a few standard properties that are used in the "line-format" to form the main message. Then, as shown in this test[3] for this log[4], the remaining properties (even ones not mentioned in the format file) are shown underneath. > or filter on it in the UI Since they are part of the message as mentioned above, they can be filtered on. > and no ability to see it in the SQLite virtual table. The "log_raw_text" column in the table can be used to access the original log message from the file. So, you can use the JSON functions in SQLite to retrieve the value: ;SELECT log_raw_text ->> '$.repository' from bunyan
[1] - https://github.com/trentm/node-bunyan[2] - https://github.com/tstack/lnav/blob/master/src/formats/bunya... [3] - https://github.com/tstack/lnav/blob/master/test/expected/tes... [4] - https://github.com/tstack/lnav/blob/master/test/logfile_buny... |