Another terminal based graphical activity monitor, inspired by gtop and vtop, this time written in Go!

Join us in #gotop:matrix.org (matrix clients).

Badges? We don't need no stinking badges!

See the change log for release updates.

Working and tested on Linux, FreeBSD and MacOS. Windows binaries are provided, but have limited testing. OpenBSD works with some caveats; cross-compiling is difficult and binaries are not provided.

If you install gotop by hand, or you download or create new layouts or colorschemes, you will need to put the layout files where gotop can find them. To see the list of directories gotop looks for files, run gotop -h. The first directory is always the directory from which gotop is run.

• Arch: Install from AUR, e.g. yay -S gotop-bin. There is also gotop and gotop-git
• Gentoo: gotop is available on guru overlay.

  sudo layman -a guru
  sudo emerge gotop

• Nix: you can run gotop with nix-shell -p gotop --run gotop or add the package gotop to your environment
• OSX: gotop is in homebrew-core. brew install gotop. Make sure to uninstall and untap any previous installations or taps.
• Windows: gotop is in the Main bucket. scoop install gotop.
• Prebuilt binaries: Binaries for most systems can be downloaded from the github releases page. RPM and DEB packages are also provided.
• Source: This requires Go >= 1.16. go install github.com/xxxserxxx/gotop/v4/cmd/gotop@latest

Extensions have proven problematic; go plugins are not usable in real-world cases, and the solution I had running for a while was hacky, at best. Consequently, extensions have been moved into the main code base for now.

• nvidia support: use the --nvidia flag to enable. You must have the nvidia-smi package installed, and gotop must be able to find the nvidia-smi executable, for this to work.
• remote: allows gotop to pull sensor data from applications exporting Prometheus metrics, including remote gotop instances themselves.

gotop requires a font that has braille and block character Unicode code points; some distributions do not provide this. In the gotop repository is a pcf font that has these points, and setting this font may improve how gotop renders in your console. To use this, run these commands:

curl -O -L https://raw.githubusercontent.com/xxxserxxx/gotop/master/fonts/Lat15-VGA16-braille.psf
setfont Lat15-VGA16-braille.psf

Sometimes libraries that gotop uses to introspect the hardware only support a subset of operating systems. Rather than cripple gotop to the LCD, I'm allowing features that may only work on some platforms. These will be listed here:

• nvidia -- only available on systems with an nvidia GPU
• SMART NVME hard drive temperatures -- Linux & Darwin

This is the download & compile approach.

gotop requires Go 1.16 or later to build, as it relies on the embed feature released with 1.16; a library it uses, lingo, uses both embed and the io/fs package. For a version of gotop that builds with earlier versions, check out one of the tags prior to v4.2.0.

git clone https://github.com/xxxserxxx/gotop.git
cd gotop
# This ugly SOB gets a usable version from the git tag list
VERS="$(git tag -l --sort=-v:refname | sed 's/v\([^-].*\)/\1/g' | head -1 | tr -d '-' ).$(git describe --long --tags | sed 's/\([^-].*\)-\([0-9]*\)-\(g.*\)/r\2.\3/g' | tr -d '-')"
DAT=$(date +%Y%m%dT%H%M%S)
go build -o gotop \
	-ldflags "-X main.Version=v${VERS} -X main.BuildDate=${DAT}" \
	./cmd/gotop

If you want to compact the executable as much as possible on Linux, change the ldflags line to this:

-ldflags "-X main.Version=v${VERS} -X main.BuildDate=${DAT} -extldflags '-s -w'" \

Now move the gotop executable to somewhere in your $PATH.

If Go is not installed or is the wrong version, and you don't have root access or don't want to upgrade Go, a script is provided to download Go and the gotop sources, compile gotop, and then clean up. See scripts/install_without_root.sh.

With Go 1.16, it is no longer necessary to call go generate. Translations and Apple SMC tags are embedded with go:embed.

Run with -h to get an extensive list of command line arguments. Many of these can be configured by creating a configuration file; see the next section for more information. Key bindings can be viewed while gotop is running by pressing the ? key, or they can be printed out by using the --list keys command.

