3 ms·
jmelloy (https://news.ycombinator.com/item?id=6334778 https://news.ycombinator.com/item?id=6334778) had a really good point that wasn't covered in the post, sin
by stevenjmurawski 13y ago
jmelloy (https://news.ycombinator.com/item?id=6334778 https://news.ycombinator.com/item?id=6334778) had a really good point that wasn't covered in the post, since it was a post about what we are doing not necessarily why we are doing it.
One of our major problems with existing monitoring and management systems is the lack of good APIs. We are a shop of developers and sysadmins who all understand the real management systems need to be composable. The system needs to understand that it won't solve every case out of the box and expose hooks into management and functionality, allowing us to tie disparate systems together and enhance their coverage. I'd rather take a bunch of existing products and put some cool dashboards on top, but most enterprise solutions (and some of the open source ones) don't offer a decent API to work with.
- dvanduzer 13y agoIt's quite likely that I'm confusing "decent API" and "ease of extending and integrating" and all that gets wrapped up with my long term familiarity with Nagios. Nagios check plugins don't have an API per se, but they have a very simple standard for exit codes to be interpreted by the Orchestration component. Nagios reporting/alerting plugins primarily use RRD, so you always have that API to do interesting things like trend analysis. (One theory I have is that there is a such a large and growing culture of technologists that are thinking "integration tool" but only know how to say "HTTP API")