Watch on YouTube
Watch on Vimeo
Controlling telemetry data (logs, metrics, events, traces) has been a fundamental challenge as the data volumes increase and budgets decrease. Data’s continuous growth and dynamic nature cause DevOps and security teams to lose confidence in the data captured. On the other hand application developers are under pressure to minimize log generation to limit observability costs but are held responsible when the absence of logs increases MTTx for debugging and troubleshooting. This session discusses how Mezmo telemetry pipelines help organizations have confidence in their data by enabling them to understand telemetry data, optimize it for observability and security, and deliver responsiveness by detecting aberrations while data is in motion. This approach ensures cost control, business insights, and faster incident response.
The presentation by Mezmo at AppDev Field Day, led by Tucker Callaway, CEO, and supported by Bill Meyer, a principal sales engineer, focused on the challenges and solutions related to managing telemetry data (logs, metrics, events, traces) in organizations. Tucker introduced Mezmo’s role in solving observability problems since 2015, highlighting their experience with large-scale data handling and their partnership with major organizations like IBM Cloud.
The core discussion revolved around the increasing volume of telemetry data and the associated costs, which do not correspond to the value derived from the data. Mezmo addresses this issue through their telemetry pipelines, which allow organizations to take control of their telemetry data by enabling functionalities such as understanding, optimizing, and responding to data in real-time. This approach facilitates cost control, enhances business insights, and accelerates incident response times.
Tucker elaborated on the concept of telemetry data, emphasizing its unique characteristics compared to business data. He introduced the telemetry pipeline as a new control point for enterprises, enabling them to manage data effectively by routing, normalizing, enriching, and transforming it according to their needs. This system prevents over-reliance on external vendors and promotes internal management of data, ensuring compliance and reducing costs.
The presentation also touched on the challenges application developers face in balancing the generation of logs with observability costs and the pressures of debugging and troubleshooting. Mezmo’s solution helps bridge the communication gap between developers and platform engineers/SREs, facilitating better data management and operational efficiency.
Bill Meyer contributed by discussing the technical aspects of Mezmo’s platform, including data profiling, in-stream data aggregation, and dynamic adjustments to data handling in response to changes in the system or data structure. He also highlighted the importance of owning and understanding telemetry data to leverage it fully for operational and business insights.
Personnel: Bill Meyer, Tucker Callaway
Watch on YouTube
Watch on Vimeo
In this demo by Mezmo, you will learn steps DevOps, SREs, and Platform Engineers can take to understand their telemetry data (logs, metrics, traces, events) by data profiling, optimize it for cost and volume for observability platforms, and respond to changing application context using alerts on data-in-motion or routing data through alternate paths in case of any incident. In this session, you’ll learn how a telemetry pipeline can help lower observability costs, improve security and compliance, and provide business insights to maximize the outcomes of your data strategy.
The session will demonstrate:
Personnel: Bill Meyer
Thank you for being part of the Tech Field Day community! Our mailing list is a great way to stay up to date on our events and technical content, and we appreciate your signup.
We promise that we’ll never spam you, send ads, or sell your information. This list will only be used to communicate with our community about our events and content. And we’ll limit it to no more than one message per week.
Although we only need your email address, it would be nice if you provided a little more information to help us get to know you better!
