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

Launch HN: Opstrace (YC S19) – open-source Datadog

news.ycombinator.com

Post reply on HN
Print view View original

41–50 of 120 posts

Re: Launch HN: Opstrace (YC S19) – open-source Datadog

#41

Post by englambert »

opsunit wrote: post #37
englambert wrote: post #34

Earlier quoted context omitted.

It's hard to answer that concretely without knowing a little bit more about your use cases. Care to share a bit more? One thing comes to mind: we don't bill by data volume. Wavefront is charging you for the volume of data your applications produce. This can lead to negative outcomes, such as surprise bills from a newly deployed service and a subsequent scramble to find and limit the offenders. We think this pricing m…

Wavefront brings a number of things to the table that aren't core competencies we wish to maintain in-house. I know it can scale to massive volumes without interaction from us. I know it'll be available when our infrastructure isn't. By being a third party we can be confident that any action on our part (such as rolling an SCP out to an AWS org, despite unit tests) won't impact the observability we rely on to tell us…

We’re building Opstrace to be as simple as a provider like Wavefront -- we’ve failed if you need additional competencies to manage it. That being said, we’re early in our journey and still have a ways to go.

As mentioned in the original post here, at the core of Opstrace is Cortex (https://cortexproject.io). We know that Cortex scales well to hundreds of millions of unique active metrics, so depending on the exact characteristics of your workload, the fundamentals should be there.

However, Cortex is a serious service to run and if you were to DIY it would require operations work that you currently don’t have with Wavefront. This is the problem we’re trying to solve—making these great OSS solutions easier to use for people like you.

Opstrace is made to be exposed on the internet (which is optional of course), so you can easily run it in an isolated account to keep it safe from all other operations. And in fact, this is the configuration we recommend for production use.

Regarding “100s of AWS accounts and 10s of payers”... does that include any form of multi-tenant isolation? We support multi-tenancy out of the box to enable controlling rate limits and authorization limits for different groups. We’d need to talk in more detail about that. If you’d like to do that privately, please shoot me at chris@opstrace.com. We’re of course happy to continue the discussion here with you as well.

Re: Launch HN: Opstrace (YC S19) – open-source Datadog

#42

Post by spahl »

erinnh wrote: post #40
spahl wrote: post #20

Earlier quoted context omitted.

Yes! We will be having features that you have to pay a subscription for. It starts with the usual suspects: custom SSO, custom domains, and authorization - things that we would be hosting as an ongoing service for customers. Most features will be open when we create them -- this is near and dear to our hearts -- it’s important our users can be successful with the OSS version. Over time, the commercial features will a…

Will you have a small(er) plan for homelabs? I like supporting open source projects, and while SSO is pretty useless to me, I always like custom domains.

We are still experimenting with pricing and what can be open and closed. To be completely transparent we chose custom domains because we know companies care a lot. When we have more features on the commercial side we can start to chat about supporting it in the open version. Still early in our journey, happy to discuss anything, like a small plan with just custom domains. Would you pay for that?

Re: Launch HN: Opstrace (YC S19) – open-source Datadog

#44

Post by englambert »

hangonhn wrote: post #39

Damn. That's one hell of a set of credentials for the founders. I was the engineer who was heavily involved with monitoring at my last job and a lot of what this is doing aligns with what I would have done myself. At my new job, I work on different stuff but I can see we're going to run into monitoring issues soon too. I'm so, so, so glad this is an option because I do not want to rebuild that stuff all over again. G…

Hey, thank you. :-) That’s kind of how we feel -- it seems like everyone is building tooling around Prometheus, and frankly, we hope that collective effort can hopefully be redirected to more impactful value creation for our industry. On a personal note, most of us on the team have been there in one way or another, struggling to actually monitor our own work. We’ve had surprise Datadog bills and felt the pain of scaling Prometheus. (In fact, I’m planning a blog post about this struggle, so stay tuned.) It feels like this problem should already be solved, but it’s not. So we’re trying to fix it.

Re: Launch HN: Opstrace (YC S19) – open-source Datadog

#46

Post by fat-apple »

polskibus wrote: post #43

What are your plans on supporting open telemetry? Can I send open telemetry data to opstrace?

Yes you can do this today. You cannot send this directly to Opstrace via grpc yet, so you would need to use the Prometheus remote write exporter (https://github.com/open-telemetry/opentelemetry-collector/bl...) with the open telemetry collector. Right now this means only metrics are supported but we will be working on traces as well. Check out the point about tracing on our roadmap https://opstrace.com/docs/references/roadmap

Re: Launch HN: Opstrace (YC S19) – open-source Datadog

#47

Post by filereaper »

nickbp wrote: post #16
tamasnet wrote: post #11

This looks very promising, thank you and congrats! Also, please don't forget about people (like me) who don't run on $MAJOR_CLOUD_PROVIDER. I'd be curious to try this e.g. on self-operated Docker w/ Minio.

Hi, this is Nick Parker from the Opstrace team. I personally have my own on-prem arm64/amd64 K3s cluster, including a basic 4-node Minio deployment, so I’m very interested in getting local deployment up and running myself. We’re a small team and we’ve been focusing on getting a couple well-defined use-cases in order before adding support for running Opstrace in custom and on-prem environments. It turns into a bit of…

Happy to hear you're now with the old Mesosphere gang at Opstrace Nick!

Re: Launch HN: Opstrace (YC S19) – open-source Datadog

#48

Post by richardw »

Point around incentives: We use Dynatrace. I’m sure it’s an eye-watering price but I do like that everyone who wants a license can get one. I don’t have to consider costs to add an entire dev team and teach them how to use it. It also means an entire dev team knows how to use it for future jobs.

Re: Launch HN: Opstrace (YC S19) – open-source Datadog

#49

Post by rubiquity »

Nice. I've talked myself out of starting a monitoring product at least a few dozen times. As you point out, customers either get to choose between being gouged or run their own spaghetti.

On top of bad UX, I do think the storage layer is where customers are really getting hit by these companies. The big players are using very unoptimized ingestion and querying layers and pretending like tiered storage never happened. Developers share some of the blame too by not being at all pragmatic about how long and how much to keep. It's a tough nut to crack.

What's the plan for commercial? They run it themselves and pay per user? If so, that's refreshing.

Post reply on HN