Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Opsee – Continuously test your services and deploy with confidence

opsee.com

Post reply on HN
Print view View original

11–16 of 16 posts

Re: Opsee – Continuously test your services and deploy with confidence

#11

Post by sboak »

toomuchtodo wrote: post #10
sboak wrote: post #8

Earlier quoted context omitted.

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.

Would you say you're competing with Nagios/Zabbix/Sensu/OpsServer?

Yes, definitely. That will become more clear when we launch support for RDS/SQL health checks in the next few weeks. The biggest differentiator between us and these OSS tools is ease-of-use and maintenance. With Opsee there are no configurations to manage, YAML files to create, or agents to run. Setup is dead simple, and you never need to maintain health checks. Our checks react instantly to changes in your infrastructure.

Re: Opsee – Continuously test your services and deploy with confidence

#12

Post by wahnfrieden »

cliffmoon wrote: post #6
dvcc wrote: post #4

Free during public beta... and then what? Rather just know the pricing model outright.

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.

Re: Opsee – Continuously test your services and deploy with confidence

#13

Post by cliffmoon »

wahnfrieden wrote: post #12
cliffmoon wrote: post #6

Earlier quoted context omitted.

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.

Re: Opsee – Continuously test your services and deploy with confidence

#15

Post by Lightbody »

cliffmoon wrote: post #13
wahnfrieden wrote: post #12

Earlier quoted context omitted.

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.
Post reply on HN