The latest News and Information on DevOps, CI/CD, Automation and related technologies.
Adopting Kubernetes and service-based architecture can bring many benefits to organizations – teams move faster and applications scale more easily. However, visibility into cloud costs is made more complicated with this transition. This is because applications and their resource needs are often dynamic, and teams share core resources without transparent prices attached to workloads.
We are excited to announce a new partnership with Microsoft Azure, which has enabled us to build streamlined experiences for purchasing, configuring, and managing Datadog directly inside the Azure portal. This first-of-its-kind integration of a third-party service into a public cloud provider reduces the learning curve for using Datadog to monitor the health and performance of your applications in Azure—and sets you up for a successful cloud migration or modernization.
Istio is a service mesh that enables teams to manage traffic in distributed workloads without modifying the workloads themselves, making it easier to implement load balancing, canarying, circuit breakers, and other design choices. Versions of Istio prior to 1.5 adopted a microservices architecture and deployed each Istio component as an independently scalable Kubernetes pod. Version 1.5 signalled a change in course, moving all of its components into a single binary, istiod.
Earlier this year, we shared the certified Ansible Collection for Sensu Go, which makes it easy to automate your monitoring and achieve real-time visibility into auto-scaling infrastructure. Now that Sensu Go 6 has been released, we’ll share the latest updates on the Collection, including the management aspects of Sensu Go 6, with a focus on the structure of Ansible playbooks in the Sensu Go 6 world.
Legacy generations of networks have predominately provided services with best-effort delivery. While this has worked for voice, text and best- effort broadband services, end users are hampered with buffering, delays, and drops as the demand for feature-rich services continues to grow.
Inodes, speculated to be short for “index nodes,” have been around since the introduction of the first UNIX file system around the late 1970s. They were adopted into Linux in the 90s—and for good reason. They’re an excellent way to keep track of how your files are stored, and the method many systems are still based on today.
