Operations | Monitoring | ITSM | DevOps | Cloud

“Stop watching me.” That’s an actual message a user typed into a search bar, captured during session monitoring. They weren’t talking to customer support. They were talking to the algorithm. It sounds absurd until you realize how common this is. When users believe a human is behind your personalization system, attributing consciousness to your automated algorithms, everything changes. Their behavior becomes erratic. Your conversions tank. And nobody talks about it.

As part of our big deploy that added ping and TCP monitoring, we’ve also shipped a small, but often requested feature: you can now choose the frequency of the check we run. By default, we check your website for uptime every minute. The Lighthouse check runs daily. Using our new feature, you can now, for instance, choose that the uptime check should run every 2 minutes, and the Lighthouse check every 5 days. You can choose the frequency at the settings of the check.

Whether you sell consumer goods, ship freight, manufacture vehicles, process payments, underwrite insurance, or manage hospital claims, your business depends on the same thing: order to cash. Orders are created, fulfilled, invoiced, and paid. In principle, it should be simple. In practice, the process is riddled with breaks. Most companies believe they are covered. They run ERP systems like SAP. They use EDI gateways such as Sterling.

The irony isn't lost on us - observability platforms are built to be proactive about system health, yet when it comes to managing observability costs themselves, teams are forced to be reactive. Today, that changes with Cost Meter, now live in our platform. Cost Meter transforms observability spend management from a monthly billing surprise into a proactive, data-driven process with hourly aggregated metrics that give you complete visibility into your telemetry ingestion patterns.

If you're thinking something and you can think it in a generic English sentence, you can write that query and execute it with trace operators. That's basically it.

A service catalog gives teams a shared view of their systems—what services exist, who owns them, how dependencies are structured, and the SLAs that guide expectations. It’s an important part of development infrastructure because it helps everyone speak the same language about services. Service catalog observability builds on that foundation.