Hi All, This is Stefano, NetBeez cofounder. We decided to build NetBeez because we felt the pain of supporting remote users without having proper data available to detect network and application performance issues. Users generally knew before us that this or that application was not working. The monitoring tools we were using only checked the status of routers and servers and were not good at detecting partial/performance failures that users experienced.<p>NetBeez agents monitor the network and applications from the user perspective. You can apt-get our software agent and install it on different linux boxes, then start running PING, DNS, HTTP, and Traceroute tests agains web applications. By doing so you catch two birds with one stone, because you validate (1) network connectivity and performance at the locations where the agents are installed and (2) detect problems with the web application itself. Also, you can understand if a problem is local (only affecting one location, thus most probably network related) or global (affecting all the locations, thus most probably web service related). We also have a Raspberry Pi image available on our website.<p>That's pretty much it, I hope you like it and please feel free to reach out to us anytime if you need help to setup or configure it.
I've got multiple physical egress points and multiple upstream providers so I do most of our monitoring myself. My home office (I work remotely) and phone -- the two places I receive alerts -- are both "off-net" so I've been looking for something simple and lightweight to "monitor the monitor" (and perhaps another important host or two) from outside the network.<p>I went to the Product Overview page, scrolled down, saw the pricing, and closed the tab. Perhaps I didn't learn enough about the product's features in the short amount of time I was on the site but the pricing just seems outrageous to me.<p><i>Edited to add background info:</i> I'm evaluating alternatives to my current monitoring application, Opsview, which runs entirely from a single internal server. I'm looking for something that can be split across multiple servers in multiple sites (directly connected) so that I can monitor the (primary) monitoring system and be alerted if it is having issues (e.g. "A" monitors "B", "B" monitors "A").
Fellow 'burgh resident here :) Any plans to add other tests (ftp, smtp, random homebrew app port, etc) or is the focus going to stay on web applications?
Let's go Pittsburgh startup! I was ecstatic to see netbeez on the front page.<p>Also, with us opening remote offices, this might be something that comes in handy.