Operations | Monitoring | ITSM | DevOps | Cloud

If you’re running infrastructure on Azure, you’ve probably dealt with the split between your Azure-native monitoring and the rest of your stack. Your VMs, databases, and Kubernetes clusters generate platform metrics through Azure Monitor, but those metrics live in a separate world from the OS-level, application, and on-prem metrics you’re already watching in Netdata.

This guide will help you understand Azure Storage costs – including tips and best practices to optimize your storage pricing. If you have trouble understanding Microsoft Azure Storage costs, you’re not alone. Azure Storage options can feel like a multi-layered maze of storage account types, tiers, pricing pages, specs — and then some. Yet, understanding your cloud cost drivers begins with looking at where your money goes. Only then can you tell if you are getting value for your money.

The new Query Plan Compare feature in Redgate Monitor helps PostgreSQL DBAs see when the optimizer switches plans for the same query, and understand why, so they can diagnose sudden performance changes faster.

As far back as 2020, Barclays found that 43% of enterprise CIOs were already planning to bring workloads back from the public cloud to on-premises or private cloud infrastructure1. Since then, IDC, Gartner and a host of vendor surveys have tracked an increase in this intention.

It's 2:47 AM. PagerDuty fires. You open a Slack alert and see: p99 latency spike on checkout-service. You SSH into the host, check dashboards in four tabs, grep logs for the last 20 minutes, and eventually find a slow query introduced in a deploy six hours ago. It took 34 minutes. You resolved it, w Prathamesh works as an evangelist at Last9, runs SRE stories - where SRE and DevOps folks share their stories, and maintains o11y.wiki - a glossary of all terms related to observability.

So far in this deployment series, you’ve: At this point, you can deploy your app. The question is: do you really want to keep doing it manually? Welcome to CI/CD — where deployments stop being an event and start becoming a system.

> Standard OTel.NET instrumentation captures headers, status codes, and timing — not request or response bodies. Here's how to add body capture to your traces while keeping PHI out of your observability backend. Prathamesh works as an evangelist at Last9, runs SRE stories - where SRE and DevOps folks share their stories, and maintains o11y.wiki - a glossary of all terms related to observability.

Now comes the part that makes your application…online or real. Step 3 is where your application gets a proper home address, becomes accessible to users, and stops living as a collection of IP addresses and ports that only you and your team understand. Welcome to DNS, domains, and yep, go live.

GCP's load balancer silently rewrites your traceparent header, orphaning spans in any OTLP backend. Here's the custom propagator that fixes it. Prathamesh works as an evangelist at Last9, runs SRE stories - where SRE and DevOps folks share their stories, and maintains o11y.wiki - a glossary of all terms related to observability.