Kubecon 2022: Industry Insights on Observability Data

    4 MIN READ

    In case you missed it, last month, we had the pleasure of setting foot in Detroit, Michigan, for another KubeCon. 

    The Mezmo team joined 7,000+ people in the Huntington Place Exhibit Hall in the Motor City for Kubecon + CloudNativeCon NA 2022 from October 24-28. Visitors from the cloud-native and Kubernetes communities came from all over the world to network, sample products, and learn about solutions to some of the world's most pertinent software problems while furthering the education and advancement of cloud-native computing.  

    While there, we had a chance to survey attendees to learn more about observability data concerns while learning more about how organizations currently use it. 

    We appreciate the valuable insights from those that chose to participate, and we want to highlight a few key takeaways from our results.

    Let's dive in. 

    Key Insights 

    When it comes to deriving value from their observability data, respondents listed the following as their main issues: 

    • Almost half of the survey respondents reported that extracting metrics from their logs is challenging because of the lack of structure. 
    • 28% of respondents reported generating more data than they could afford to send to their observability tools. 
    • 22% of respondents reported that their data is often in an incorrect or unusable format, linking to structured vs. unstructured data. 
    • 19% of respondents reported that their data often needs more critical contextual elements. 

    Other issues included users wasting too much time with OpenTelemetry configurations and teams wanting access to observability data but not being able to receive it. 

    We also asked if respondents are using OpenTelemetry. 21% of respondents said that most of their observability data is standardized on OpenTelemetry, and another 37% responded that they are evaluating using it. 

    These results indicate that OpenTelemetry adoption is reaching a critical mass, with 58% already using or evaluating the standard.

    Do More With Your Telemetry Data 

    There were many conversations about the value an observability pipeline provides and the general desire to evolve how companies access and control telemetry data. Most users are interested in using an observability pipeline to gain the maximum value from their data to meet various business needs. 

    Tip: Get an in-depth understanding of observability pipelines and how they work with this primer

    With an observability pipeline, you gain a centralized way of interacting with telemetry data from across the business, ensuring that it's available to you where you want, in whichever format you need to drive crucial decisions.

    Additionally, an observability pipeline can help manage your budget, reducing spending and increasing efficiency. 

    Tip: For more information on the factors you should consider when evaluating an observability pipeline for your business, check out our Decision Maker's Guide to Choosing an Observability Pipeline

    We built our Observability Pipeline on the foundation of first-generation pipeline solutions emphasizing data aggregation and routing. Our open platform supports various data sources and destinations. It has several processors to help you shape data (such as sampling, deduping, and filtering) to quickly filter the signal from the noise. With easy-to-configure routing rules, you can optimize your data flow to help reduce spending. Organizations using Observability Pipeline store only what they need and pay for what they use, rather than having to store and pay for everything.

    The result is more actionable data, improved efficiency, and faster decision-making at a reduced price. 

    Take the time to learn more about Observability Pipeline by checking out our blog post on the launch. To see it in action, request a demo with our team. 

    TéJaun RiChard


    TéJaun is the Content Manager at Mezmo. He enjoys video games, traveling, photography, language learning, and front-end development when he's not working.