Operations | Monitoring | ITSM | DevOps | Cloud

AI agents can interact with the world using tools. Those tools can be generic or specific. For example: Generic: Specific: The most general ones, like “run a bash command” and “read and write files” are built into the agent. More specific ones are provided through Model Control Protocol (MCP) servers. Every tool provided to the agent comes with instructions sent as part of the context.

I recorded a video showing how to properly set up TrackJS for a new production website, specifically CertKit, our new certificate lifecycle management tool. The key to effective error monitoring isn’t just installing the tracking snippet, it’s configuring the system to surface real issues while filtering out the noise. I configure a forwarding domain (errors.certkit.io) to bypass ad blockers that might prevent error reporting.

In e-commerce, we all know that speed = money. I know it, you know it, Amazon knows it, eBay knows it, Shopify knows it, everyone knows it. In this article we’ll see how we can improve the perceived performance of our site’s critical pages, like the Product Details page, the Cart page, the Checkout page. We’re going to use the Speculation Rules API (SRA) to prerender/prefetch them, and also explain how certain frameworks like Next.js offer their own prefetching mechanisms.

When I was working at Shopify, Black Friday and Cyber Monday were our Superbowl. We initiated code-freeze weeks before to make sure merchants wouldn't have any unexpected issues during one of the most important times of the year. Sometimes, though, you need to ship updates last minute. Picture this: It's Black Friday Eve, 11:47 PM. You've just deployed a new /sale page with 50+ products at discounted prices. Marketing is about to email 500,000 subscribers. Everything tested fine with your sample data.

When you’re debugging a tricky issue in a distributed system, “what changed?” is often the most important question. You add logs, you capture data, you redeploy, and suddenly your browser is full of open tabs, copied JSON blobs, and screenshots of log lines. Comparing behavior between two requests, two users, or two releases turns into a manual, error-prone chore. Lightrun Snapshots were built to fix the data collection side of that story.

At Coralogix, we’re constantly looking to evolve the measurements we take to better understand the efficiency of our infrastructure. We constantly assess and investigate sources of cost in our cloud infrastructure, to ensure we’re getting the best return on investment. This activity, often referred to as FinOps, is becoming a cornerstone of engineering teams.

You don’t have to choose between capturing every signal and keeping costs predictable. Modern observability stacks blend full-fidelity storage (time series or columnar systems like ClickHouse and Apache Druid), tail-based sampling for heavy traffic, and tiered storage (hot/warm/cold with S3-backed archives). This gives you full-fidelity incident forensics with the day-to-day cost profile of a sampled setup.

As the year winds down, my inbox is overflowing with Black Friday offers and festive greetings. It’s that time when Thanksgiving and the run-up to December holidays remind us to pause and appreciate what truly matters. Yet, in my recent conversations with IT leaders in financial services, I’ve noticed something: the time and calm need to do this feels elusive.

ServiceNow is one of those platforms that looks simple from the outside but turns into a labyrinth the moment an organization starts customizing it. What begins as a service catalog or an HR portal quickly evolves into a tangle of custom tables, UI policies, business rules, Flow Designer actions, and scripted REST endpoints. None of this is bad. In fact, it’s the whole reason companies choose ServiceNow: you can build anything.