Go to file
Ingo Oeser 25ae11ff27 Support basic auth
since many API services are behind authenticated endpoints
2015-07-08 10:45:28 +02:00
demo Updated screenshots 2015-05-03 21:09:27 +03:00
.gitignore gitignore change 2015-05-03 19:58:36 +03:00
README.md Fix typos in README.md 2015-05-03 18:34:42 -06:00
data.go Code cleanups 2015-05-01 20:12:23 +03:00
expvars.go Support basic auth 2015-07-08 10:45:28 +02:00
expvars.json Initial commit 2015-04-21 12:51:01 +03:00
expvars_advanced.json Refactoring 2015-04-25 15:54:17 +03:00
expvars_test.go Make go lint happy 2015-05-01 20:52:17 +03:00
main.go Print errors to stderr. Check interval flag for valid value 2015-05-04 16:33:48 -04:00
self.go Renamed self.go 2015-05-03 19:46:26 +03:00
service.go Added annotation 2015-05-12 12:50:25 +03:00
stack.go Added Max() functionality 2015-05-02 22:29:02 +03:00
stack_test.go Refactored ui_single 2015-05-03 18:03:49 +03:00
ui.go UI separated to multiple files 2015-05-03 16:52:50 +03:00
ui_dummy.go UI separated to multiple files 2015-05-03 16:52:50 +03:00
ui_multi.go Make golint happy 2015-05-03 21:59:45 +03:00
ui_single.go Make golint happy 2015-05-03 21:59:45 +03:00
utils.go Fixed ports parsing 2015-05-03 20:42:21 +03:00
utils_test.go Fixed ports parsing 2015-05-03 20:42:21 +03:00
var.go Comment 2015-05-03 19:04:17 +03:00
var_test.go Introduced kind: modifier 2015-05-02 10:12:38 +03:00

README.md

ExpvarMon

Build Status

TermUI based Go apps monitor using expvars variables (/debug/vars). Quickest way to monitor your Go app.

Introduction

Go apps console monitoring tool. Minimal configuration efforts. Quick and easy monitoring solution for one or multiple services.

Features

  • Single- and multi-apps mode
  • Local and remote apps support
  • Arbitrary number of apps and vars to monitor (from 1 to 30+, depends on size of your terminal)
  • Track restarted/failed apps
  • Show maximum value
  • Supports: Integer, float, duration, memory, string, bool variables
  • Sparkline charts for integer, duration and memory data
  • Auto-resize on font-size change or window resize
  • Uses amazing TermUI library by gizak

Demo

Multiple apps mode

Multi mode

Single app mode

Single mode

You can monitor arbitrary number of services and variables:

1 var 25 apps

Purpose

This app targets debug/develop sessions when you need an instant way to monitor you app(s). It's not intended to monitor apps in production. Also it doesn't use any storage engines and doesn't send notifications.

Install

Just run go get:

go get github.com/divan/expvarmon

Usage

Prepare your app

First, you have to add expvars support into your Go program. It's as simple as:

import _ "expvar"

and note the port your app is listening on. If it's not, just add two lines:

import "net/http"
...
http.ListenAndServe(":1234", nil)

and expvar will add handler for "localhost:1234/debug/vars" to your app.

By default, expvars adds two variables: memstats and cmdline. It's enough to monitor memory and garbage collector status in your app.

Run expvarmon

Just run expvarmon with -ports="1234" flag:

expvarmon -ports="1234"

That's it.

More examples:

./expvarmon -ports="80"
./expvarmon -ports="23000-23010,80" -i=1m
./expvarmon -ports="80,remoteapp:80" -vars="mem:memstats.Alloc,duration:Response.Mean,Counter"
./expvarmon -ports="1234-1236" -vars="Goroutines" -self

Advanced usage

If you need to monitor more (or less) vars, you can specify them with -vars command line flag.

$ expvarmon -help
Usage of ./expvarmon:
-dummy=false: Use dummy (console) output
-i=5s: Polling interval
-ports="": Ports for accessing services expvars (start-end,port2,port3)
-self=false: Monitor itself
-vars="mem:memstats.Alloc,mem:memstats.Sys,mem:memstats.HeapAlloc,mem:memstats.HeapInuse,memstats.EnableGC,memstats.NumGC,duration:memstats.PauseTotalNs": Vars to monitor (comma-separated)
Examples:
    ./expvarmon -ports="80"
    ./expvarmon -ports="23000-23010,80" -i=1m
    ./expvarmon -ports="80,remoteapp:80" -vars="mem:memstats.Alloc,duration:Response.Mean,Counter"
    ./expvarmon -ports="1234-1236" -vars="Goroutines" -self
For more details and docs, see README: http://github.com/divan/expvarmon

So, yes, you can specify multiple ports, using '-' for ranges, and specify host(s) for remote apps.

You can also monitor expvarmon itself, using -self flag.

Vars

Expvarmon doesn't restrict you to monitor only memstats. You can publish your own counters and variables using expvar.Publish() method or using expvar wrappers libraries. Just pass your variables names as they appear in JSON to -var command line flag.

Notation is dot-separated, for example: memstats.Alloc for .MemStats.Alloc field. Quick link to runtime.MemStats documentation: http://golang.org/pkg/runtime/#MemStats

Expvar allows to export only basic types - structs, ints, floats, bools and strings. Ints are used for sparklines, and displayed as is. But you can specify modifier to make sure it will be rendered properly.

Vars are specified as a comma-separated list of var identifiers with (optional) modifiers.

Modifier Description
mem: renders int64 as memory string (KB, MB, etc)
duration: renders int64 as time.Duration (1s, 2ms, 12h23h)
str: doesn't display sparklines chart for this value, just display as string

TODO

  • ports auto-discovery for given hostname
  • more tests coverage
  • better usage of color highlighting (for max values or failed apps), after relevant patches will be merged to TermUI