DataDog asked OpenTelemetry contributor to kill pull request

Re:DataDog asked OpenTelemetry contributor to kill pull request by ren_engineer on Thursday January 26, 2023 @07:24PM (#34540848)

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

[ Parent | on HN ]

Re:DataDog asked OpenTelemetry contributor to kill pull request by MuffinFlavored on Thursday January 26, 2023 @07:28PM (#34540887)

> 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.

[ Parent | on HN ]

Re:DataDog asked OpenTelemetry contributor to kill pull request by rad_gruchalski on Thursday January 26, 2023 @09:00PM (#34541561)

I used the collector to proxy otel traces to jaeger zipkin for uniform istio tracing.

[ Parent | on HN ]

Re:DataDog asked OpenTelemetry contributor to kill pull request by xcasperx on Thursday January 26, 2023 @10:43PM (#34542188)

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

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

[ Parent | on HN ]

Re:DataDog asked OpenTelemetry contributor to kill pull request by vertis on Saturday January 28, 2023 @12:00PM (#34559206)

I understand the need to charge money for things, but the $150 per month pretty much rules out any bootstrapped startups.

[ Parent | on HN ]

Re:DataDog asked OpenTelemetry contributor to kill pull request by MuffinFlavored on Sunday January 29, 2023 @01:24AM (#34565495)

I wish I knew the right answer between "spin up a cloud VPS Linux server and run your own with Docker compose" and pay $150/mo for something like DataDog

[ Parent | on HN ]

Re:DataDog asked OpenTelemetry contributor to kill pull request by m-o11y on Friday January 27, 2023 @02:39AM (#34543624)

If you're looking for something a bit more "few-clicks-and-you-are-and-running", check out OpsVerse ObserveNow: https://opsverse.io/observenow-observability/ .. Entirely powered by OSS tools, ingestion-driven pricing, and without the hassle of managing the stack and scaling up.

[ Parent | on HN ]

Re:DataDog asked OpenTelemetry contributor to kill pull request by hughesjj on Wednesday February 01, 2023 @01:12PM (#34614858)

Add another exporter to the `otel-config.yaml` and if they support it properly that should literally be all it takes. That said, "if they support it properly" is exactly what otel is working on. It's super stable for a <v1 release but is still missing some features and polish imho that prevents it from getting the official v1 tag.

[ Parent | on HN ]

Re:DataDog asked OpenTelemetry contributor to kill pull request by ChrisCooneyUK on Friday January 27, 2023 @05:08AM (#34544440)

Full transparency: I work at Coralogix HOWEVER I am speaking as me, Chris, the engineer, and do not reflect the views of Coralogix!!

This business model is only bad for a company if they're not confident that the value they bring isn't enough OR if there is a plan to ratchet up prices, once customers are locked in. If the agreement is transparent, then there's no need for this kind behaviour. That's why at Coralogix, we openly encourage our customers to use an open source integration, and we keep them around with 30 second ticket response times and 40-70% cost savings, without any performance or feature sacrifice :) https://coralogix.com/docs/opentelemetry-using-kubernetes/

[ Parent | on HN ]

Re:DataDog asked OpenTelemetry contributor to kill pull request by mindcrime on Friday January 27, 2023 @06:59AM (#34545077)

which is obviously bad for DataDog and other companies business model

Meh. The best way to keep somebody on your product is to make it easy for them to get off your product.

[ Parent | on HN ]