Operations | Monitoring | ITSM | DevOps | Cloud

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.

Industry analyst recognition means something different from an award. GigaOm does not hand out trophies. They evaluate products against a defined capability framework and tell the market where vendors actually stand. By that measure, Kubex has been named a Leader in two of GigaOm’s 2026 Radar Reports: Kubernetes Resource Management and Cloud Resource Optimization. In the Kubernetes report, we are positioned as an Outperformer. In Cloud Resource Optimization, a Fast Mover.

AI coding agents are fast. They generate functions, refactor modules, and wire up boilerplate faster than any human. What they don’t do by default is enforce the conventions a specific team has agreed on: the lint rules, the review patterns that senior engineers flag on every PR. A generated diff looks clean until someone runs CI or reads it carefully.

Netdata has always collected database metrics: connections, throughput, replication lag, buffer cache hit ratios, and so on. These tell you that something is wrong, but they don’t tell you why. When your PostgreSQL response time spikes, the metric alone doesn’t tell you which query is responsible. For that, you’ve traditionally needed to SSH into the box, connect to the database, and run diagnostic queries manually. Or set up a separate database monitoring tool entirely.