Skip to content
Lifeguard is a highly scalable, fault tolerant distributed infrastructure and application monitoring service.
JavaScript Erlang Shell
Find file
Latest commit e4fb733 Jun 22, 2012 @mitchellh Don't reset ticks on GC_TICKS so that MAX_TICKS will hit.
By resetting on GC_TICKS, MAX_TICKS was never reached because it is
always larger than GC_TICKS. So we use a modulo check now. We still
reset MAX_TICKS to 0, since that should be larger.
Failed to load latest commit information.
apps/lifeguard
rel
vendor
.gitignore
.gitmodules
CHANGELOG.md Don't reset ticks on GC_TICKS so that MAX_TICKS will hit. Jun 22, 2012
Makefile
README.md Add README Apr 25, 2012
TODO.md Watches are rescheduled when they are run. Jun 4, 2012
rebar
rebar.config

README.md

Lifeguard

Lifeguard is still alpha quality and not ready for production use.

Lifeguard is a highly scalable, fault tolerant distributed infrastructure and application monitoring service. The health of your systems are determined by checks written in JavaScript that run across the monitoring cluster. The data that the checks inspect can be retrieved from various sources, such as a database, Graphite, or remote SSH commands. Failing checks notify your IT team as necessary.

Features

Lifeguard brings monitoring to the modern age. Some features and a brief description of each is given below:

  • Highly Scalable. Monitoring systems such as Nagios very quickly run into scaling issues as the number of nodes and checks increases. With Lifeguard, you simply add more nodes and computation is evenly distributed across the entire cluster.

  • Fault Tolerant. Lifeguard is master-less and can handle failure in many nodes.

  • Extensible. Checks are all written in JavaScript and run using V8. Data sources and notifiers can be written in Erlang.

Something went wrong with that request. Please try again.