No description
f1f131a06b
Every clock tick, check if the lowest priority item in the priority queue is in the past, and possibly expire it. This prevents events from stalling in the dashboard forever when they don't receive any more updates from riemann because thoses updates don't match the query used. |
||
|---|---|---|
| bin | ||
| example | ||
| lib/riemann | ||
| sh | ||
| test | ||
| .gitignore | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE | ||
| Rakefile.rb | ||
| README.markdown | ||
| riemann-dash.gemspec | ||
Riemann-Dash
A javascript, websockets-powered dashboard for Riemann.
Get started
$ gem install riemann-dash
$ riemann-dash
Then open http://localhost:4567 in a browser. Riemann-dash will connect to the local host (relative to your browser) by default, and show you a small manual.
Configuring
Riemann-dash takes an optional config file, which you can specify as the first command-line argument. If none is given, it looks for a file in the local directory: config.rb. That file can override any configuration options on the Dash class, and hence, all Sinatra configuration.
set :port, 6000 # HTTP server on port 6000
set :bind, "1.2.3.4" # Bind to a different interface
config[:ws_config] = 'custom/config.json' # Specify custom workspace config
Development
$ git clone git://github.com/aphyr/riemann-dash.git
$ cd riemann-dash
$ bundle
Testing
# run tests
$ sh/test
Releasing
$ rake build
$ rake release
REPL
$ sh/c
> irb :001 > Riemann::Dash::VERSION
> => "0.2.2"