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.
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.
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.
The biggest difference is in the way we handle checks inside AWS. When you add our EC2 Instance we automatically discover your infrastructure and track changes. When you create health checks for groups and other dynamic AWS resources (ELBs, RDS, ECS, etc...) we track membership and automatically update your checks with no maintenance.
I've been a Pingdom user for several years and I can't stand it. I'm very excited to see another player in this market. The one thing we're hoping to see is some form of integration with StatusPage.io. As soon as we have that kind of integration, I'm jumping ship to a new provider.
Hi, I'm Steve and I run product at Opsee. There are a few important differences:
1. The rich assertion language in Opsee means we're checking for more than availability - we're looking for correct responses too. This makes us more useful for checking APIs, since services can fail and still return a 200
2. We're measuring round-trip time for every check - Pingdom charges a lot more for this than their standard checks
3. Usability. Our integrations with Slack and Pagerduty are really simple to set up, our UI is responsive and well...better
4. We can also health check inside your AWS environment when you add our EC2 Instance, giving you more complete coverage. We actually do a lot of cool stuff inside AWS.
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.