Avoiding Tool Sprawl in Your Observability Practice
January 26, 2023

Anurag Gupta

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

December 07, 2023

Part 4 covers OpenTelemetry: Next year, we're going to see more embrace of OpenTelemetry across the entire industry — opening up the future of instrumentation ...

December 06, 2023

Part 3 covers even more on Observability: Observability will move up the organization to support the sustainability and FinOps drive. The combined pressure of needing to adopt more sustainable practices and tackle rising cloud costs will catapult observability from an IT priority to a business requirement in 2024 ...

December 05, 2023

Part 2 covers more on Observability: In 2024, observability platforms will embrace and innovate with new technologies like GenAI for real-time analytics, becoming the fulcrum for digital experience management ...

December 04, 2023

The Holiday Season means it is time for APMdigest's annual list of Application Performance Management (APM) predictions, covering IT performance topics. Industry experts — from analysts and consultants to the top vendors — offer thoughtful, insightful, and often controversial predictions on how APM, Observability, AIOps and related technologies will evolve and impact business in 2024. Part 1 covers APM and Observability ...

November 30, 2023

To help you stay on top of the ever-evolving tech scene, Automox IT experts shake the proverbial magic eight ball and share their predictions about tech trends in the coming year. From M&A frenzies to sustainable tech and automation, these forecasts paint an exciting picture of the future ...

November 29, 2023
The past few years have presented numerous challenges for businesses: a pandemic, rising interest rates, supply chain disruptions, and geopolitical conflict that sent shockwaves across the global economy. But change may finally be on the horizon. According to a recent report by Endava ... a majority of executives confirmed they are feeling optimistic about the current business climate, and as a result, are forecasting larger IT budgets, increased technology funding and rollout, and prioritized innovation in the coming year ...
November 28, 2023

Incident management processes are not keeping pace with the demands of modern operations teams, failing to meet the needs of SREs as well as platform and ops teams. Results from the State of DevOps Automation and AI Survey, commissioned by Transposit, point to an incident management paradox. Despite nearly 60% of ITOps and DevOps professionals reporting they have a defined incident management process that's fully documented in one place and over 70% saying they have a level of automation that meets their needs, teams are unable to quickly resolve incidents ...

November 27, 2023

Today, in the world of enterprise technology, the challenges posed by legacy Virtual Desktop Infrastructure (VDI) systems have long been a source of concern for IT departments. In many instances, this promising solution has become an organizational burden, hindering progress, depleting resources, and taking a psychological and operational toll on employees ...

November 22, 2023

Within retail organizations across the world, IT teams will be bracing themselves for a hectic holiday season ... While this is an exciting opportunity for retailers to boost sales, it also intensifies severe risk. Any application performance slipup will cause consumers to turn their back on brands, possibly forever. Online shoppers will be completely unforgiving to any retailer who doesn't deliver a seamless digital experience ...

November 21, 2023

Black Friday is a time when consumers can cash in on some of the biggest deals retailers offer all year long ... Nearly two-thirds of consumers utilize a retailer's web and mobile app for holiday shopping, raising the stakes for competitors to provide the best online experience to retain customer loyalty. Perforce's 2023 Black Friday survey sheds light on consumers' expectations this time of year and how developers can properly prepare their applications for increased online traffic ...