Jason Dixon
Jason Dixon
Rather than needing to allow configuration of the step value we might be able to get by with applying a `summarize(target, 10)` to the query.
To be determined. As you've seen in #7, storage schemas can bite users in the ass. I'd love to be intelligent about this and perhaps query Graphite/Carbon for whisper metadata,...
Sorry I missed this earlier. Good idea. I'd be tempted to use `format=raw` for all of our data collection, but since we already use the Graphite context (and I'm too...
Cubism already uses `format=raw` to fetch data, so I'm not sure why they don't already adjust based on the step returned to them. Since we don't know what the range...
Seems useful, got any screenshots?
Yup, encountered this myself recently. Thanks for opening an issue for it. Jason Dixon Sent from my iPhone > On Feb 2, 2015, at 9:27 PM, Tavis Aitken [email protected] wrote:...
I don't think an environment variable (to toggle _everything_) is the right approach. If you want anonymous viewers to be able to read proposals, there needs to be a view...
I think it could be, but I think all judges of the same event would need to use the same scale. I might just stick with the existing 0-10 scale...
Why don't you just set `warning` to 0 and `critical` to 1?
Sure, but you're also using the check in a way it isn't meant to be used. What happens if warning == critical where 1 is "good" and 0 is "bad"?...