One challenge for the widespread adoption of telemetry pipelines for SRE teams within an organization is knowing where to start when building a pipeline. Faced with a wide assortment of sources, processors, and destinations, setting up a telemetry pipeline can seem like trying to build a Lego set without any instructions. The solution is to provide teams with pre-defined components that provide specific functionality, that they can then use to build pipelines that meet their own requirements.

Alerts that you receive from your observability tool are based on conditions that existed seconds to minutes in the past, because the alert is only triggered after the data has been indexed within the tool. This means that your ability to take timely action in response to the condition is significantly limited, and often your window of opportunity to react is past by the time you receive the alert.

Once upon a time, we thought “Log everything” was the way to go to ensure we have all the data we needed to identify, troubleshoot, and debug issues. But we soon had new problems: cost, noisiness, and time spent sifting through all that log data. Enter log analysis tools to help refine volumes of log data and differentiate signal from the noise to reduce mental toil to process. Log beast tamed, for now….

Once upon a time, we thought “Log everything” was the way to go to ensure we have all the data we needed to identify, troubleshoot, and debug issues. But we soon had new problems: cost, noisiness, and time spent sifting through all that log data. Enter log analysis tools to help refine volumes of log data and differentiate signal from the noise to reduce mental toil to process. Log beast tamed, for now….