github
Advanced Search
  • Home
  • Pricing and Signup
  • Explore GitHub
  • Blog
  • Login

fiveruns / dash-sensor

  • Admin
  • Watch Unwatch
  • Fork
  • Your Fork
  • Pull Request
  • Download Source
    • 20
    • 4
  • Source
  • Commits
  • Network (4)
  • Issues (0)
  • Downloads (1)
  • Wiki (1)
  • Graphs
  • Branch: master

click here to add a description

click here to add a homepage

  • Branches (1)
    • master ✓
  • Tags (1)
    • v0.8.5
Sending Request…
Enable Donations

Pledgie Donations

Once activated, we'll place the following badge in your repository's detail box:
Pledgie_example
This service is courtesy of Pledgie.

Daemon for external monitoring of infrastructure with Dash — Read more

  cancel

  cancel
  • Private
  • Read-Only
  • HTTP Read-Only

This URL has Read+Write access

Update sample config with varnish config 
mperham (author)
Wed Mar 11 13:53:53 -0700 2009
commit  72de782d038680c27c2e971cf6a96378199d24dd
tree    68351ffdf901ff0cd3d40140cfcb754e86151b11
parent  5ff5d8799332608c2eb1edcb59d52c28a0e33a17
dash-sensor /
name age
history
message
file .gitignore Loading commit data...
file README.rdoc
file Rakefile
file VERSION.yml
directory bin/
file config.rb
file dash-sensor.gemspec
directory lib/
directory plugins/
README.rdoc

fiveruns-dash-sensor

Please see dash.fiveruns.com for an overview of the Dash service.

Summary

Sensor provides a mechanism for "external" monitoring of infrastructure with Dash. Since Dash is usually embedded within an application (i.e. internal), there’s no easy way to monitor things like Apache, memcached, or other pieces. Sensor is designed to be installed on a machine and upload metrics for any infrastructure on that machine. The user just needs to configure which elements they want to monitor.

Installation

gem install fiveruns-dash-sensor -s gems.github.com

Configuration

When you run ‘fiveruns-dash-sensor’ for the first time, it will create a blank configuration for you in ~/.fiveruns-dash-sensor/config.rb. You will need to edit this file with your app token and activate the plugins for your environment. Once done, you should be able to restart ‘fiveruns-dash-sensor’ for a few minutes to verify everything is working as designed. If there are no problems, you can run ‘fiveruns-dash-sensor -d’ to spin off the daemon into the background and forget about it.

Command Summary

  fiveruns-dash-sensor --help

Sensor allows you to control OS-specific parameters like log file and PID file location, the user and group to run as, etc. -d will start Sensor as a daemon. To stop it, just kill the associated PID.

Creating your own Plugins

Sensor allows you to create your own custom plugins for your own infrastructure. Each plugin should reside in ~/.fiveruns-dash-sensor/<name>.rb and config.rb should have an entry in it like this:

  sensor.plugin :<name>, any options here...

Please see the existing plugins for examples of how your code should work.

License

  # (The FiveRuns License)
  #
  # Copyright (c) 2009 FiveRuns Corporation
  #
  # Permission is hereby granted, free of charge, to any person obtaining
  # a copy of this software and associated documentation files (the
  # 'Software'), to deal in the Software without restriction, including
  # without limitation the rights to use, copy, modify, merge, publish,
  # distribute, sublicense, and/or sell copies of the Software, and to
  # permit persons to whom the Software is furnished to do so, subject to
  # the following conditions:
  #
  # The above copyright notice and this permission notice shall be
  # included in all copies or substantial portions of the Software.
  #
  # THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,
  # EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
  # MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
  # IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
  # CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
  # TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
  # SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Blog | Support | Training | Contact | API | Status | Twitter | Help | Security
© 2010 GitHub Inc. All rights reserved. | Terms of Service | Privacy Policy
Powered by the Dedicated Servers and
Cloud Computing of Rackspace Hosting®
Dedicated Server