René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"New `logs` CLI command","articleBody":"**Motivation**\r\n\r\nExamining the Fibratus logs can be a hassle, especially if the end user is not familiar with Powershell. It would be much more convenient if the Fibratus CLI provided the facilities for grepping log files, filtering relevant log messages, etc.\r\n\r\n**Feature**\r\n\r\nExpand the Fibratus CLI with a new `logs` command. The command should ideally provide the following set of modifiers:\r\n\r\n- `-f`: tails the log file in realtime as the file gets written by the Fibratus process \r\n- `-n`: shows the last N lines of the log file\r\n- `-h`: shows the first N lines of the log file\r\n- `-l`: filters the log messages by the log level (debug, info, warning, and error)\r\n- `--grep`: accepts the Go-compatible regular expression and applies on each log line. If it produces any match, the log line is shown on the console.\r\n\r\nIf the command is run without any modifiers, the entire log file is read and dumped on the console.\r\n\r\nExamples:\r\n\r\nShow last 10 lines and watch for subsequent changes in realtime:\r\n\r\n```\r\n$ fibratus logs -n 10 -f\r\n```\r\n\r\nFilter logs by info level\r\n\r\n```\r\n$ fibratus logs -l info\r\n```\r\n\r\n**Additional context**\r\n\r\nFor watching the file changes in realtime, consider the usage of the [fsnotify](https://github.com/fsnotify/fsnotify) package.\r\n","author":{"url":"https://github.com/rabbitstack","@type":"Person","name":"rabbitstack"},"datePublished":"2024-12-13T18:01:30.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/410/fibratus/issues/410"}