Skip to content

parser details usability for JSON logs #1682

@tstack

Description

@tstack

The parser details (opened by pressing p) is not very usable for JSON logs that contain a lot of data. The current design is geared towards writing SQL, but that's probably not necessary anymore with the new prompt code. Instead we should focus on drilling into the raw log message object tree, like jless / fx. So, instead of jget(...), it should show the hierarchy and support folding subtrees. Pressing / should start a search in the overlay and n/N should move forwards/backwards. Pressing c should copy the value and maybe pressing C should copy the JSON-path.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions