3 ms·
No offense meant to the contributors or authors, but I don’t know if I trust Datadog (the company) to steward what looks to be an OTEL competitor.
by _pob 3y ago
No offense meant to the contributors or authors, but I don’t know if I trust Datadog (the company) to steward what looks to be an OTEL competitor.
- datadeft 3y agoBut you trust a committee to deliver one of the most crucial part of your infra?
- jakewins 3y agoTo deliver a cross vendor narrow spec, you mean? Given my experience with Datadogs pricing lock-in-and-switch, yeah 100% I’d rather run agents that allow me to pick the collection backend than another tool from Datadog.
- datadeft 3y agoNot sure what pricing you are talking abot in the context of Vector. Its license explicitly allows free of charge commercial use. https://github.com/vectordotdev/vector/blob/master/LICENSE https://github.com/vectordotdev/vector/blob/master/LICENSE For the record here is what Vector is: https://github.com/vectordotdev/vector/blob/master/website/static/img/diagram.svg https://github.com/vectordotdev/vector/blob/master/website/s...
- dan-robertson 3y agoWithout having thought much about this, surely datadog only want to store your data and have you pay for the storage/indexing/querying? I guess your worry is something like datadog making themselves the only possible backend? I don’t feel like that’s a very big risk – I think trying it would just lead to a fork of vector. Perhaps a more realistic risk is that vector would implicitly assume datadog’s constraints, eg (making these up without knowing much about datadog) field types or required information or the expected number of unique fields across all messages.
- jakewins 3y agoYeah the trick is if they can lock you into a stack that sits everywhere in your apps, it’s very expensive to switch vendors, letting them extract high rents. This is what happened with the Datadog agents. In that context, OTEL is an existential threat, because it makes them a commodity. Then it becomes relatively clear why they wouldn’t put OTEL support in the Vector roadmap.
- dan-robertson 3y agoI guess I’m surprised that your claim is basically that datadog’s advantage is in ingestion. I would have assumed they would be focusing on trying to make a product so good that people wouldn’t want to switch from it. Vector supporting multiple backends would be good for datadog if it can get more people in the door, so long as their product is compelling enough for people to stay. I don’t know what exactly you mean about otel but elsewhere in this comments section someone linked to upscale, which uses vector to collect otel logs. Is that a counterexample?
- jakewins 3y agoMy experience with using Datadog at (some) scale was that they focused on making it really, really easy to integrate their agent with your apps, and then once they had a large base of users with high switching costs they started rapidly raising prices. In other words: My claim isn’t that they were better at ingestion but at onboarding and at creating switching costs. Since that was how their leadership acted last time I used their code, I expect the same leadership to act the same way again with this other piece of code they own.
- lokar 3y agoSame here. At work we were gearing up to use this, but after the acquisition changed focus to otelc.
- FridgeSeal 3y agoIIRC this work predates acquisition by datadog, and it’s continued well since then.
- NewJazz 3y agohttps://github.com/vectordotdev/vector/issues/1444#issuecomment-1703937605 https://github.com/vectordotdev/vector/issues/1444#issuecomm...