31–40 of 109 posts
I like it so much that I did an experiment to implement it in C++
https://github.com/juruen/cavalieri
My implementation sucks, but I had a lot of fun working on it and I got to learn how Riemann works better.
Evaluated it, and ultimately rejected it for a couple of reasons: - You must pick up Clojure to understand and configure Riemann (we're not a Clojure shop, so this is a non-trivial requirement) - Config file isn't a config file, it's an executed bit of Clojure code - Riemann is not a replacement for an alerting mechanism, it's another signal for alerting mechanisms (though since it's Clojure and the configuration fil…
Earlier quoted context omitted.
It's actually a disadvantage, since it's Clojure, and Riemann requires that its operator actually knows Clojure (knowledge of dozen languages, even when some of them are functional, is not enough).
Is requiring someone to learn a programming language worse than requiring someone to learn a custom DSL? Seems a strange assertion.
Earlier quoted context omitted.
It's actually a disadvantage, since it's Clojure, and Riemann requires that its operator actually knows Clojure (knowledge of dozen languages, even when some of them are functional, is not enough).
Is requiring someone to learn a programming language worse than requiring someone to learn a custom DSL? Seems a strange assertion.
Clojure. I think I should stop thinking and really learn that language now. It seems very tempting as a first functional language.
Earlier quoted context omitted.
I don't like it since the master basically does a curl on each server to get the info, so it doesn't work behind a firewall without tons of issues
That's the reason I haven't bothered with Prometheus - pull systems make no sense to me since you have to configure a single place with perfect* knowledge of your system rather than just pushing local knowledge to a collector. (Ok, you do need some knowledge at the parent if you want to raise alerts but you'd need that anyway.)
If you can't easily do that with your existing infrastructure, you should fix that first. I've written about this at http://www.robustperception.io/you-look-good-have-you-lost-m...
Anyone use http://prometheus.io/ ? wdyt
I don't like it since the master basically does a curl on each server to get the info, so it doesn't work behind a firewall without tons of issues
Evaluated it, and ultimately rejected it for a couple of reasons: - You must pick up Clojure to understand and configure Riemann (we're not a Clojure shop, so this is a non-trivial requirement) - Config file isn't a config file, it's an executed bit of Clojure code - Riemann is not a replacement for an alerting mechanism, it's another signal for alerting mechanisms (though since it's Clojure and the configuration fil…
For stream processing engines, configuration will be code. Unfortunate, but unavoidable.
> Riemann is not a replacement for an alerting mechanism
> Riemann is not a replacement for a trend graphing mechanism.
Indeed it is not. It's misadvertised as a monitoring solution, while it's a stream processing engine.
What I think of it is that you're supposed build a monitoring system on top of stream processing engine. It's a pity Riemann doesn't allow to subscribe to its streams from the outside, so to add any message destination you need to update its config.