This article details how to set up a local AI assistant within a Linux terminal using Ollama and Llama 3.2. It explains the installation process, necessary shell configurations, and practical applications for troubleshooting and understanding system logs and processes. The author demonstrates how to use the AI to explain command outputs, interpret journal logs, and gain insights into disk usage and running processes, improving efficiency and understanding for both beginners and advanced Linux users. It also discusses the benefits and limitations of this approach.
This article details seven terminal-based tools – Gonzo, Lazyjournal, Toolong, Humanlog, GoAccess, Logrotate, and Logwatch – that can significantly improve the experience of working with logs for debugging, analysis, and management. It highlights how these tools offer interactive visualization, efficient navigation, and automated management to make log analysis more manageable and even enjoyable.
This Emacs major mode is designed for viewing the output from systemd’s journalctl within Emacs. It provides a convenient way to interact with journalctl logs, including features like fontification, chunked loading for performance, and custom keyword highlighting.
systemctl-tui is a fast, simple TUI for interacting with systemd services and their logs. It allows browsing service status, starting/stopping/restarting/reloading services, and viewing/editing unit files.
Linux log management can be a tricky process. This article guides you through best practices for managing logs on Linux systems.
Lnav is a log file viewer for large plain text files. It can handle files of any size and offers features like search, filter, and regex highlighting. It's built with C and supports Linux, macOS, and Unix systems.
View Apache requests per minute
Run the following command to see requests per minute:
grep "23/Jan/2013:06" example.com | cut -d -f2 | cut -d » -f1 | awk -F: '{print $2":"$3}' |
sort -nk1 -nk2 | uniq -c | awk '{ if ($1 > 10) print $0}'
Code breakdown:
Run the following command to see requests per minute:
grep "23/Jan/2013:06" example.com | cut -d -f2 | cut -d » -f1 | awk -F: '{print $2":"$3}' |
sort -nk1 -nk2 | uniq -c | awk '{ if ($1 > 10) print $0}'
Code breakdown:
questionable security in the script but the source of file list is interesting
