Tail JSONL Logs
I wanted to find a tool that could:
- Convert a stream of JSONL logs into a readable
logfmt
-like output with minimal configuration - Show exceptions on their own line
I investigated a lot of alternatives such as: humanlog, lnav, goaccess, angle-grinder, jq, textualog, logss, etc. but nothing would both cleanly format the JSONL data and show the exception.
pipx install tail-jsonl
Pipe JSONL output from any file, kubernetes (such as stern), Docker, etc.
# Example piping input in shell
echo '{"message": "message", "timestamp": "2023-01-01T01:01:01.0123456Z", "level": "debug", "data": true, "more-data": [null, true, -123.123]}' | tail-jsonl
cat tests/data/logs.jsonl | tail-jsonl
# Optionally, pre-filter or format with jq, grep, awk, or other tools
cat tests/data/logs.jsonl | jq '.record' --compact-output | tail-jsonl
# An example stern command (also consider -o=extjson)
stern envvars --context staging --container gateway --since="60m" --output raw | tail-jsonl
# Or with Docker Compose (note that awk, cut, and grep all buffer. For awk, add '; system("")')
docker compose logs --follow | awk 'match($0, / \| \{.+/) { print substr($0, RSTART+3, RLENGTH); system("") }' | tail-jsonl
Optionally, specify a path to a custom configuration file. For an example configuration file see: ./tests/config_default.toml
echo '...' | tail-jsonl --config-path=~/.tail-jsonl.toml
See the Open Issues
and/or the CODE_TAG_SUMMARY. For release history, see the CHANGELOG.
We welcome pull requests! For your pull request to be accepted smoothly, we suggest that you first open a GitHub issue to discuss your idea. For resources on getting started with the code base, see the below documentation:
We follow the Contributor Covenant Code of Conduct.
We try to reasonably meet most aspects of the "OpenSSF scorecard" from Open Source Insights
If you have any security issue to report, please contact the project maintainers privately. You can reach us at [email protected].