Simple process monitoring in Go
Switch branches/tags
Nothing to show
Clone or download
ksred Merge pull request #1 from myles-mcdonnell/mm_recon
Added godeps and go report card badge to readme
Latest commit 2287e26 Apr 25, 2017
Type Name Latest commit message Commit time
Failed to load latest commit information.
Godeps Added godeps and go report card badge to readme Apr 3, 2017
.gitignore Added godeps and go report card badge to readme Apr 3, 2017 Added godeps and go report card badge to readme Apr 3, 2017
init Renamed to go-monitor Jul 9, 2016 Added install script Jul 9, 2016
main_test.go Created configFile flag "f" Apr 24, 2017

Go Report Card

Simple server monitoring in Go

go-monitor is simple server monitoring written in Go. I was on the lookout for a tool which allowed me to monitor a list of services and notify me through SMS or email. Everything I found seemed a bit too complex and so go-monitor was born.


go-monitor monitors a list of services as specified by the user and then notifies one or more users through SMS of any services that are down.

We use MessageBird as an SMS delivery service. SMS can be exchanged for a number of other services through MessageBird.

Config is read through a yaml file. Users can specify how often they are notified of a given service being down through the defaultttl value in the config.

By default, processes are checked every 60 seconds. This can be increased or decreased depending on the importance of services.

This program is intended for use on Unix systems.


  1. go get

  2. Install dependencies: godep restore (If you are unfamiliar with Godeop see here)

  3. Update go-monitor.yml.sample to include the configuration options desired.

  4. Rename config to go-monitor.yml.

  5. bash will build the program and add it as a service.

How it works

We use a Go to push this onto the server:

ps aux | grep PROCESS_NAME

We then read the number of lines returned. Super simple.


Down the line it would be nice to have server monitoring in addition to process monitoring:

  • CPU
  • Disks (usage, read/write)
  • Memory

This could further be extended into network monitoring. Someday.