With containerized workloads now the norm, and Kubernetes the chosen method for orchestration, new ways of operating and managing the underlying infrastructure have emerged. In this Kubernetes-first world, the goal is to not have to think about managing compute or storage.
Just how smart is your storage management? Storage is one of the most promising ways to shift from the "more is better" philosophy to the "work smarter" philosophy. What do I mean by that? Historically, IT managers who needed more storage responded in the most obvious way: they bought more. Then they deployed it, integrated it, and waited until the problem recurred.
Current IT monitoring software lacks the necessary metrics for minimizing downtime for systems and applications. Most provide system and application metrics but there is much more than this required for properly monitoring your infrastructure. With eBPF there is a technological advancement that allows monitoring software to provide rich information from the Linux kernel and present it.
Amazon Elastic File System (EFS) provides shared, persistent, and elastic storage in the AWS cloud. Like Amazon S3, EFS is a highly available managed service that scales with your storage needs, and it also enables you to mount a file system to an EC2 instance, similar to Amazon Elastic Block Store (EBS).
In Part 1 of this series, we looked at EFS metrics from several different categories—storage, latency, I/O, throughput, and client connections. In this post, we’ll show you how you can collect those metrics—as well as EFS logs—using built-in and external tools.
In Part 1 of this series, we looked at the key EFS metrics you should monitor, and in Part 2 we showed you how you can use tools from AWS and Linux to collect and alert on EFS metrics and logs. Monitoring EFS in isolation, however, can lead to visibility gaps as you try to understand the full context of your application’s health and performance.
A Storage Area Network (SAN) is a specialized, high-speed network that provides block-level network access to storage. SANs are typically composed of hosts, switches, storage elements, and storage devices that are interconnected using a variety of technologies, topologies, and protocols. Each computer on the network can access storage on the SAN as if they are local disks connected directly to the computer.
At Taloflow we recently launched a way for companies migrating from AWS/GCP/Azure to 3rd party object storage providers like Storj to receive an objective TCO analysis of all the switching and storing costs associated. But what exactly is object storage - and how does it compare to block storage? For both, we will cover the technical description, benefits, and application use-cases.
In this article, we dig deeper into why we decided to extend support for ClickHouse as a storage backend for SigNoz and the efficiency gains we achieved using it.
