3 ms·

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 ca

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.

predakanga 4y ago
> How long before Grafana has these capabilities in OSS? They've already started down that path with Grafana Tempo[0]. It's functional, but their UX and discoverability need a lot of work. [0]: https://grafana.com/oss/tempo/ https://grafana.com/oss/tempo/
dalyons 4y ago
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.
Mesverrum 4y ago
As someone who has been in this space a long time I think you are pretty off base here. The commercial vendors have absolutely been the ones who did all the innovations in tracing. The OSS equivalents were really poor imitations for the longest time. Zipkin/Jaeger/Opentrace have been coming along slowly for many years, but it's really been maybe 2 years since that work has really become competitive with what was available in the commercial APM space. For the most part it's felt like that only happened because the commercial tools have all halted new work on their proprietary tools and told their staff to push Otel over the finish line. None of them actually want to pay teams of engineers to maintain proprietary libraries for every language, the execs are absolutely drooling to find a way to pawn as much of that cost off onto others via Otel. Locking people in on agents is naive when the truly heavy lift in migrating platforms is the swapping dashboards and alerts and retraining all your staff. You see the same thing around integrations, everyone used to have to roll their own proprietary chunks of code that in the end were all querying mostly the same data points back from servers and API's. Now everyone just prefers to wait for the Prometheus exporter and they adopt that instead.

predakanga 4y ago

> How long before Grafana has these capabilities in OSS? They've already started down that path with Grafana Tempo[0]. It's functional, but their UX and discoverability need a lot of work. [0]: https://grafana.com/oss/tempo/ https://grafana.com/oss/tempo/

dalyons 4y ago

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.

Mesverrum 4y ago

As someone who has been in this space a long time I think you are pretty off base here. The commercial vendors have absolutely been the ones who did all the innovations in tracing. The OSS equivalents were really poor imitations for the longest time. Zipkin/Jaeger/Opentrace have been coming along slowly for many years, but it's really been maybe 2 years since that work has really become competitive with what was available in the commercial APM space. For the most part it's felt like that only happened because the commercial tools have all halted new work on their proprietary tools and told their staff to push Otel over the finish line. None of them actually want to pay teams of engineers to maintain proprietary libraries for every language, the execs are absolutely drooling to find a way to pawn as much of that cost off onto others via Otel. Locking people in on agents is naive when the truly heavy lift in migrating platforms is the swapping dashboards and alerts and retraining all your staff. You see the same thing around integrations, everyone used to have to roll their own proprietary chunks of code that in the end were all querying mostly the same data points back from servers and API's. Now everyone just prefers to wait for the Prometheus exporter and they adopt that instead.