json-log-viewer

KO | EN

gitlite — search

#react #llm #go #golang #machine-learning #linux #docker #macos #java #cli #awesome-list #security #mcp #open-source

json-log-viewer

(★ 265)

Powerful terminal based viewer for JSON logs using ncurses.

파일 탐색기

최종 버전 다운로드 (.zip)

- - BaseWidget.js
  - LogDetails.js
  - MainPanel.js
  - Picker.js
  - StatusLine.js
- index.js
- log.js
- polyfills.js
- utils.js
- - broken.log
  - monolog.log.json
  - transform1.ini
  - workflow-engine.log.2017-09-25
- - fixtures.js
  - test-helper.js
- browser.test.js
- log.test.js
- utils.test.js
.eslintignore
.eslintrc
.gitignore
package-lock.json
package.json
README.md
screenshot.png
screenshot1.png
screenshot2.png
screenshot3.png
transform.png
yarn.lock

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# json-log-viewer

[![npm version](https://badge.fury.io/js/json-log-viewer.svg)](https://badge.fury.io/js/json-log-viewer)

> Powerful terminal based viewer for JSON logs using ncurses.

![screenshot](https://raw.githubusercontent.com/gistia/json-log-viewer/master/screenshot.png)

**json-log-viewer** is a feature intensive viewer and analyze tool for JSON logs created by libraries like [https://github.com/winstonjs/winston](winston).

Features:

- completely operated by hotkeys
- powerful command line arguments
- sort by timestamp, level or message
- filter by any field or metadata
- search

Hotkeys:

- `arrows` and `page up/down` to move
- `/` to search
- `n` to search again
- `s` to sort
- `f` to filter
- `l` to filter by level
- `g` to go to line
- `0` to go to first line
- `$` to go to last line
- `q` to quit

## Install

```bash
npm install --global json-log-viewer
```

## Usage

```bash
jv application.log.2017-01-01 --sort -timestamp
```

### Configuration

The default expected log format include fields `timestamp`, `level` and `message`. If the log file you're trying to parse doesn't include those fields, you can create a config file on your HOME path called `.json-log-viewer`.

For example, if your log lines look like this:

```json
{
  "message":
    "Matched route \"**_heartbeat_check\" (parameters: \"_controller\": \"**\\Controller\\**Controller::heartbeatCheckAction\", \"_route\": \"**_heartbeat_check\")",
  "context": [],
  "level": 200,
  "level_name": "INFO",
  "channel": "request",
  "datetime": {
    "date": "2017-12-06 09:23:42.253060",
    "timezone_type": 3,
    "timezone": "Europe/Berlin"
  },
  "extra": []
}
```

You can create a mapping configuration like this:

```ini
[transform]
level=level_name
timestamp=datetime.date
message=message
extra=$
```

This way the messages will properly be displayed. The `$` has a special meaning: it tells the the old object should be included on the `extra` key on the resulting JSON. The result will look like this:

![transform](https://raw.githubusercontent.com/gistia/json-log-viewer/master/transform.png)

## Screenshots

__Details view__

![screenshot](https://raw.githubusercontent.com/gistia/json-log-viewer/master/screenshot1.png)

__Filters__

![screenshot](https://raw.githubusercontent.com/gistia/json-log-viewer/master/screenshot2.png)

__Log level selection__

![screenshot](https://raw.githubusercontent.com/gistia/json-log-viewer/master/screenshot3.png)

## License

[MIT](http://vjpr.mit-license.org)

json-log-viewer

파일 탐색기

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

json-log-viewer

파일 탐색기

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README