Logz.io has recently launched its Smart Tiering solution, which gives you the flexibility to place data on different tiers to optimize cost, performance and availability. Our mission has been to make Smart Tiering a multi-cloud and multi-region service. As part of this launch, we are glad to announce that the Historical Tier now supports Microsoft Azure Blob Storage, alongside AWS S3.
2020 is coming to an end, and we can definitely say it was an amazing year for Cortex. Dare I say, it has been the best year so far! It was a year filled with huge milestones for the project. We released the first major version 1.0.0 back in April, along with introducing some versioning rules to avoid breaking changes to our users.
Do you really ever know how much Azure Storage you are consuming or how many Azure Storage Blobs you have in each of your Storage Accounts? Perhaps you just need an overview of your Azure Storage Account Consumption, including things like the number of Blobs per storage account, Number of Containers, and the Azure Blob Storage Capacity used. All this information is quite easy to gather from one of the several reports available in Cloud Storage Manager.
Sematext Logs is a Log Management-as-a-service. Think of it as your own central location for logs in the cloud. If you prefer or need to keep logs in your own environment instead of shipping it to the cloud Sematext Enterprise, designed to run on your own infrastructure, makes that possible. You can collect logs from any part of your software stack or infrastructure, IoT devices, network hardware, and much more.
Cloud-native is the ultimate buzzword lately. So, is “cloud-native storage” just an attempt to grab on to this concept, hoping for a little boost? Actually, there is something more to it, and I’ll unpack that here. The premise of cloud-native storage is simple: its native habitat is a Kubernetes cluster. When we design with the assumption that a technology will exist in Kubernetes, we get to look around and see what functionalities already exist in that system.
Data in your enterprise organization doubles almost every year, and data multiplication at this pace requires boosting your storage capacity. But when the magnitude of data size increases, latency or performance lags are inevitable. You can outsource your storage infrastructure management to a third-party, but this might place your data at risk from security threats. The correct approach is to install a dedicated storage monitoring solution in your network. Fair enough! But is it essential?
Azure storage has provided companies with a way to store almost limitless amount of data. But just like kids in a candy store this can get out of hand, and expensive. Being able to store as much data as you want is great, however it is something that can grow to a point where you are spending more on storage than you actually need.
Recently we had one of our clients inform us that he used Cloud Storage Manager to find which were the largest Blobs in his Azure Storage Containers. Here is a quick run down to show one of the many reports on your Azure Blob consumption that you can run with Cloud Storage Manager.
"A long time ago in a data centre far, far away.... Our first episode takes us back to the early days of launching Civo, where we had a fledgling Ceph cluster with a bunch of SSDs in each. Those were darker times, in the early days of OpenStack. As time went by the cluster grew, new bigger nodes were added along with bigger disks.
