Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Merge branch 'master' of github.com:spawnfest/beamspirit

  • Loading branch information...
commit 42c0b7f3495edfa27433618809d37f8c06e6c76b 2 parents 03d7b86 + 67ebcc2
Steven Gravell authored
Showing with 11 additions and 9 deletions.
  1. +11 −9 README
View
20 README
@@ -4,9 +4,9 @@ Tools that we currently include custom versions of:
* "etop" - see which processes are using the most cpu/heap/reds/etc
* "rb" - browse SASL reports
-* "appmon" - explore application supervision hierarchies
+* "appmon" - explore application supervision hierarchies
-Also included is a VM dashboard with release_handler details, loaded
+Also included is a VM dashboard with release_handler details, loaded
applications, and VM settings.
@@ -53,7 +53,7 @@ on nodes you wish to inspect.
Web Architecture
----------------
-We are using cowboy, with a combination of webservices that return JSON, and
+We are using cowboy, with a combination of webservices that return JSON, and
websockets to deliver realtime updates to the browser.
@@ -69,25 +69,27 @@ SASL Report Browsing
'rb' is for reading SASL reports written by the log_mf_h event handler which
SASL adds to the error_logger process. The on-disk format/writing looks like
it's been around long before disk_log wrapfiles were conceived, since it sort
-of does what you would nowadays use disk_log for.
+of does what you would nowadays use disk_log for.
-The rb module is designed to print text reports to stdout.
+The rb module is designed to print text reports to stdout.
The bigwig_report_loader module is our alternative to rb which loads the SASL
report terms from the file and returns them, which we subsequently convert to
-JSON and render client side. We also use the SASL-provided renderer code and
+JSON and render client side. We also use the SASL-provided renderer code and
send the familiar looking log format to the client too.
Would *love* to install our own handler that writes the reports as documents to
couch, or at the very least using disk_log, and with a better separation of
-loading the terms and rendering them. No time for this yet, and at least with
-our current approach we don't need people to install anything on nodes they
+loading the terms and rendering them. No time for this yet, and at least with
+our current approach we don't need people to install anything on nodes they
wish to examing using Bigwig.
eTop
----
-TODO write stuff here
+A web interface surfacing the information provided by etop with client-side
+sorting, introspection of pids and modules and the ability to pause and page
+through results.
AppMon
Please sign in to comment.
Something went wrong with that request. Please try again.