Trendshift - Ask AI

base on 🌀 A log file highlighter <img src="assets/tailspin.png" width="230"/> # A log file highlighter <img src="assets/main.png" width="700"/> ### Features - 🪵 View (or `tail`) any log file of any format - 🍰 No setup or config required - 🌈 Highlights numbers, dates, IP-addresses, UUIDs, URLs and more - ⚙️ All highlight groups are customizable - 🧬 Easy to integrate with other commands - 🔍 Uses `less` under the hood - 📦 Powered by the [`manifold`](https://github.com/bensadeh/manifold) crate # ### Table of Contents * [Overview](#overview) * [Usage](#usage) * [Installing](#installing) * [Highlight Groups](#highlight-groups) * [Watching folders](#watching-folders) * [Customizing Highlight Groups](#customizing-highlight-groups) * [Working with `stdin` and `stdout`](#working-with-stdin-and-stdout) * [Using the pager `less`](#using-the-pager-less) * [Settings](#settings) *** ## Overview `tailspin` works by reading through a log file line by line, running a series of regexes against each line. The regexes recognize patterns you expect to find in a logfile, like dates, numbers, severity keywords and more. `tailspin` does not make any assumptions on the format or position of the items it wants to highlight. For this reason, it requires no configuration and the highlighting will work consistently across different logfiles. ## Usage The binary name for `tailspin` is `tspin`. ```console # Read from file and view in `less` tspin application.log # Read from file and print to stdout tspin application.log --print # Read from stdin and print to stdout kubectl logs [pod name] --follow | tspin # Capture the stdout of another command and view in `less` tspin --listen-command 'kubectl logs -f pod_name' ``` ## Installing ### Package Managers ```console # Homebrew brew install tailspin # Cargo cargo install tailspin # Archlinux pacman -S tailspin # Nix nix-shell -p tailspin # NetBSD pkgin install tailspin # FreeBSD pkg install tailspin ``` ### From Source ```console cargo install --path . ``` Binary will be placed in `~/.cargo/bin`, make sure you add the folder to your `PATH` environment variable. > [!IMPORTANT] > When building from source, make sure that you are using the latest version > of [`less`](http://greenwoodsoftware.com/less/). ## Highlight Groups ### Dates <img src="assets/examples/dates.png" width="600"/> ### Keywords <img src="assets/examples/keywords.png" width="600"/> ### URLs <img src="assets/examples/urls.png" width="600"/> ### Numbers <img src="assets/examples/numbers.png" width="600"/> ### IP Addresses <img src="assets/examples/ip.png" width="600"/> ### Quotes <img src="assets/examples/quotes.png" width="600"/> ### Unix file paths <img src="assets/examples/paths.png" width="600"/> ### HTTP methods <img src="assets/examples/http.png" width="600"/> ### UUIDs <img src="assets/examples/uuids.png" width="600"/> ### Key-value pairs <img src="assets/examples/kv.png" width="600"/> ### Pointer addresses <img src="assets/examples/pointers.png" width="600"/> ### Unix processes <img src="assets/examples/processes.png" width="600"/> ## Watching folders `tailspin` can listen for newline entries in a given folder. Watching folders is useful for monitoring log files that are rotated. <img src="assets/examples/folder.png" width="600"/> When watching folders, `tailspin` will start in follow mode (abort with <kbd>Ctrl + C</kbd>) and will only print newline entries which arrive after the initial start. ## Customizing Highlight Groups ### Overview Create a `theme.toml` in `~/.config/tailspin` to customize highlight groups. Styles have the following shape: ```toml style = { fg = "color", bg = "color", italic = false, bold = false, underline = false } ``` To edit the different highlight groups, include them in your `theme.toml` file. For example, to edit the `date` highlight group, add the following to your `theme.toml`: ```toml [date] style = { fg = "green" } ``` Expand the section below to see the default config for the highlight groups: <details> <summary>Default highlight groups settings</summary> ```toml [date] date = { fg = "magenta" } time = { fg = "blue" } zone = { fg = "red" } separator = { faint = true } [[keywords]] words = ['null', 'true', 'false'] style = { fg = "red", italic = true } [[keywords]] words = ['GET'] style = { fg = "black", bg = "green" } [url] http = { fg = "red", faint = true } https = { fg = "green", faint = true } host = { fg = "blue", faint = true } path = { fg = "blue" } query_params_key = { fg = "magenta" } query_params_value = { fg = "cyan" } symbols = { fg = "red" } [number] style = { fg = "cyan" } [ip] number = { fg = "blue", italic = true } letter = { fg = "magenta", italic = true } separator = { fg = "red" } [quotes] style = { fg = "yellow" } token = '"' [path] segment = { fg = "green", italic = true } separator = { fg = "yellow" } [uuid] number = { fg = "blue", italic = true } letter = { fg = "magenta", italic = true } separator = { fg = "red" } [pointer] number = { fg = "blue", italic = true } letter = { fg = "magenta", italic = true } separator = { fg = "red" } [key_value] key = { faint = true } separator = { fg = "white" } [process] name = { fg = "green" } separator = { fg = "red" } id = { fg = "yellow" } [json] key = { fg = "yellow" } quote_token = { fg = "yellow", faint = true } curly_bracket = { faint = true } square_bracket = { faint = true } comma = { faint = true } colon = { faint = true } ``` </details> ### Disabling Highlight Groups To individually disable or enable highlight groups, use the `--enable` and `--disable` flags: ```console # Enable only the url highlight group, disabling the rest tspin application.log --enable=url # Disable the numbers highlight group, keeping the rest tspin application.log --disable=numbers ``` ### Adding Keywords via theme.toml To add custom keywords, either include them in the list of keywords or add new entries: ```toml [[keywords]] words = ['MyCustomKeyword'] style = { fg = "green" } [[keywords]] words = ['null', 'true', 'false'] style = { fg = "red", italic = true } ``` ### Adding Keywords from the command line Sometimes it is more convenient to add highlight groups on the fly without having to edit a TOML. To add highlights from the command line, use the `--words-[red|green|yellow|blue|magenta|cyan]` flag followed by a comma separated list of words to be highlighted. <img src="assets/examples/otf.png" width="800"/> ### Custom regex highlighters When you need more control over the highlighting, you can use the regex highlighter. This highlighter allows you to specify a regex and a style to be applied to the matched text. It supports one capture group `()`. When found, it will apply the style to the captured text. ```toml [[regexps]] regex = 'Started (.*)\.' style = { fg = "red" } ``` ## Working with `stdin` and `stdout` ### Default behavior with pipes By default, `tailspin` will open a file in the pager `less`. However, if you pipe something into `tailspin`, it will print the highlighted output directly to `stdout`. This is similar to running `tspin [file] --print`. To let `tailspin` highlight the logs of different commands, you can pipe the output of those commands into `tailspin` like so: ```console journalctl -f | tspin cat /var/log/syslog | tspin kubectl logs -f pod_name | tspin ``` ### Capturing the output of a command and viewing it in `less` To capture the output of a command and view it in `less`, use the `--listen-command` flag: ```console tspin --listen-command 'kubectl logs -f pod_name' ``` This will run the command `kubectl logs -f pod_name` in the background and pipe the output to `tailspin`. The output will be displayed in `less`, allowing you to navigate and search through the logs. ## Using the pager `less` ### Overview `tailspin` uses `less` as its pager to view the highlighted log files. You can get more info on `less` via the **man** command (`man less`) or by hitting the <kbd>h</kbd> button to access the help screen. ### Navigating Navigating within `less` uses a set of keybindings that may be familiar to users of `vim` or other `vi`-like editors. Here's a brief overview of the most useful navigation commands: - <kbd>j</kbd>/<kbd>k</kbd>: Scroll one line up / down - <kbd>d</kbd>/<kbd>u</kbd>: Scroll one half-page up / down - <kbd>g</kbd>/<kbd>G</kbd>: Go to the top / bottom of the file ### Follow mode When you run `tailspin` with the `-f` or `--follow` flag, it will scroll to the bottom and print new lines to the screen as they're added to the file. To stop following the file, interrupt with <kbd>Ctrl + C</kbd>. This will stop the tailing, but keep the file open, allowing you to review the existing content. To resume following the file from within `less`, press <kbd>Shift + F</kbd>. ### Search Use <kbd>/</kbd> followed by your search query. For example, `/ERROR` finds the first occurrence of **ERROR**. After the search, <kbd>n</kbd> finds the next instance, and <kbd>N</kbd> finds the previous instance. ### Filtering `less` allows filtering lines by a keyword, using <kbd>&</kbd> followed by the pattern. For instance, `&ERROR` shows only lines with **ERROR**. To only show lines containing either `ERROR` or `WARN`, use a regular expression: `&\(ERROR\|WARN\)`. To clear the filter, use <kbd>&</kbd> with no pattern. ## Settings ```console -f, --follow Follow the contents of the file -e, --start-at-end Start at the end of the file -p, --print Print the output to stdout -c, --listen-command '[CMD]' Listen the output (stdout) of the provided command --config-path [PATH] Use the configuration file from the provided path --words-[COLOR] [WORDS] Highlight the provided words with the given color --no-builtin-keywords Disable the highlighting of booleans, nulls, log severities and common REST verbs --enable=[HIGHLIGHT_GROUP] Enable one or more highlight groups, disabling the rest --disable=[HIGHLIGHT_GROUP] Disable one or more highlight groups, enabling the rest ``` ", Assign "at most 3 tags" to the expected json: {"id":"4497","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"

AI prompts

AI prompts