Lexicon
Vendor lock-in
Vendor lock-in is the switching cost that keeps you on a platform: agents, formats, query languages, contracts. How observability lock-in works and unwinds.
On this page
Definition
Vendor lock-in is the accumulation of switching costs that makes leaving a platform impractical regardless of how the relationship is going: proprietary instrumentation, captive data, workflows that exist in only one tool, and contracts priced to reward staying. In observability, lock-in has historically been severe.
What it means in observability
Observability lock-in earned its reputation honestly. The classic model put a vendor's agent on every host, in every container, sometimes in every function, so switching meant re-instrumenting the entire estate. Years of dashboards, monitors, and runbooks written in a proprietary query language compounded the hold, and the telemetry itself sat in the vendor's cloud, exportable in theory and in practice too large to move. Each renewal negotiation happened with the vendor knowing all of this as well as you did.
How it works in practice
Lock-in operates through three layers. Instrumentation lock: proprietary agents and SDKs that only speak to one backend, which OpenTelemetry was created to dissolve. Data and workflow lock: telemetry stored in proprietary formats behind proprietary query languages, with the accumulated dashboards and alerts as hostages. Commercial lock: multi year commitments and volume discounts engineered so leaving mid contract costs more than staying. Reducing lock-in means addressing each layer, starting with instrumentation, where the open standard now makes portability the default.
Where it gets hard
OpenTelemetry solved less than teams assume. Platforms that are OTel compatible rather than OTel native accept open data at the door and convert it into proprietary shape inside, quietly relocating lock-in from instrumentation to storage. Egress costs make repatriating accumulated telemetry expensive even when export is technically offered. And workflow migration, the dashboards, the alerts, the muscle memory, remains real work that no standard eliminates.
Where Tsuga fits
Tsuga minimizes both ends: OpenTelemetry native means your instrumentation and its exact data shape stay portable, and BYOC means the telemetry sits in your own cloud account either way. If you ever leave, the data was always yours; exit is a configuration change, not a migration project.
Related terms
- BYOCBYOC, Bring Your Own Cloud, is a deployment model where a vendor's software runs inside the customer's own cloud account, operated by the vendor but living on infrastructure the customer owns.
- Data sovereigntyData sovereignty is the question of whose laws govern your data and who can be compelled to grant access to it.
- DatadogDatadog is the largest SaaS observability platform, spanning infrastructure monitoring, APM, logs, RUM, security, and dozens of adjacent products, collected largely through its proprietary agent and priced per product.
- DynatraceDynatrace is an enterprise observability platform known for its OneAgent automatic instrumentation, the Davis AI engine for root cause analysis, and the Grail data lakehouse, sold on a consumption based pricing model.
- Egress costsEgress costs are the fees cloud providers charge for data leaving their network, priced per gigabyte and varying by destination.
- Elastic ObservabilityElastic offers observability built on the Elasticsearch stack: log search at its core, with metrics, traces, and APM layered on, available self managed or as the hosted Elastic Cloud.
- New RelicNew Relic is one of the original APM vendors, now a broad all in one observability SaaS covering APM, infrastructure, logs, browser monitoring, and more, priced on data ingested plus per user seats.
- OpenTelemetryOpenTelemetry is an open source framework for generating, collecting, and exporting telemetry: the logs, metrics, and traces that describe how software behaves in production.
- Semantic conventionsSemantic conventions are OpenTelemetry's standard vocabulary: the agreed names, types, and values for the attributes that describe telemetry.
- SplunkSplunk is the long standing leader in log analytics and SIEM, acquired by Cisco in 2024, offering log search through its SPL query language plus an observability suite spanning metrics and traces.