Give opsee a try https://opsee.com/

Hi, I'm Cliff Moon, CEO & co-founder of Opsee. Modern applications are built on 3 kinds of APIs: cloud provider APIs, the business logic APIs your engineering team maintains and third party APIs you rely on like Stripe & Twilio. Monitoring your applications without blind spots requires pulling together monitoring of all 3 into one place, with crisp & actionable alerts instead of a deluge of dashboards to sift through.

Opsee monitors and tests the APIs you rely on, so you can stop worrying about downtime and get back to shipping code. Opsee lets you create health checks for your public facing APIs, ensuring not just their uptime but also validating the data they return and their latency from points all across the globe. We also have an instance you can launch into your AWS environment that lets you health check APIs behind the firewall, and health check Amazon services themselves such as RDS and Cloudwatch.

I'd love to get feedback about your monitoring challenges and what you'd expect to see from a modern monitoring solution.

This is so cool. I got a health check up and running in seconds. We're gonna be trying it out :)

- What are your plans on pricing after beta?

- ETA on sharing dashboards/checks, or some form of team/organization functionality?

- UX Feedback: I dislike the search bar. It's very non-obvious that it's an input, barely even looks clickable.

- General feedback: No obvious way to customize or even view check frequency. Are they every minute? Every 24 hours? I can't tell.

- Bug: I broke webhook test with an ipv6 address. Can I add custom headers to the webhook?

Thanks!

- You'll get a single check for free for life and after that we'll be charging $5 per check / month.

- Teams are coming in the next week or so, we can add you to the whitelist for early access.

- feedback has been relayed to the team, thanks.

- Checks run every 30 seconds, we go into detail in the docs: https://app.opsee.com/docs/checks.

- Unfortunately we don't support IPv6 or custom headers on webhooks quite yet, but we'll put them in the queue to implement.

Continuing my thoughts for earlier, I personally see a need for less-frequent monitoring checks of various kinds. For example, if I could set up a daily check that my SSL certificate is valid for at least 2 more weeks, your service would warn me when my certs are about to expire.

SSL-related asserts would be awesome in general.

Thanks! I'll wait for teams, no need to whitelist me.

$5/check/month gets very expensive, very fast if I want to make a lot of use of your product. Would you consider making single-region checks available for a lower price? eg. in the cases where I care less about latency and more about general availability.

I share the same feeling. $5/check/month is really expensive. but what I realized is that this is no replacement for functional tests.

Congrats on the launch, Cliff!

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.

Thanks. New Relic incentivizes running fewer, larger instances, which unnecessarily exposes to risk of machine failure.

Exactly, and with a containerized infrastructure the per host pricing model breaks down further. Our goal is to have the most frictionless pricing model for people with a microservice architecture.

Just to be clear: we (New Relic) explicitly state on our pricing page that we do NOT charge for containers. It's in our FAQ. We view them as processes, not hosts.

I'm working on a startup that does exactly this. It's AWS only and in private beta right now: https://opsee.com/

Opsee | Frontend Application Developer | SF, Full Time, Early Stage

Opsee is looking for a talented, senior frontend engineer to be our second employee and lead development of our web application. You’ll be using your expertise in Javascript and modern frameworks to build tools developers love.

You’ll work closely with the backend team to spec and build new features, and process real-time data streams from our APIs and bastion hosts. You’ll also work with design to create a seamless and delightful product experience, and a powerful web application to notify users of problems and visualize and report on their application health and performance.

Opsee is early stage, but we're well funded and offer competitive salary, great benefits, and generous equity. Get in touch: cliff@opsee.co

Boundary already has a bunch of open source stuff and more coming soon. https://github.com/boundary. Our first offering will be as a service. If you want to talk more ping me cliff@boundary.com.