Eero Founder Takes on Observability Giants: 'They're Selling You the Problem'

The multi-billion dollar observability market is about to get a shakeup. Tim Lossen, the engineer behind the popular open-source data router Vector, is publicly calling out major observability vendors for profiting from complexity. Lossen argues these companies benefit from bloated data pipelines and vendor lock-in, rather than solving the underlying problems. This is a direct shot at the likes of Datadog, New Relic, and Splunk, and Lossen isn't holding back.

From Vector to Vendor Critique

Lossen's credibility stems from his deep understanding of data infrastructure. Vector, now maintained by Datadog after acquisition, is a widely-used tool for routing, transforming, and aggregating observability data. His blog post, titled "I built Vector. Now I'm answering the question your observability vendor won't," directly challenges the business models of established players. The core of his argument? Observability vendors are incentivized to make data processing complex, driving up costs and creating dependency on their platforms.

"The dirty secret is that observability vendors make more money when your systems generate more data, regardless of whether that data is actually useful," Lossen writes. He points to the proliferation of agents, sidecars, and proprietary formats as symptoms of this problem. Instead of simplifying data pipelines, vendors often add layers of abstraction that ultimately increase operational overhead. This resonates with many engineers who struggle with the cost and complexity of managing observability data at scale.

A Call for Open Standards and Simplicity

Lossen is advocating for a shift towards open standards and simpler, more efficient data processing. He believes that companies should prioritize reducing the volume of irrelevant data and optimizing their data pipelines before blindly throwing more money at observability tools. He argues this can be achieved through better instrumentation, data filtering, and aggregation techniques. This approach would empower engineering teams to take control of their data and reduce their reliance on expensive vendor solutions.

His critique also touches on the issue of vendor lock-in. Many observability platforms use proprietary data formats and APIs, making it difficult to switch providers or integrate with other tools. This creates a significant barrier to entry for smaller players and limits customer choice. Lossen is calling for greater interoperability and standardization to promote a more competitive and open market. It remains to be seen whether this call will resonate with the larger community and spur meaningful change.

Industry Reaction and Future Implications

Lossen's comments have already sparked a heated debate within the observability community. Many engineers and open-source advocates are applauding his willingness to challenge the status quo. However, some industry insiders are dismissing his claims as sour grapes, pointing to the value that established observability platforms provide to large enterprises. Regardless of the outcome, Lossen's intervention has brought a crucial issue to the forefront. The industry needs to address the inherent conflict of interest in the current vendor-driven model. As companies generate exponentially more data, the pressure to optimize costs and simplify operations will only intensify. Lossen's critique may well be a harbinger of a broader shift towards more efficient and open observability solutions. The future favors efficiency and control.