Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Stack Exchange's monitoring system is now open source

github.com

Post reply on HN
Print view View original

21–30 of 57 posts

Re: Stack Exchange's monitoring system is now open source

#21

Post by rch »

AsymetricCom wrote: post #10

Looks like a tangled mess of a decision engine. Why would anyone want this? Surely, there are other solutions out there that are more mature? (nagios comes to mind but is a poor example)

Any and all answers to this question would be appreciated, even those that just qualify as 'promising' and 'active' (as opposed to mature). All I know of is nagios really.

Re: Stack Exchange's monitoring system is now open source

#22

Post by hamburglar »

AsymetricCom wrote: post #10

Looks like a tangled mess of a decision engine. Why would anyone want this? Surely, there are other solutions out there that are more mature? (nagios comes to mind but is a poor example)

The fact that you're labeling the only alternative you can think of "a poor example" seems significant. Edit: and I agree that nagios is a poor example, and welcome newcomers.

Re: Stack Exchange's monitoring system is now open source

#24

Post by meowface »

kingkilr wrote: post #20
crazygringo wrote: post #16

Earlier quoted context omitted.

Interesting. Why? What would be valuable about the commit history for you?

The same things that are valuable about any commit history?

I would imagine that if you're a random person only just finding the project now and aren't already involved in it (by working for or with Stack Exchange), then you probably wouldn't get all that much value out of the commit history.

Feel free to dispute that, though. There may be some scenarios I'm not considering.

Re: Stack Exchange's monitoring system is now open source

#25

Post by gecko »

toyg wrote: post #17

Looks nice, sadly it's just overkill for what I need. Has anyone built a very simple solution to start/stop an arbitrary set of Windows services across several boxes, in a specific order? It'd be nice to have a simple GUI for this sort of thing. I've started working on it, but I suck at desktop programming (well, at programming in general, probably)...

Unless you really need a GUI, it's insanely easy to do exactly this with PowerShell workflows (http://technet.microsoft.com/en-us/library/jj134242.aspx).

Re: Stack Exchange's monitoring system is now open source

#26

Post by michaelfdeberry »

pygy_ wrote: post #9

Wow... Nice one. Does anybody know if it works with Mono?

I haven't pulled the code yet, but it looks like it targeting MVC4. The documentation[1] states that mono currently partially supports it, everything but the async stuff, but that doesn't mean there isn't anything else in there that will cause it to not be compatible.

[1]http://www.mono-project.com/Compatibility

Re: Stack Exchange's monitoring system is now open source

#27

Post by sk5t »

jamesRaybould wrote: post #5

Having a quick poke around and I notice that they are storing all exceptions in an SQL database. I've been looking at storing all the errors we get in our various applications in a central repository and was wondering what the general consensus was? Currently I'm going a centralised logstash server and using a logstash shipper on each of my servers to push the exceptions, from a standard logfile to it. I was toying w…

We built our monitoring package at Zetetic to be extremely flexible about what events go where, with multiple levels of non-blocking filtering and routing, so that everything remotely interesting could go to SQL (with or without a durable local queue in front of it), and just very critical stuff could also go to a local embedded database / lpr / MQ / ZeroMQ publisher, etc. My preference is for decoupled ZMQ subscribers to handle anything very gnarly.

Internal errors in the monitoring software itself first surface in NLog, which could--but probably oughtn't--be configured to feed even more errors into the monitoring system; obviously this could create a terrible feedback loop if left unchecked.

Re: Stack Exchange's monitoring system is now open source

#28

Post by tedunangst »

meowface wrote: post #24
kingkilr wrote: post #20

Earlier quoted context omitted.

The same things that are valuable about any commit history?

I would imagine that if you're a random person only just finding the project now and aren't already involved in it (by working for or with Stack Exchange), then you probably wouldn't get all that much value out of the commit history. Feel free to dispute that, though. There may be some scenarios I'm not considering.

    if (x  1776)
        useConfabulator = false;
Why? Who knows? People don't comment their code for many reasons, not least of which is that it's not technically required and you can easily put it off and forget. Every checkin generally requires at least some comment. You can still enter meaningless messages like "fix", but you're not liable to do so by accident.

Re: Stack Exchange's monitoring system is now open source

#29

Post by stevepotter »

The anti .net kneejerk reactions on HN really disturbs me. You spend all day on stackoverflow then blindly bash their tech stack. Developing, deploying, and hosting .net apps is just fine. Many brilliant people choose .net and are plenty happy with it. Maybe rather than jumping to conclusions, you could give it a shot.

Re: Stack Exchange's monitoring system is now open source

#30

Post by rurounijones »

stevepotter wrote: post #29

The anti .net kneejerk reactions on HN really disturbs me. You spend all day on stackoverflow then blindly bash their tech stack. Developing, deploying, and hosting .net apps is just fine. Many brilliant people choose .net and are plenty happy with it. Maybe rather than jumping to conclusions, you could give it a shot.

What anti .net kneejerk? At time of this comment there are 28 comments, only 2 of which are anti .net / Microsoft (with no replies) and they are already well on their way to being downvoted into oblivion.
Post reply on HN