Operations | Monitoring | ITSM | DevOps | Cloud

…and why it matters even more in the age of AI-generated code Software development is changing fast. Thanks to tools like GitHub Copilot, Cursor, and Windsurf, developers can now generate large chunks of code in seconds. Product velocity is exploding. Startups are shipping faster than ever before. But there’s a catch: More code ≠ better code.

Logs are a key part of building and running software, but managing them can get complicated fast. As your apps grow and generate logs from many sources, choosing the right tool to store, search, and analyze those logs becomes important. Graylog and Loki are two popular options, each with a different way of handling logs. In this blog, we’ll break down the main differences between Graylog and Loki, how they work, and which types of projects they suit best.

A CDN delivers your content around the world, making sure users get it quickly and reliably. When it slows down or goes offline, users notice right away. Good CDN monitoring gives your team the information needed to fix issues before they affect users. This guide explains the basics of CDN monitoring and shows practical ways to set it up.

The rapid growth in OpenStack installation and orchestration tools that we have seen in recent years has effectively established OpenStack as the world’s leading open source cloud platform. Projects like Sunbeam or Kolla Ansible, for example, are effectively transforming OpenStack into yet another user application.

At first glance, AWS Config seems like a no-brainer for tracking changes, catching misconfigurations, and proving compliance. But beneath the surface, Config pricing can get surprisingly intricate. Costs don’t just depend on the number of resources you monitor. They also hinge on how often those resources change, how many rules you evaluate, and how you manage historical data. In this guide, we’ll demystify AWS Config pricing.

Platform engineering has emerged as the natural progression of DevOps—not a replacement as some may think, but rather more of a refinement. While DevOps broke down silos and encouraged shared responsibility, it often left teams fending for themselves across sprawling infrastructure stacks. Developers were promised autonomy, but were instead overwhelmed by the burden of managing CI/CD, security, observability, infrastructure provisioning, and more.

Long before ORMs, LINQ, and high-level abstractions became common in the.NET ecosystem, there was ADO.NET—raw, fast, and unapologetically hands-on. It was the original data access layer for developers who wanted complete control. And two decades later, it’s still the tool of choice when performance, precision, and transparency matter most. But how does it deliver that control?

In our post, 9 Continuous Delivery Tools For Reliable Releases, we explored why continuous delivery is critical to building robust development pipelines — and how it helps teams deliver customer value while boosting the bottom line. Today, we’re diving into the next evolution of that pipeline: continuous deployment. Today’s technology companies need to release quality features quickly and put them in users’ hands even quicker.

VPC Flow Logs come with a default format that gives you basic network traffic details. But you can tweak the format to capture exactly what you need. This can lower costs, speed up processing, and make your logs fit better with what you’re trying to monitor. If you want to improve security, keep an eye on performance, or save money, adjusting your VPC logs can make a big difference. Let’s take a look at some practical ways to customize your logs beyond the default settings.