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

DataDog asked OpenTelemetry contributor to kill pull request

github.com

Post reply on HN
Print view View original

71–80 of 107 posts

Re: DataDog asked OpenTelemetry contributor to kill pull request

#71

Post by shyn3 »

slyall wrote: post #49
aeyes wrote: post #39

Earlier quoted context omitted.

> negotiated annual contract Maybe we are too small but Datadog is one of the few vendors which we haven't been able to negotiate down in years. The price has always been whats on the website. I honestly don't even mind, with some vendors it feels like you are on a basar and they always tell you that their final discountns had to get approval by the CEO.

I always tell people looking at Datadog to remember "DDDD" or "DataDog Don't Discount". Compared to most Enterprise vendors it is a lot harder to get a discount from Datadog. Most vendors will give you 1/3 off just for signing a contract and committing to a spend, Datadog is not like that.

Just show them New Relics new pricing

Re: DataDog asked OpenTelemetry contributor to kill pull request

#72

Post by bdcravens »

nabakin wrote: post #52
bdcravens wrote: post #51

I'm always willing to dogpile on DataDog (no pun intended), given bad experiences with their sales, but all I'm reading out of this is that the DD person didn't want to review it out of a potential conflict of interest. It was reviewed however by someone else. Am I missing something here?

You're missing that this was a year-old PR ready to merge but it was stopped from merging by DataDog because it makes it easier for users to migrate from DataDog to another logging service

No, I am unsurprised by the DataDog taking that position; it fits with what I know of the company. However as someone pointed out, the comment in question wasn't originally linked, but I see it now.

Re: DataDog asked OpenTelemetry contributor to kill pull request

#74

Post by xcasperx »

MuffinFlavored wrote: post #34
ren_engineer wrote: post #30

Earlier quoted context omitted.

OpenTelemetry basically allows for vendor neutral instrumentation for your metrics, logs, and traces. It makes it easy to switch to a cheaper or better service with minimal lock-in, which is obviously bad for DataDog and other companies business model

> It makes it easy to switch to a cheaper or better service with minimal lock-in Got any examples? I tried running my own "stack" for a project I wanted alerting on. I landed on Jaeger all-in-one (wasted time on Zipkin, the UI just was nowhere near as good as it ought to be) Docker container in docker-compose with COLLECTOR_OTLP_ENABLED.

Check out telemetryhub.com (admittedly I work here).

We offer a free trial and don't charge per a seat.

Re: DataDog asked OpenTelemetry contributor to kill pull request

#75

Post by davidjfelix »

stvnbn wrote: post #67

How can DataDog threaten open source developers? Can they sue them? what is it?

A little lost here as well but my read was that the PR author was working with outside parties (their company??) to get approval (sign a CLA?) and some third party asked for Datadog's opinion and Datadog advised that they wait for a Datadog feature. Due to this discussion, the third party was in "default no" and the PR author did not push the matter, expecting Datadog to release something, when they did not after several months, the author reopened and pushed to get approval.

I could be totally wrong, but maybe combined we can make sense of it. From my read it feels like DD misguided this third party which then advised the author to spike.

Re: DataDog asked OpenTelemetry contributor to kill pull request

#76

Post by CSDude »

We switched to OpenTelemetry agent from DataDog agent. Out of all commercial providers, Datadog is the worst one to show traces properly. Although it captures mostly the same traces, all of them have io.opentelemetry.something on UI making it very hard to read. I’ve tried Honeycomb, NewRelic, Lightstep.

Re: DataDog asked OpenTelemetry contributor to kill pull request

#78

Post by dalyons »

floatinglotus wrote: post #42

More vendor lock-in shenanigans. Data dog has always been a proprietary POS. I don’t know why people use it, APM traces? How long before Grafana has these capabilities in OSS? So annoying seeing a company like DD who cannot innovate at all, trying to lock in the average company.

Do you actually use it at scale in a large complicated system? IMHO it’s the opposite - datadog is consistently the most innovative and fastest iterating observability platform out there. Nothing comes close. It’s expensive yes, and there’s some lock-in yes, but they are GOOD.

Re: DataDog asked OpenTelemetry contributor to kill pull request

#79

Post by quickthrower2 »

joshxyz wrote: post #54

I love this bit: > Hello, I'm using this receiver in production for about one year, and left some comments that may be helpful. >> Are you serious? That is intense. Did it scale? Any memory issues? If I remember correctly I tuned all that away. Always astonishing to see broken stuff doing well in prod lol.

“Not production ready” stopped noone

Re: DataDog asked OpenTelemetry contributor to kill pull request

#80

Post by zug_zug »

kevincox wrote: post #31
Mizza wrote: post #11

Datadog is stupidly expensive for what it provides. Don't recommend and I hope something open kills it soon.

I'm not so sure to be honest. It is very expensive. But being able to quickly get all of the features is fantastic for a small company. As you start to use more volume (and your bill starts growing) then it makes sense to start considering self-hosting. But for many teams with relatively small data volumes self-hosting is likely not worth the engineering time.

Out of curiosity, is there anything self-hosted that compares to data-dog RUM?
Post reply on HN