Live data from Hacker News

Riemann – A network monitoring system

riemann.io

41–50 of 109 posts

Re: Riemann – A network monitoring system

#41
post #35

Earlier quoted context omitted.

Is requiring someone to learn a programming language worse than requiring someone to learn a custom DSL? Seems a strange assertion.

Clojure is a bigger language than small custom DSL.

The parts of Clojure required to write a config file are probably roughly the same size as a custom DSL though.

Maps and lists are gonna be maps and lists...

Re: Riemann – A network monitoring system

#42

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…

I'd be really hesitant recommending Skyline, since Etsy has declared it and the rest of Kale a failure.

https://vimeo.com/131581331

Re: Riemann – A network monitoring system

#44
post #37

Earlier quoted context omitted.

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.)

You need a place with all that information anyway, otherwise how do you alert on something being missing? 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...

If a stream of data stops appearing, then you can alert. You don't need to pre-configure the existence of that stream (although if you might never get data from an object, this obviously is a failure you won't catch.)

Your article is a good one but in my experience, many companies are still many years from being able to implement that kind of database:machine knowledge consistency.

Re: Riemann – A network monitoring system

#45
post #41
post #35

Earlier quoted context omitted.

Clojure is a bigger language than small custom DSL.

The parts of Clojure required to write a config file are probably roughly the same size as a custom DSL though. Maps and lists are gonna be maps and lists...

Except for Clojure's data model. You'll still need to understand what apostrophe ("'") does and what keyword (":foo") is.

Re: Riemann – A network monitoring system

#46

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…

We rejected Riemann as well because there was just too much overlap with other tools and the user interface was not very good.

I actually think Clojure is a huge selling point.. seriously you should see the crap that Rackspace has https://www.rackspace.com/knowledge_center/article/alarm-lan... which I'm ashamed to say we use it (the lua monitors though are cool and its free monitoring infrastructure).. and yes its not the same as Riemann as Riemann is not exactly just an alerting tool.

And that is sort of the problem.. Riemann is a tool that does one thing really well but has not that good of a UI.. sadly we want prettier graphs and less granular tool.. a better nagios.

Re: Riemann – A network monitoring system

#48
post #42

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…

I'd be really hesitant recommending Skyline, since Etsy has declared it and the rest of Kale a failure. https://vimeo.com/131581331

We use it (well, a derivative of it) to great success. The trend monitoring has proven invaluable at early detection of problems, at a level where pure thresholds would produce much more noise than signal.

Re: Riemann – A network monitoring system

#49
post #40

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…

> Config file isn't a config file, it's an executed bit of Clojure code 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 sup…

That was my problem with Riemann. I love its core but I really want something built on top of it. Basically a Jenkins of monitoring (since clojure is JVM). I contemplated building it (ie taking Jenkins plugin system as inspiration) but it was just way to much work.

Re: Riemann – A network monitoring system

#50
post #32

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…

IME configs often end up being turing-complete; if so, better to have them in a real programming language where you at least have tools available to manage the complexity.

The problem with configs (and this is with my operations hat on), is that they are rarely as well secured (or reviewed) as regular code, so code based configuration files pose a significant privilege escalation threat on production servers.

With my programmer's hat on, they're also harder to populate programmatically, so I have a hard time justifying their use.

Post reply on HN