This post was originally published on Network Computing
When it comes to telemetry data – meaning the logs, metrics, traces, and other information engineers use to monitor applications, manage performance, and troubleshoot outages– more is usually better. But there’s a big caveat: If you fail to manage telemetry data effectively, the data can quickly create more problems than it solves, leading to problems like higher storage costs, difficulty finding the right information when responding to failures, and the risk of exposing sensitive information to unauthorized access.
That’s why telemetry pipelines have become an essential ingredient in modern application observability and performance management strategies and a critical resource when deploying tools like Security Information and Event Management (SIEM) platforms. Telemetry pipelines allow businesses to collect, process, route, and store telemetry data efficiently and at scale.
That, at least, is a high-level overview of what telemetry pipelines do and their importance from both a technical and a business perspective. For a deeper dive, keep reading as we draw on our collective experience in designing, implementing, and managing telemetry pipelines to explain why they’re so valuable and what to look for when building a telemetry pipeline tailored to your organization’s needs.
What are telemetry pipelines, and why do they matter?
Telemetry pipelines are a type
— Read the rest of this post, which was originally published on Network Computing.
