Rick Bradley c49c252f8f [QENG-4075] Allow specifying 'graphs:' for dashboard ... Prior to this the dashboard front-end would use the configuration settings for `graphite[:server]`/`graphite[:prefix]` to locate a graphite server to use for rendering graphs. Now that we have multiple possible metrics backends, the front-end graph host for the dashboard could be entirely different from the back-end metrics server that we publish to (if any). This decouples those settings: - use `graphs[:server]` / `graphs[:prefix]` for the graphite-compatible web front-end to use for dashboard display graphs - fall back to `graphite[:server]`/`graphite[:prefix]` if `graphs` is not specified, in order to support legacy `vmpooler.yaml` configurations. Note that since `statsd` takes precedence over `graphite`, it's possible to specify both `statsd` (for publishing) and `graphite` (for reading). We still prefer `graphs` over `graphite`. Updated the example `vmpooler.yaml` config file.		2016-07-12 15:22:13 -05:00
..
vmpooler	[QENG-4075] Allow specifying 'graphs:' for dashboard	2016-07-12 15:22:13 -05:00
vmpooler.rb	(maint) move statsd-ruby require into Vmpooler::Statsd class	2016-07-12 14:52:09 -05:00