Operations | Monitoring | ITSM | DevOps | Cloud

Making an SRE agent available in Slack sounds straightforward until you start thinking about what that agent can access. If it's connected to Kubernetes, you need to consider how Slack communicates with the agent, what infrastructure the agent can inspect, and who can ask it to do something. Making operational tools easier to use shouldn't mean exposing another service or giving everyone unrestricted access to production.

A tampered build of the Claude Code editor extension (anthropic.claude-code 2.1.313) was published on the Open VSX store used by Vs code,Cursor and similar editors, quietly gives attackers persistent remote access to any computer that runs it, while the extension keeps working normally. Researchers don’t yet know how it was published (the listing belongs to an Anthropic employee) or who is behind it. They found no evidence that Anthropic’s official Marketplace release was affected.

See how packet-level and DevTools throttling produce different performance results, and learn which method reveals the network costs that slow your pages.

See how a Google Cloud outage took major brands like Home Depot offline, and why digital experience monitoring spots failures before status pages update.

When a branch office can’t reach the ERP system and customer calls start dropping, who gets the call? It’s almost always the network administrator. What that person does the rest of the week is less clear, and a CIO, a CFO and the admin themselves would probably each describe it differently. Part of the reason is how much the network has grown. Ten years ago it was mostly switches, cables and one building.

With VoIP monitoring, you hear about a bad call before anyone opens a ticket. Voice handles trouble worse than most traffic on your network. When a file download drops packets, it just asks for them again. A live call has no time for that. A 2% burst of packet loss, which a download wouldn't notice, is enough for everyone on the call to hear a gap. Most of those problems start on the network path, which you can measure and fix.

Most teams reach for Ansible in CI/CD pipelines the same way: a shell step that runs ansible-playbook, SSH keys stored as secrets, and a growing list of manual steps nobody documented. It works until it doesn't : then the failure happens at the worst possible moment and the pipeline becomes a debugging session.

I don't write SQL. Not by hand anyway. That might sound like a confession, but it's true of most analysts (and engineers) now. In the 9 months since joining incident.io I have built headcount models for hiring decisions, a Slack bot for assigning new customers, guidance for our AI data analyst, and a couple of internal web apps. If you asked me which of those counted as "analysing data", I'd struggle to say. A lot of that comes down to the "commercial" part of the job title.

Replay and key takes from our October 20 live with TPC: why Day Two is 80% of infrastructure work, why shared staging breaks when agents write the code, how agents cut migrations from months to hours, and how to keep agents under control with policy tokens and audit logs. Romaric founded Qovery to make Kubernetes accessible to every engineering team. He writes about platform strategy, developer experience, and the future of cloud infrastructure.

The ingestion card on your Logit.io dashboard has a 24h / 7d toggle for Logs and Metrics, hourly log counts built from counter increases and a dotted line for the hour that is still filling in. Those three changes decide whether a dip on the chart is a real problem or just the clock.