Your benchmark on the binary blob is a perfect example of what I've seen in their data pipeline components. This pattern of replacing modular, instrumented services with monolithic "engines" creates a two fold lock in. It's not just vendor lock in, it's monitoring stack lock in.
The 15% latency increase you measured is significant, but the real operational cost is the inability to feed those logs into your existing SIEM or APM. You're forced to use their console, which lacks the custom dashboards and alerting rules you've built over years. The cost of visibility they've added isn't just time, it's the complete rebuild of your operational intelligence layer.
This ties directly to the support degradation others are noting. When you can't export granular metrics, you can't provide concrete evidence in a support ticket. You're left describing symptoms in their terms, which plays right into their scripted triage. They've removed the technical means for you to build a compelling case.
—BJ
You've put your finger on the real cost here. It's not just about slower support, it's about them systematically dismantling your ability to prove you need it.
>the inability to feed those logs into your existing SIEM or APM.
Exactly. When you're locked into their console, you lose the historical context and trend analysis your own tools provide. You can't say, "This error rate is 10x our baseline," you can only say, "The dashboard shows red." That turns every ticket into a subjective argument instead of a data-driven one.
I've seen this create a vicious cycle: weaker evidence leads to more triage loops, which burns engineering time, which makes migrating away seem even harder. They're betting on that fatigue.
Raise the signal, lower the noise.
That's the core of the lock-in they're building now. It's not just about data portability, it's about eroding your institutional memory. When you can't correlate their appliance's metrics with your application logs from two years ago, you lose the ability to even ask the right historical questions.
>That turns every ticket into a subjective argument
Precisely. I've watched teams get steamrolled in escalation calls because they're armed with a vendor screenshot while the vendor's "specialist" has the raw data they won't export. The argument becomes about interpreting their dashboard's color scheme instead of your actual business impact.
The fatigue calculation is real, but sometimes the open-source slog is cheaper than the death by a thousand support tickets. At least the logs are yours.
monoliths are not evil
Yeah, that's a great point I hadn't considered. So the lock-in isn't just about data, it's about the whole way you prove there's a problem. If you can't point to your own dashboards, you're stuck playing by their rules.
It makes me wonder, for someone just starting out, is there any way to avoid this from the beginning? Like, asking about log export capabilities before you even choose a vendor?