In at this time’s quickly evolving observability and safety use circumstances, the idea of “shifting left” has moved past simply software program improvement. With the constant and speedy rise of information volumes throughout logs, metrics, traces, and occasions, organizations are required to be much more considerate in efforts to show chaos into management in relation to understanding and managing their streaming knowledge units. Groups are striving to be extra proactive within the administration of their mission vital manufacturing programs and want to realize far earlier detection of potential points. This strategy emphasizes shifting historically late-stage actions — like seeing, understanding, reworking, filtering, analyzing, testing, and monitoring — nearer to the start of the info creation cycle. With the expansion of next-generation architectures, cloud-native applied sciences, microservices, and Kubernetes, enterprises are more and more adopting Telemetry Pipelines to allow this shift. A key factor on this motion is the idea of information tiering, a data-optimization technique that performs a vital function in aligning the cost-value ratio for observability and safety groups.
The Shift Left Motion: Chaos to Management
“Shifting left” originated within the realm of DevOps and software program testing. The concept was easy: discover and repair issues earlier within the course of to cut back danger, enhance high quality, and speed up improvement. As organizations have embraced DevOps and steady integration/steady supply (CI/CD) pipelines, the advantages of shifting left have change into more and more clear — much less rework, quicker deployments, and extra strong programs.
Within the context of observability and safety, shifting left means undertaking the evaluation, transformation, and routing of logs, metrics, traces, and occasions very far upstream, extraordinarily early of their utilization lifecycle — a really totally different strategy compared to the normal “centralize then analyze” methodology. By integrating these processes earlier, groups cannot solely drastically scale back prices for in any other case prohibitive knowledge volumes, however may even detect anomalies, efficiency points, and potential safety threats a lot faster, earlier than they change into main issues in manufacturing. The rise of microservices and Kubernetes architectures has particularly accelerated this want, because the complexity and distributed nature of cloud-native functions demand extra granular and real-time insights, and every localized knowledge set is distributed when in comparison with the monoliths of the previous.
This results in the rising adoption of Telemetry Pipelines.
What Are Telemetry Pipelines?
Telemetry Pipelines are purpose-built to allow next-generation architectures. They’re designed to provide visibility and to pre-process, analyze, remodel, and route observability and safety knowledge from any supply to any vacation spot. These pipelines give organizations the excellent toolbox and set of capabilities to manage and optimize the circulation of telemetry knowledge, guaranteeing that the appropriate knowledge reaches the appropriate downstream vacation spot in the appropriate format, to allow all the appropriate use circumstances. They provide a versatile and scalable method to combine a number of observability and safety platforms, instruments, and providers.
For instance, in a Kubernetes setting, the place the ephemeral nature of containers can scale up and down dynamically, logs, metrics, and traces from these dynamic workloads must be processed and saved in real-time. Telemetry Pipelines present the potential to combination knowledge from numerous providers, be granular about what you wish to do with that knowledge, and finally ship it downstream to the suitable finish vacation spot — whether or not that’s a conventional safety platform like Splunk that has a excessive unit price for knowledge, or a extra scalable and value efficient storage location optimized for giant datasets long run, like AWS S3.
The Position of Knowledge Tiering
As telemetry knowledge continues to develop at an exponential price, enterprises face the problem of managing prices with out compromising on the insights they want in actual time, or the requirement of information retention for audit, compliance, or forensic safety investigations. That is the place knowledge tiering is available in. Knowledge tiering is a technique that segments knowledge into totally different ranges (tiers) primarily based on its worth and use case, enabling organizations to optimize each price and efficiency.
In observability and safety, this implies figuring out high-value knowledge that requires quick evaluation and making use of much more pre-processing and evaluation to that knowledge, in comparison with lower-value knowledge that may merely be saved extra cheaply and accessed later, if essential. This tiered strategy sometimes contains:
- High Tier (Excessive-Worth Knowledge): Vital telemetry knowledge that’s important for real-time evaluation and troubleshooting is ingested and saved in high-performance platforms like Splunk or Datadog. This knowledge may embody high-priority logs, metrics, and traces which might be important for quick motion. Though this could embody loads of knowledge in uncooked codecs, the excessive price nature of those platforms sometimes results in groups routing solely the info that’s actually essential.
- Center Tier (Average-Worth Knowledge): Knowledge that’s necessary however doesn’t meet the bar to ship to a premium, standard centralized system and is as an alternative routed to extra cost-efficient observability platforms with newer architectures like Edge Delta. This may embody a way more complete set of logs, metrics, and traces that provide you with a wider, extra helpful understanding of all the varied issues taking place inside your mission vital programs.
- Backside Tier (All Knowledge): Because of the extraordinarily cheap nature of S3 relative to observability and safety platforms, all telemetry knowledge in its entirety could be feasibly saved for long-term development evaluation, audit or compliance, or investigation functions in low-cost options like AWS S3. That is sometimes chilly storage that may be accessed on demand, however doesn’t must be actively processed.
This multi-tiered structure permits massive enterprises to get the insights they want from their knowledge whereas additionally managing prices and guaranteeing compliance with knowledge retention insurance policies. It’s necessary to remember that the Center Tier sometimes contains all knowledge throughout the High Tier and extra, and the identical goes for the Backside Tier (which incorporates all knowledge from larger tiers and extra). As a result of the associated fee per Tier for the underlying downstream locations can, in lots of circumstances, be orders of magnitude totally different, there isn’t a lot of a profit from not duplicating all knowledge that you just’re placing into Datadog additionally into your S3 buckets, as an example. It’s a lot simpler and extra helpful to have a full knowledge set in S3 for any later wants.
How Telemetry Pipelines Allow Knowledge Tiering
Telemetry Pipelines function the spine of this tiered knowledge strategy by giving full management and adaptability in routing knowledge primarily based on predefined, out-of-the-box guidelines and/or enterprise logic particular to the wants of your groups. Right here’s how they facilitate knowledge tiering:
- Actual-Time Processing: For top-value knowledge that requires quick motion, Telemetry Pipelines present real-time processing and routing, guaranteeing that vital logs, metrics, or safety alerts are delivered to the appropriate device immediately. As a result of Telemetry Pipelines have an agent element, quite a lot of this processing can occur regionally in an especially compute, reminiscence, and disk environment friendly method.
- Filtering and Transformation: Not all telemetry knowledge is created equal, and groups have very totally different wants for the way they might use this knowledge. Telemetry Pipelines allow complete filtering and transformation of any log, metric, hint, or occasion, guaranteeing that solely probably the most vital data is distributed to high-cost platforms, whereas the complete dataset (together with much less vital knowledge) can then be routed to extra cost-efficient storage.
- Knowledge Enrichment and Routing: Telemetry Pipelines can ingest knowledge from all kinds of sources — Kubernetes clusters, cloud infrastructure, CI/CD pipelines, third-party APIs, and so forth. — after which apply numerous enrichments to that knowledge earlier than it’s then routed to the suitable downstream platform.
- Dynamic Scaling: As enterprises scale their Kubernetes clusters and enhance their use of cloud providers, the quantity of telemetry knowledge grows considerably. Resulting from their aligned structure, Telemetry Pipelines additionally dynamically scale to deal with this rising load with out affecting efficiency or knowledge integrity.
The Advantages for Observability and Safety Groups
By adopting Telemetry Pipelines and knowledge tiering, observability and safety groups can profit in a number of methods:
- Value Effectivity: Enterprises can considerably scale back prices by routing knowledge to probably the most acceptable tier primarily based on its worth, avoiding the pointless expense of storing low-value knowledge in high-performance platforms.
- Quicker Troubleshooting: Not solely can there be some monitoring and anomaly detection throughout the Telemetry Pipelines themselves, however vital telemetry knowledge can be processed extraordinarily shortly and routed to high-performance platforms for real-time evaluation, enabling groups to detect and resolve points with a lot higher pace.
- Enhanced Safety: Knowledge enrichments from lookup tables, pre-built packs that apply to numerous identified third-party applied sciences, and extra scalable long-term retention of bigger datasets all allow safety groups to have higher means to seek out and determine IOCs inside all logs and telemetry knowledge, bettering their means to detect threats early and reply to incidents quicker.
- Scalability: As enterprises develop and their telemetry wants increase, Telemetry Pipelines can naturally scale with them, guaranteeing that they’ll deal with rising knowledge volumes with out sacrificing efficiency.
All of it begins with Pipelines!
Telemetry Pipelines are the core basis to sustainably managing the chaos of telemetry — and they’re essential in any try to wrangle rising volumes of logs, metrics, traces, and occasions. As massive enterprises proceed to shift left and undertake extra proactive approaches to observability and safety, we see that Telemetry Pipelines and knowledge tiering have gotten important on this transformation. By utilizing a tiered knowledge administration technique, organizations can optimize prices, enhance operational effectivity, and improve their means to detect and resolve points earlier within the life cycle. One further key benefit that we didn’t give attention to on this article, however is necessary to name out in any dialogue on fashionable Telemetry Pipelines, is their full end-to-end help for Open Telemetry (OTel), which is more and more turning into the trade customary for telemetry knowledge assortment and instrumentation. With OTel help built-in, these pipelines seamlessly combine with various environments, enabling observability and safety groups to gather, course of, and route telemetry knowledge from any supply with ease. This complete compatibility, mixed with the flexibleness of information tiering, permits enterprises to realize unified, scalable, and cost-efficient observability and safety that’s designed to scale to tomorrow and past.
To be taught extra about Kubernetes and the cloud native ecosystem, be part of us at KubeCon + CloudNativeCon North America, in Salt Lake Metropolis, Utah, on November 12-15, 2024.