Co-founder here. The big difference, compared with tools like Pingdom, is that we're operating inside your environment. We can tell you where the failure happened and give you tools to fix it. We're like Pingdom for microservice environments, helping developers know their services, inside or outside the firewall, are working as expected.
I saw a demo of this a few months ago, and it looks like they're reframing the product now with Health Checks being the primary feature. I know it's a small difference from monitoring, but I'd be interested to know why the change in framing.
It seems like everyone conflates the term monitoring with metrics, so instead of spending a lot of words in our messaging trying to redefine it, we felt it's more straight foward to frame everything around health checks. Hope that answers your question.
Hey, I'm one of the co-founders of Opsee. Part of our beta is collecting enough data to figure out a reasonable pricing structure. We're leaning pretty heavily towards charging based on the number of health checks you have setup, independent of the number of instances you're checking. So it'll be much closer to how pingdom does pricing than a new relic, for instance.
I saw a first-hand demo of this a couple of months ago - looks like a great way to start external monitoring without putting in too much effort, and will easily cover the needs of many public-facing sites and services.
