Home

Awesome

JSON Log Viewer

Version Build Status Go Report Card Coverage Status

It is an interactive tool for viewing and analyzing complex structured json-log files.

Animation

Main features:

  1. It is interactive.
  2. It displays a compact list of log entries.
  3. It is possible to expand the log and see the full prettified JSON tree.
  4. All non-json logs are captured.
  5. Fields are customizable.
  6. Filtering is easy to use.
  7. Log levels are colorized.
  8. Transforming numeric timestamps.

It uses antonmedv/fx for viewing JSON records and charmbracelet/bubbletea for organizing the terminal UI. The tool is inspired by the project json-log-viewer which is unfortunately outdated and deserted.

The application is designed to help in visualization, navigation, and analyzing of JSON-formatted log data in a user-friendly and interactive manner. It provides a structured and organized view of the JSON logs, making it easier to comprehend the hierarchical nature of the data. It uses collapsible/expandable tree structures, indentation, and color-coded syntax to represent the JSON objects and arrays. It is possible to search for specific keywords, phrases, or patterns within the JSON logs. So it helps to significantly simplify the process of working with JSON logs, making it more intuitive and efficient. It is easy to troubleshoot issues, monitor system performance, or gain a deeper understanding of the application's behavior by analyzing its log data in post-mortem.

Table of content

Usage

Reading from file

jlv assets/example.log
jlv -config example.jlv.jsonc assets/example.log

Reading from Stdin

jlv < assets/example.log

Common applications:

curl https://raw.githubusercontent.com/hedhyw/json-log-viewer/main/assets/example.log | jlv

jlv << EOF
{"time":"1970-01-01T00:00:00.00","level":"INFO","message": "day 1"}
{"time":"1970-01-02T00:00:00.00","level":"INFO","message": "day 2"}
EOF

kubectl logs pod/POD_NAME -f | jlv
docker logs -f 000000000000 2>&1 | jlv

Hotkeys

KeyAction
EnterOpen log
EscBack
FFilter
RReverse
Ctrl+CExit
F10Exit
↑↓Line Up / Down
HomeNavigate to Start
EndNavigate to End

Attempting to navigate past the last line in the log will put you in follow mode.

Install

MacOS/Linux HomeBrew

brew install hedhyw/main/jlv
# jlv application.log

Package

Latest DEB and RPM packages are available on the releases page.

Standalone Binary

Download latest archive *.tar.gz for your target platform from the releases page and extract it to /usr/local/bin/jlv. Add this path to PATH environment.

Source

git clone git@github.com:hedhyw/json-log-viewer.git
cd json-log-viewer
make build
cp ./bin/jlv /usr/local/bin
chmod +x /usr/local/bin/jlv

# jlv application.log

Customization

The application will look for the config .jlv.jsonc in the working directory or in the home directory:

It's also possible to define the path to the configuration using "-config" flag.

The Json path supports the described in yalp/jsonpath syntax.

Example configuration: example.jlv.jsonc.

Time Formats

JSON Log Viewer can handle a variety of datetime formats when parsing your logs. The value is formatted by default in the "RFC3339" format. The format is configurable, see the time_format field in the config.

time

This will return the exact value that was set in the JSON document.

numerictime

This is a "smart" parser. It can accept an integer, a float, or a string. If it is numeric (1234443, 1234443.589, "1234443", "1234443.589"), based on the number of digits, it will parse as seconds, milliseconds, or microseconds. The output is a UTC-based RFC 3339 datetime.

If a string such as "2023-05-01T12:00:34Z" or "---" is used, the value will just be carried forward to your column.

If you find that the smart parsing is giving unwanted results or you need greater control over how a datetime is parsed, considered using one of the other time formats instead.

secondtime

This will attempt to parse the value as number of seconds and render as a UTC-based RFC 3339. Values accepted are integer, string, or float.

millitime

Similar to secondtime, this will attempt to parse the value as number of milliseconds. Values accepted are integer, string, or float.

microtime

Similar to secondtime and millistime, this will attempt to parse the value as number of microseconds. Values accepted are integer, string, or float.

Resources

Alternatives:

Contribution

Check open unassigned issues, write comments, ask questions, fork, and create a pull request.

License

MIT License.