3 ms·

imo Datadog is pretty hostile to OTel too. Ever since https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/5836 https://github.com/open-telem

imo Datadog is pretty hostile to OTel too. Ever since https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/5836 https://github.com/open-telemetry/opentelemetry-collector-co... was nearly killed by them I never felt like they fully supported the standard (perhaps for good reasons) OTel is a bear though. I think the biggest advantage it gives you is the ability to move across tracing providers

bebop 2y ago
I worry that vision is not going to become reality if the large observability vendors don't want to support the standard.
- phillipcarter 2y ago
  FWIW the "datadog doesn't like otel" thing is kind of old hat, and the story was a little more complicated at the time too. Nowadays they're contributing more to the project directly and have built some support to embed the collector into their DD agent. Other vendors (splunk, dynatrace, new relic, grafana, honeycomb, sumo logic, etc.) contribute to the project a bunch and typically recommend using OTel to start instead of some custom stuff from before.
  - arccy 2y ago
    They support ingesting via otel (ie competing with other vendors for their customers) but won't support ingesting via their SDKs (they still try very hard to lock you in to their tooling).
rikthevik 2y ago
> the ability to move across tracing providers It's a nice dream. At Google Cloud Next last year, the vendors kinda of came in two buckets. Datadog, and everyone trying to replace Datadog's outrageous bills.
hangonhn 2y ago
Yeah their agent will accept traces from the standard Otel SDK but there is no way to change their SDK to send the traces to anyone other than Datadog when I last checked a couple(?) of years ago. I mean I understand why they did that but it really removes one of the most compelling parts about Otel. We ended doing the hard work of using the standard Otel libraries. I had to contribute a PR or two to get it all to work with our services but am glad that's the route we went because now we can switch vendors if needed (which is likely in the not too distant future in our case.
jensensbutton 2y ago
Pretty sure Datadog is literally one of the top contributors to OTel.

bebop 2y ago

I worry that vision is not going to become reality if the large observability vendors don't want to support the standard.

phillipcarter 2y ago
FWIW the "datadog doesn't like otel" thing is kind of old hat, and the story was a little more complicated at the time too. Nowadays they're contributing more to the project directly and have built some support to embed the collector into their DD agent. Other vendors (splunk, dynatrace, new relic, grafana, honeycomb, sumo logic, etc.) contribute to the project a bunch and typically recommend using OTel to start instead of some custom stuff from before.
- arccy 2y ago
  They support ingesting via otel (ie competing with other vendors for their customers) but won't support ingesting via their SDKs (they still try very hard to lock you in to their tooling).

rikthevik 2y ago

> the ability to move across tracing providers It's a nice dream. At Google Cloud Next last year, the vendors kinda of came in two buckets. Datadog, and everyone trying to replace Datadog's outrageous bills.

hangonhn 2y ago

Yeah their agent will accept traces from the standard Otel SDK but there is no way to change their SDK to send the traces to anyone other than Datadog when I last checked a couple(?) of years ago. I mean I understand why they did that but it really removes one of the most compelling parts about Otel. We ended doing the hard work of using the standard Otel libraries. I had to contribute a PR or two to get it all to work with our services but am glad that's the route we went because now we can switch vendors if needed (which is likely in the not too distant future in our case.

jensensbutton 2y ago

Pretty sure Datadog is literally one of the top contributors to OTel.