Avoiding Tool Sprawl in Your Observability Practice
January 26, 2023

Anurag Gupta
Calyptia

Share this

As enterprises work to implement or improve their observability practices, tool sprawl is a very real phenomenon. A recent Cloud Native Computing Foundation (CNCF) survey asked, “how many different tools does your organization use for monitoring, gathering logging and tracing data, and for metrics." The results were intimidating: 72% of respondents indicated that they were using up to nine different tools, and over a fifth said they were using between 10 and 15.

Too often, these tools lack integration and interoperability. Half of the CNCF survey participants identified tool sprawl as one of the biggest challenges to their observability efforts, making it the most common challenge across all organizations.

Tool sprawl can and does happen all across the organization. In this post, though, we'll focus specifically on how and why observability efforts often result in tool sprawl, some of the possible negative consequences of that sprawl, and we'll offer some advice on how to reduce or even avoid sprawl.

What is Tool Sprawl?

Let's begin by declaring what observability tool sprawl is not. It is not simply having more than one observability tool in your stack.

A carpenter needs both a saw and a hammer to build a house. While it may be possible to pound in a nail with a saw, it's inefficient and potentially dangerous. And you'd be hard-pressed to cut lumber with a hammer. The trick is to have the right tools for the right tasks. Each tool has a specific role to play in building the house.

Sprawl, then, is having more tools than required. Sean McDermott, a consultant with decades of experience helping companies manage IT software sprawl, defines it as “the redundancy, wasteful spending and system complexity associated with the unnecessary purchase of new IT tools, and the use or misuse of stagnant, legacy systems."

Observability Seems Particularly Prone to Sprawl

Observability efforts seem particularly vulnerable to tool sprawl. In the same CNCF survey, 4% of respondents indicated using more than 15 tools in their observability stack. Several reasons contribute to this.

1. Observability is still early in its development and adoption. Google searches for observability have quadrupled since mid-2020. A recent survey showed that 58% of respondents were considered "beginners" in their observability journey, while another survey showed that 95% of organizations expected to have a fully implemented observability practice by 2025.

As a result, there is still a lot of uncertainty about best practices. Combine that uncertainty with the large number of new and established vendors attempting to secure their share of the rapidly expanding observability market. and you have a perfect environment for tool sprawl.

2. Observability is not easy, and the explosion of containerized microservices increases the difficulty exponentially. The amount of telemetry data generated by these systems is staggering and still growing. Organizations that adopted a single platform approach to observability (e.g., send everything to Splunk) soon found the consumption-based pricing models of some of those platforms to be prohibitive and went searching for solutions to reduce costs, which often meant adopting another tool.

3. Log, metrics, and traces are often referred to as the three pillars of observability. But these are very different types of data, and tools often specialize in processing and analyzing one or the other. That's fine — remember our earlier analogy about trying to pound a nail wwith a saw — there is nothing wrong with using the best tool for a task. But observability applications often are actually a suite of tools: agents deployed on servers for gathering the data, some sort of system for storing the gathered data, and an application for searching and analyzing the stored data. Often these components are vendor-specific, which sometimes results in multiple data gathering and forwarding apps running on each server sending data to their own vendor-specific backend.

The Consequences of Tool Sprawl

Tool sprawl results in inefficiencies, unnecessary expenses and increased risk. Common problems include:

■ Underutilization of tools that are perfectly capable of doing the job currently handled by another tool.

■ Siloization of teams as groups become entrenched in the idea that only their tool can meet their needs.

■ Increased and unnecessary complexity of the observability pipeline, resulting in greater effort by SREs to ensure that everything continues functioning.

■ Reduced efficiency of the systems being observed as more of their resources are consumed by the tools observing them.

■ Increased downtime due to longer times required to diagnose and repair problems (This is particularly ironic given the purpose of implementing an observability practice).

■ Wasted budget on license renewals, training, implementation, consulting, and integration.

■ Increased security risk as every tool represents a possible attack vector.

Tips for Reducing or Avoiding Sprawl

Thankfully, tool sprawl is neither inevitable nor incurable if it has already infected your observability practice. Here are a few tips.

Know your needs

Identify the specific needs of your team and organization: The first step is to clearly define the goals and objectives of your observability practice and to determine the specific data sources, visualization and analysis tools, and integration processes needed to meet these goals. This will help you to identify the specific tools that will be required and to avoid selecting tools that are not well-suited to your needs.

Evaluate the tools you are using

