Operations | Monitoring | ITSM | DevOps | Cloud

Automate Product Analytics reports with your agent and the CX CLI

Every page view, click, and session your RUM SDK captures lands in Coralogix as a log event under the cx_rum subsystem — the raw data behind how people actually use your product. You can turn it into a shareable report without writing a single query. Just ask your coding agent. Your agent queries that data through the CX CLI and writes the report for you: describe what you want in plain English, get a formatted report back — without leaving the terminal.

What's actually inside your SBOM (and why it matters)

An SBOM is more than a compliance checkbox. It's literally a bill of materials for your product: every software component that makes it into what you ship, plus the metadata that tells you whether it's safe to use. This video covers what that metadata actually does for you: An SBOM earns its keep when it shows you what's actually there, version to version, on a continual basis.

When an AI Agent Breaks the Law, Who's Responsible?

An AI agent was given one simple task: book a gym class when a slot became available. Instead, it discovered a vulnerability in the gym’s software, gained administrative access, deleted another user, and booked the slot anyway. Australian AI technologist Andrew Bird had connected an AI agent to WhatsApp to automate a routine gym booking. But when the agent encountered an API without proper authorization checks, it didn’t simply stop. It found a way around the problem and used the vulnerability to accomplish the task it had been given. And that creates a much bigger question.

Shipped: Self-serve your MCP server credentials

Enterprise agent platforms need a client ID and client secret in hand before they will connect to anything. An admin with the Modify MCP Settings permission can now issue that pair directly in Settings, connect the platform, and manage the credential lifecycle on whatever schedule your security policy requires. No support request, no wait.

The pager shouldn't be what starts the investigation

Authored by Greg Janco, Engineering Manager at Mezmo I've always thought there was something backwards about incident response. An alert fires at 3 a.m. PagerDuty does its job. Somebody wakes up, grabs a laptop, connects to the VPN, opens the alert, and then starts answering the same basic questions we ask at the beginning of almost every incident. What changed? What else is broken? Have we seen this before? Some of those need a human eventually. A lot of the first pass doesn't.

10 Top Website Monitoring Tools for Uptime, Page Speed and Real User Data

Your uptime tool reports the site as available all month. Support reports something else, because customers in one region spent the morning unable to complete a checkout. Both records are accurate, and that is the problem. An external check confirms the page answered. It cannot tell you that the answer took nine seconds for everyone routed through one CDN edge, or what caused the delay.