Dev Tools: Integrate Logfile Navigator (lnav)

[Aharonee]

• Install lnav (Logfile Navigator) dependency and add custom format for logrus
• Reformat "Logging Starting" messages to be JSON instead of strings

Usage:

1. Install dependency and custom format by running ./scripts/configure_dev.sh
2. Open logfile by running lnav node.log

[codecov]

Codecov Report

Merging #5000 (f5aef89) into master (19fa6c2) will decrease coverage by 1.95%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #5000      +/-   ##
==========================================
- Coverage   53.65%   51.71%   -1.95%     
==========================================
  Files         432      432              
  Lines       54058    54058              
==========================================
- Hits        29007    27958    -1049     
- Misses      22805    23783     +978     
- Partials     2246     2317      +71     

Impacted Files	Coverage Δ
daemon/algod/server.go	4.62% <0.00%> (ø)

... and 103 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[cce]

I would prefer to see the logging started, telemetry enabled vs disabled, GUID/Session information show up in node.log, with some structure show up node.log, rather than remove it altogether

[algorandskiy]

node archive is missing

[Aharonee]

file-pattern is used to avoid potential conflicts when lnav chooses the file format to use.
I've replaced it with sample which defines some log line samples and uses them for conflict resolution instead (seems like this is the more common approach).

[bbroder-algo]

I am in favor of making the log entirely one object format.

[ahangsu]

let me second an approval, for it helps in reading the logs

[algorandskiy]

I'd prefer to see a some kind of lnav header as Chris suggested as well but LGTM

[winder]

Seems weird to print "Logging Started" in the log file.

Some better options:

• Write "Logging Started: " to stdout.
• Delete these lines.

Either way, definitely remove the ++++++++++++++++++++++++++++++++++++++++ banner.

[bbroder-algo]

+++ATH0

[excalq]

If I'm restarting a container, and tailing logs, it is helpful to see a clear location where the restart is obvious. But that said, it shouldn't deviate from the normal formatting expected by machine parsers, e.g. Filebeat.

[bbroder-algo]

Maybe, "algod process start"

[ahangsu]

+++ATH0

Is this https://support.usr.com/support/3cxm756/3cxm756-ug/atcoms.htm ?