Tim Stack

Why did you close this?

Can you run lnav with `-d /tmp/lnav-dbg.log` and then attach that file, it might help in diagnosing the issue. From the screenshot, the "error.log" file might have some non-UTF-8 data,...

> By the way, How to use lnav on a remote server like tail -f /var/log/log.log | ssh root@remote "lnav" but remote lnav return failed error: stdout is not a...

Try passing `-t` to ssh to allocate a pty.

Can you run lnav with `-d /tmp/lnav-debug.log` and attach the generated debug file. Can you mention what OS you are using locally and what is on the remote? It kind...

It's because the timestamp of the log message is out-of-order with respect to the surrounding messages. When you scroll that message, it should show an overlay that mentions that, like...

Is there a service that outputs this format of JSON logs? If so, it can be added as a default format. > with regex stuff The format file for a...

@wsargent It looks like the log messages are not on a single line, is that right? Currently, lnav requires each JSON log message to be on a single line. So,...

> That’s kind of a problem given JSON can have variable formatting. I thought most/all JSON logs were line-oriented since not all JSON parsers can handle multiple JSON values. The...

> * Pretty printed JSON is a known logging format (logstash has both a json codec and a jsonlines codec, for example) It may be known, but jsonlines is going...