Check GitHub releases for Windows installers and Linux/Mac packages.
Development status
Klogg is a multi-platform GUI application that helps browse and search through long and complex log files. It is designed with programmers and system administrators in mind and can be seen as a graphical, interactive combination of grep, less, and tail.
Please refer to the documentation page for how to use Klogg.
Windows | Linux | Mac |
---|---|---|
continuous-win | continuous-linux | continuous-osx |
I try to keep a changelog with monthly changes.
Klogg started as a fork of glogg - the fast, smart log explorer in 2016.
Since then it has evolved from fixing small annoying bugs to rewriting core components to make it faster and smarter that predecessor.
Development of klogg is driven by features my colleagues and I need to stay productive as well as feature requests from users on Github and in glogg mailing list.
Latest news about klogg development can be found at https://klogg.filimonov.dev.
Klogg has all best features of glogg:
And on top of that klogg:
Here is a small demo showing how much faster klogg is (searching in ~1Gb file stored on tmpfs):
https://user-images.githubusercontent.com/1620716/117588567-bea39100-b12c-11eb-990a-90a667bcaeaa.mp4
List of glogg issues that have been fixed/implemented in klogg can be found here.
List of all changes can be found here.
This project uses Calendar Versioning. For a list of available versions, see the repository tag list.
Binaries for all platforms can be downloaded from GitHub releases.
Windows installer is also available from:
Package for Mac can be installed from Homebrew
It is recommended to use klogg package from distribution-specific repositories.
Generic packages are available from klogg DEB and RPM repositories hosted at GitHub Pages. They are built to run on Ubuntu 18.04/20.04/22.04 and Oracle Linux 7/8 (x86-64 only).
For DEB packages first download the gpg key:
curl -sS https://klogg.filimonov.dev/klogg.gpg.key | gpg --dearmor | sudo tee /etc/apt/keyrings/klogg.gpg
You might need to manually create /etc/apt/keyrings
directory.
Then download the repository list file for you distribution (replace <ubuntu_release>
with one of bionic
, focal
, jammy
):
curl -sS https://klogg.filimonov.dev/deb/klogg.<ubuntu_release>.list | sudo tee /etc/apt/sources.list.d/klogg.list
Finally, install using apt
sudo apt-get update
sudo apt install klogg
If there is already an entry for JFrogg hosted klogg repository in /etc/apt/sources.list
, then remove this line from it:
deb [trusted=yes] https://favpackage.jfrog.io/artifactory/klogg_deb/ <ubuntu_release> utils
For RPM download klogg repo file (replace <oracle_release>
with one of 7
, 8
):
curl -sS https://klogg.filimonov.dev/rpm/klogg-oracle-<oracle_release>.repo | sudo tee /etc/yum.repos.d/klogg-rpm.repo
Then install using yum
sudo yum update
sudo yum install klogg
There is also an AppImage package that can be used without installation. To run klogg from AppImage, download the package and make in executable with either a file manager or terminal command chmod +x <path_to_klogg_AppImage>
and then run the AppImage file.
AppImage uses FUSE2 and Ubuntu 22.04 has moved away from FUSE2 into FUSE3 and therefore you need to install the necessary package to enable compatibility with FUSE2 sudo apt install libfuse2
.
As indicated by this link from the official appimage documentation: https://docs.appimage.org/user-guide/troubleshooting/fuse.html#setting-up-fuse-2-x-alongside-of-fuse-3-x-on-recent-ubuntu-22-04-debian-and-their-derivatives
Windows | Linux | Mac |
---|---|---|
continuous-win | continuous-linux | continuous-osx |
Please review BUILD.md for how to setup Klogg on your local machine for development and testing purposes.
First, please refer to the documentation page.
You can open issues using klogg issues page or post questions to glogg development mailing list.
We encourage public contributions! Please review CONTRIBUTING.md for details on our code of conduct and development process.
This project is licensed under the GPLv3 or later - see COPYING file for details.
See also the list of contributors who participated in this project.