In addition to the key bindings, the mouse can be used to control the process list:

• click to select process
• mouse wheel to scroll through processes

For more information on other topics, see:

• Layouts
• Configuration
• Color schemes
• Device filtering
• Extensions

gotop can monitor gotops running on remote machines and display (some of the) metrics within a single instance. gotop expects to be behind a proxy, or within a secure intranet, so while it's not exactly hard to set up, it's also not trivial. An example set-up is explained in the Remote Monitoring document.

Many people have contributed code to gotop. Most of the work was by the original author, Caleb Bassi, who was seduced by the dark side (Rust) and had to be thrown into a volcano. Thanks to everyone who's submitted a PR, or otherwise contributed to the project!

• gizak/termui
• nsf/termbox
• exrook/drawille-go
• shirou/gopsutil
• goreleaser/nfpm
• distatus/battery
• VictoriaMetrics/metrics Check this out! The API is clean, elegant, introduces many fewer indirect dependencies than the Prometheus client, and adds 50% less size to binaries.
• lingo is forked from jdkeke142's lingo, which was in turn forked from kortemy's original project.

ca. 2020-01-25 The original author of gotop started a new tool in Rust, called ytop, and deprecated his Go version. This repository is a fork of original gotop project with a new maintainer to keep the project alive and growing. An objective of the fork is to maintain a small, focused core while providing a path to extend functionality for less universal use cases; examples of this is sensor support for NVidia graphics cards, and for aggregating data from remote gotop instances.

I obviously think gotop is the Bee's Knees, but there are many alternatives. Many of these have been around for years. All of them are terminal-based tools.

• Grandpa top. Written 36 years ago, C, installed by default on almost every Unix descendant.
• bashtop, in pure bash! Beautiful and space efficient, and deserves special comment.
• bpytop, @aristocratos, the author of bashtop, rewrote it in Python in mid-2020; it's the same beautiful interface, and a very nice alternative.
• htop. A prettier top. Similar functionality. 16 years old!
• atop. Detailed process-focused inspection with a table-like view. Been around for 9 long years.
• iftop, a top for network connections. More than just data transfer, iftop will show what interfaces are connecting to what IP addresses. Requires root access to run.
• iotop, top for disk access. Tells you which processes are writing to and from disk space, and how much. Also requires root access to run.
• nmon a dashboard style top; widgets can be dynamically enabled and disabled, pure ASCII rendering, so it doesn't rely on fancy character sets to draw bars.
• ytop, a rewrite of gotop (ca. 3.0) in Rust. Same great UI, different programming language.
• slabtop, part of procps-ng, looks like top but provides kernel slab cache information! Requires root.
• systemd-cgtop, comes with systemd (odds are your system uses systemd, so this is already installed), provides a resource use view of control groups -- basically, which services are using what resources. Does not require root to run.
• virt-top top for virtualized containers (VMs, like QEMU).
• ctop top for containers (LXC, like docker)

In a chat room I heard someone refer to gotop as "another one of those fancy language rewrites people do." I'm not the original author of gotop, so it's easy to not take offense, but I'm going on record as saying that I disagree with that sentiment: I think these rewrites are valuable, useful, and healthy to the community. They increase software diversity at very little cost to users, and are a sort of evolutionary mechanism: as people do rewrites, some are worse, but some are better, and users benefit. Rewrites provide options, which fight against monocultures. As importantly, most developers are really only fluent in a couple of programming languages. We all have familiarity with a dozen, and may even have extensive experience with a half-dozen, but if you don't constantly use a language, you tend to forget the extended library APIs, your development environment isn't tuned, you're rusty with using the tool sets, and you may have forgotten a lot of the language peculiarities and gotchas. The barrier to entry for contributing to a software project -- to simply finding and fixing a bug -- in a language you're not intimate with can be very high. It gets much worse if the project owner is a stickler for a particular style. So I believe that gotop's original author's decision to rewrite his project in Rust is a net positive. He probably made fewer design mistakes in ytop (we always do, on the second rewrite), and Rust developers -- who may have hesitated learning or brushing up on Go to submit an improvement -- have another project to which they can contribute.

Diversity is good. Don't knock the free stuff.