The next step is to carefully evaluate the tools you are currently using and to determine whether they are meeting the needs of your team and organization. This may involve conducting surveys or user interviews to gather feedback and analyzing data to assess the effectiveness of the tools. Look especially for opportunities for consolidation.

Adopt tools that support open standards

Perhaps the worst mistake an organization can make is adopting tools that do not support open standards. Open standards help organizations avoid vendor lock-in, enabling them to more easily swap out tools that no longer meet their needs. When an organization is locked in to a particular vendor due to the effort required to completely rework its entire observability pipelines and platforms, the organization is at the mercy of the vendor when it comes to contract renewals.

OpenTelemetry has become the standard for telemetry data. The open-source project provides a set of standardized vendor-agnostic SDKs, APIs, and tools for ingesting, transforming, and sending data to an Observability backend (i.e., open source or commercial vendor). At a minimum, you should ensure that any observability backend you adopt supports OpenTelemetry.

Next Steps

Reducing tool sprawl can be painful, especially if you have previously invested in tools whose makers view vendor lock-in as a business strategy. However, the results are worth the effort, assuming you follow the advice above. You are likely to see substantially reduced costs, improved efficiency, faster time to insights, and better visibility into your systems.

Anurag Gupta is Co-Founder of Calyptia
Share this

The Latest

March 18, 2024

Gartner has highlighted the top trends that will impact technology providers in 2024: Generative AI (GenAI) is dominating the technical and product agenda of nearly every tech provider ...

March 15, 2024

In MEAN TIME TO INSIGHT Episode 4 - Part 1, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at Enterprise Management Associates (EMA) discusses artificial intelligence and network management ...

March 14, 2024

The integration and maintenance of AI-enabled Software as a Service (SaaS) applications have emerged as pivotal points in enterprise AI implementation strategies, offering both significant challenges and promising benefits. Despite the enthusiasm surrounding AI's potential impact, the reality of its implementation presents hurdles. Currently, over 90% of enterprises are grappling with limitations in integrating AI into their tech stack ...

March 13, 2024

In the intricate landscape of IT infrastructure, one critical component often relegated to the back burner is Active Directory (AD) forest recovery — an oversight with costly consequences ...

March 12, 2024

eBPF is a technology that allows users to run custom programs inside the Linux kernel, which changes the behavior of the kernel and makes execution up to 10x faster(link is external) and more efficient for key parts of what makes our computing lives work. That includes observability, networking and security ...

March 11, 2024

Data mesh, an increasingly important decentralized approach to data architecture and organizational design, focuses on treating data as a product, emphasizing domain-oriented data ownership, self-service tools and federated governance. The 2024 State of the Data Lakehouse report from Dremio presents evidence of the growing adoption of data mesh architectures in enterprises ... The report highlights that the drive towards data mesh is increasingly becoming a business strategy to enhance agility and speed in problem-solving and innovation ...

March 07, 2024
In this digital era, consumers prefer a seamless user experience, and here, the significance of performance testing cannot be overstated. Application performance testing is essential in ensuring that your software products, websites, or other related systems operate seamlessly under varying conditions. However, the cost of poor performance extends beyond technical glitches and slow load times; it can directly affect customer satisfaction and brand reputation. Understand the tangible and intangible consequences of poor application performance and how it can affect your business ...
March 06, 2024

Too much traffic can crash a website ... That stampede of traffic is even more horrifying when it's part of a malicious denial of service attack ... These attacks are becoming more common, more sophisticated and increasingly tied to ransomware-style demands. So it's no wonder that the threat of DDoS remains one of the many things that keep IT and marketing leaders up at night ...

March 05, 2024

Today, applications serve as the backbone of businesses, and therefore, ensuring optimal performance has never been more critical. This is where application performance monitoring (APM) emerges as an indispensable tool, empowering organizations to safeguard their applications proactively, match user expectations, and drive growth. But APM is not without its challenges. Choosing to implement APM is a path that's not easily realized, even if it offers great benefits. This blog deals with the potential hurdles that may manifest when you actualize your APM strategy in your IT application environment ...

March 04, 2024

This year's Super Bowl drew in viewership of nearly 124 million viewers and made history as the most-watched live broadcast event since the 1969 moon landing. To support this spike in viewership, streaming companies like YouTube TV, Hulu and Paramount+ began preparing their IT infrastructure months in advance to ensure an exceptional viewer experience without outages or major interruptions. New Relic conducted a survey to understand the importance of a seamless viewing experience and the impact of outages during major streaming events such as the Super Bowl ...