Operations | Monitoring | ITSM | DevOps | Cloud

See how DNS turns a domain name into an IP address step by step, and why fast resolution keeps your pages loading quickly for users all around the world.

See how BGP announcements, replacements, and withdrawals shift reachability across networks you don’t own, and why outside-in monitoring catches them.

Last week, dozens of schools found out their certificate authority was being distrusted and they needed to replace all of their certificates in a few days. We wanted to know how we’d handle it if our own CA went away, and how long it would take. So we tried it with one of our other products. It has 6 certificates from Let’s Encrypt, deploying to 18 targets across Windows IIS, Linux nginx, Elasticsearch, and a mail server. Then we wargamed it: “Let’s Encrypt is being distrusted.

A critical application slows overnight. Monitoring identifies an unhealthy component, and an engineer finds a familiar remedy: restart a service. The command takes seconds. Determining whether the restart will restore the application or disrupt another dependency takes far longer. That is the real challenge in enterprise incident remediation. Most IT teams already know how to automate a task.

A sovereign cloud is a cloud computing environment designed to keep data, infrastructure, and operations under the control of a specific country or jurisdiction. It helps organizations maintain control over who can access their data and how it is managed. Depending on the provider and service, this may include storing data within national borders, using locally governed infrastructure, and ensuring that operations comply with regional regulations.

A back-office server that runs out of disk space can interrupt an important internal workflow. A process that stops on a staging host can delay development. Although workloads like these might not require application-level instrumentation, teams still need to know when the hosts that support them require attention. Without a monitoring solution tailored to these requirements, teams have to apply more monitoring than the workload needs, maintain a separate tool, or accept a gap in visibility.

We set out to understand how customers were using Coralogix from outside the web app. Olly answers questions about a system in plain language. Coding agents query logs, examine traces, read metrics and configure the platform through the Coralogix CLI and MCP server. We wanted to see how much of this was becoming part of everyday work. In the week of 20–26 October, 39% of Coralogix sessions included Olly, the CLI or MCP.

AI has made life easier for us developers. Dozens of AI tools are getting more advanced every day, shortening and speeding up the development cycle. Converting an idea into a concrete MVP is faster than ever before. Intelligent models turn your ideas into a working project with just a few prompts. End users or product owners can see the application, use the beta version, and give feedback on the spot.

Having spent significant time working with the Network Observability Deployment Engine (NODE), I can confidently say that modernizing network observability does not have to feel like black magic. NODE simplifies how we deploy, scale, and manage complex network observability environments. Whether you're working with Kubernetes for the first time or streamlining an enterprise monitoring stack, NODE brings structure and clarity to the setup process. At its core, NODE relies on two main building blocks.

How long does it take your service desk to rule the proxy in or out when a user says a site won't load? The proxy carries every outbound web request in most companies, and it still tends to be checked last. So service desks guess, even though the proxy has already logged what happened to that request. For a lot of those companies, the proxy is Squid. It has cached pages and enforced web policy for close to three decades, and it logs every request it touches.