Colorize JSON-structured log lines from stdin.
cor reads newline-delimited JSON log entries from stdin and prints colorized,
human-readable output to stdout. Non-JSON lines pass through unchanged.
$ echo '{"level":"info","ts":"2026-01-15T10:30:01.456Z","msg":"server started","host":"0.0.0.0","port":8080}' | cor
2026-01-15T10:30:01.456 INFO: server started
host: 0.0.0.0
port: 8080
Why "cor"? — Cor (pronounced /koɾ/) means "color" in Portuguese. Because naming a log colorizer "color" felt too obvious, we went with the version that sounds cooler and confuses spellcheckers.
cat logs.jsonl | cor
cat logs.jsonl | cor --level warn
cat logs.jsonl | cor -i method,path,status
cat logs.jsonl | cor -e func,query
cat logs.jsonl | cor --json --level error
cat logs.jsonl | cor --max-field-length 20
- Auto-detects fields from logrus, zap, slog, pino, bunyan, structlog, and more
- Embedded JSON — handles lines like
2026-01-15 10:30:00 {"level":"info",...} - Level filtering —
--level warnsuppresses debug and info - Numeric levels — bunyan/pino
30→info,40→warn, etc. - Custom keys —
--message-key,--level-key,--timestamp-key - Field filtering —
--include-fieldsor--exclude-fields - JSON passthrough —
--jsonoutputs filtered JSON for piping - Truncation — long values truncated at 120 chars (configurable)
- Line gap — configurable blank lines between entries (default: 1)
- Config file —
~/.config/cor/config.tomlfor persistent settings - NO_COLOR — respects no-color.org convention
- Fast — ~400K lines/sec, O(line-length) memory, streaming I/O
cargo install corgit clone https://github.com/alexsavio/cor-cli.git
cd cor-cli
cargo install --path .# Pipe any JSON log stream
my-app | cor
# Filter by level
kubectl logs my-pod | cor --level warn
# Custom keys
my-app | cor --message-key event --level-key severity
# Only show specific fields
my-app | cor --include-fields=host,port,status
# Hide noisy fields
my-app | cor --exclude-fields=pid,hostname
# Output filtered JSON (for piping)
my-app | cor --level error --json | jq .
# Disable truncation
my-app | cor --max-field-length=0
# Compact output (no blank lines between entries)
my-app | cor --line-gap=0
# Extra spacing between entries
my-app | cor --line-gap=3
# Force colors in pipes
my-app | cor --color=always | less -RYYYY-MM-DDTHH:MM:SS.mmm LEVEL: message
key: value
other_key: other_value
- Timestamp — bold
YYYY-MM-DDTHH:MM:SS.mmmin UTC - Level — colored and bold, right-justified in a 5-char field
- TRACE · DEBUG · INFO · WARN · ERROR · FATAL
- Message — plain text
- Extra fields — one per line, key right-justified to 25 chars, bold gray
These levels are recognized (case-insensitive, with aliases):
| Level | Aliases | Numeric (bunyan/pino) |
|---|---|---|
| TRACE | trace, trc |
10 |
| DEBUG | debug, dbg |
20 |
| INFO | info, inf, information |
30 |
| WARN | warn, warning, wrn |
40 |
| ERROR | error, err, fatal_error |
50 |
| FATAL | fatal, critical, crit, panic, emerg |
60 |
Custom level aliases can be defined in the config file.
cor scans for well-known field names used by popular logging frameworks:
| Field | Aliases |
|---|---|
| Timestamp | time, ts, timestamp, @timestamp, datetime, date, t |
| Level | level, severity, loglevel, log_level, lvl, priority |
| Message | msg, message, text, log, body, event, short_message |
CLI flags (--message-key, --level-key, --timestamp-key) override auto-detection.
Lines with a text prefix before JSON are detected automatically:
2026-01-15 10:30:00.123 {"level":"info","msg":"server started","port":8080}
[INFO] 2026-01-15T10:30:01Z {"level":"debug","msg":"config loaded"}
myapp | {"level":"warn","msg":"disk space low"}
The prefix is preserved in the output after the level badge.
Nested JSON objects are flattened using dot notation:
{"level":"info","msg":"req","http":{"method":"GET","status":200}}INFO: req
http.method: GET
http.status: 200
cor loads ~/.config/cor/config.toml (or $XDG_CONFIG_HOME/cor/config.toml) if present. CLI flags always take precedence.
# Default minimum level
level = "info"
# Color mode: auto, always, never
color = "auto"
# Timestamp display format (strftime)
timestamp_format = "%Y-%m-%dT%H:%M:%S%.3f"
# Max field value length (0 = unlimited)
max_field_length = 120
# Blank lines between entries (0 = compact)
line_gap = 1
# Examples of custom timestamp formats:
# timestamp_format = "%H:%M:%S%.3f" # time only with milliseconds
# timestamp_format = "%H:%M:%S" # time only, no milliseconds
# Override field key names
[keys]
message = "msg"
level = "level"
timestamp = "ts"
# Map custom level names → standard levels
[levels]
"verbose" = "debug"
"critical" = "fatal"
"success" = "info"| Variable | Effect |
|---|---|
NO_COLOR |
Disables colors when set (any non-empty value) |
FORCE_COLOR |
Enables colors even when not a TTY |
TERM=dumb |
Disables colors in auto mode |
--color=always and --color=never override all environment variables.
cor [OPTIONS]
Options:
-c, --color <COLOR> Color mode [default: auto] [values: auto, always, never]
-l, --level <LEVEL> Minimum severity level [values: trace, debug, info, warn, error, fatal]
-m, --message-key <KEY> Override message field key
--level-key <KEY> Override level field key
-t, --timestamp-key <KEY> Override timestamp field key
-i, --include-fields <FIELDS> Only show these fields (comma-separated)
-e, --exclude-fields <FIELDS> Hide these fields (comma-separated)
-j, --json Output raw JSON instead of colorized text
-M, --max-field-length <N> Max field value length [default: 120]
-g, --line-gap <N> Blank lines between entries [default: 1]
--config <PATH> Path to config file
-h, --help Print help
-V, --version Print version
MIT — Alexandre Savio





