Skip to content
Browse files

this shouldn't be this hard

  • Loading branch information...
1 parent a475b76 commit 029450405f71d8c71f2ca7982f645b6b3e5c0c17 Geoff Flarity committed
Showing with 6 additions and 4 deletions.
  1. +6 −4
@@ -1,13 +1,13 @@
-BBB# Nervous - Monitoring doesn't have to suck.
-#83;40003;0c# Manifesto:
+# Nervous - Monitoring doesn't have to suck.
+# Manifesto:
Graphite does a good job storing and presenting time series data. But I've yet to find satisfactory solution to the problem of gathering hardware, operating system and application data to feed Graphite. Collectd comes closest, but using C is uncessary overkill (these days) and more importantly creates a unecessary barrier to plugin development.
"Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices."
The ease with which plugins can be written in Node.js JavaScript is also advantage. For these reasons I feel that Node.js is perfectly suited for writing a pluggable monitoring system. Nervous is the embodiment of these beliefs, it is a simple plugin based monitoring system with support for sending data to Graphite (or Response). It follows the 'convention over configuration' and 'keep it simple shithead' ethea.
Contributions in the form of code, plugins, documentation, spreading the word, high fives are all encouraged. Specifically I could use help creating startup scripts, packaging manifests for different platforms etc.
## About Plugins:
@@ -20,7 +20,9 @@ Plugins get loaded during startup. Inside the plugin you define how data gets re
## Quick Start:
1) Install/setup Graphite (optional)
2) edit the config in ./bin/nervous file, if you don't have graphite then change system_type to 'stdout' instead.
3) start nervous up
cd plugins

0 comments on commit 0294504

Please sign in to comment.
Something went wrong with that request. Please try again.