Skip to content
A top-like tool for monitoring an Erlang node
Branch: master
Clone or download
Pull request Compare This branch is 9 commits ahead, 34 commits behind mazenharake:master.
zaa Merge pull request #1 from systra/master
Add missing property for systools
Latest commit 67e6dc6 Jul 29, 2016
Type Name Latest commit message Commit time
Failed to load latest commit information.
ebin Add missing property for systools Jul 22, 2016
.gitignore Use rebar deps to pull cecho Feb 1, 2011
LICENSE Changed the license to Apache License. Please see the file LICENSE. The Aug 20, 2010
NOTICE Changed the license to Apache License. Please see the file LICENSE. The Aug 20, 2010 README update Feb 26, 2012
entop Fixes issue 4: entop does not use Erlang cookie properly mazenharake#4 Oct 7, 2011
rebar Update rebar version, remove Makefile and use only rebar. Feb 25, 2012
rebar.config Switch back to original cecho repo Jul 26, 2016


A top-like Erlang node monitoring tool


Entop is a tool which shows information about a remote Erlang node in a way which is similar to unix 'top'.

For entop to run it needs cecho 0.3.0 or higher for pre-R15 or cecho 0.4.0 or higher for R15 and above (


To clean/compile run

./rebar clean
./rebar compile

NOTE: If you have problems with dependencies to cecho then create a symlink to cecho in deps/ (if you already have cecho somewhere) or run ./rebar get-deps to download the latest version. Don't forget to recompile if you get the dependencies through rebar.


To run entop make sure you have Erlang installed and that the cecho library ( is available in your Erlang code path. The start script assumes that you run it inside the entop application root directory, if you don't want that then change the paths in the scripts accordingly or just make sure you have the ebin/ directory for entop in your Erlang code path. Look at the start script for more details.

Usage: ./entop <TARGETNODE> [-name <NAME>|-sname <SNAME>] [-setcookie <COOKIE>]

An example of how you run entop:

> ./entop foo@ -name entop@ -setcookie secret

User Interface:

entop's interface can be customized so this section only applies for the "built-in" interface.


First row shows information about the node which is more or less static such as the node name the operating system, erl flags and erlang version it is running.
The second row shows information on what the local time is (according to the node), how long it has been up for (Days:Hours:Minutes:Seconds) and how much latency there is to the node I.e. how long a net_adm:ping() takes.
Third row shows information about the processes of the system; the total number of processes, the run queue (number of processes scheduled to run by the scheduler(s)), the reductions per interval (RpI) which shows how many reductions the system has made since it last called the node and how much memory the processes are using.
Fourth row shows how much system memory, atom memory (currently used/total allocated), binary memory, code memory and ets memory.
Fifth row is left blank and is reserved for now.
Sixth row shows information about the rows in the list such as the interval in which the information is fetched, what the list is sorted on and how long it took to retrieve the information.

Commands when running entop:

[1-N]: Sort on column number 1 through N. Starts with first column (1) and up to N where N is the last column.

r: Toggles the sorting order from ascending to descending and vice versa.

q: Quits entop and return to the shell.

Ctrl-C: Same as 'q'.

'<' and '>': Moves the sorting column to the left or right respectively (these are the lower/greater-than-tags; not arrow keys).


Should you find yourself using entop and have issues, comments or feedback please [create an issue!] 1

You can’t perform that action at this time.