Operations | Monitoring | ITSM | DevOps | Cloud

Agents have quickly become part of the tech landscape as organizations embrace AI across their businesses. But embracing agents also means embracing the monitoring best practices that have long been part of engineers' workflows: tracking performance, catching errors, and responding to incidents But it doesn't stop there. Agents also introduce new challenges.

This is a guest post from Armin Ulrich, a fullstack developer, and founder of placid.app. He also created the MadeWith* network where he shares his projects and allows other developers to share theirs. Two people and one beagle run the project showcase madewithvuejs.com. The beagle is actually an AI agent that we have added to our workflows, but we’re very fond of her by now. Milly is part of the team, scouting for content, building features and sniffing for bugs.

Grafana’s Logs Drilldown is a point-and-click way to investigate logs without writing queries. Drilldown lets you break the logs down by service, label, pattern, or any other field, and narrow the selection one click at a time until the problem is in view. It’s a powerful tool, but it only works with Loki. So we built the same experience into the VictoriaLogs data source. We’re happy to announce that the VictoriaLogs data source for Grafana now ships with Drilldown integration.

Running an LLM on Kubernetes is rarely just a Deployment with vLLM in it anymore. A whole layer of frameworks and operators has grown up for it: KServe, NVIDIA Dynamo, Ray Serve, Kthena, llm-d. Each one adds its own custom resource that describes a model deployment, with routing, autoscaling and the split of a model across pods built in, and each one turns that resource into ordinary Kubernetes objects in its own way.

Resque 3.2.0 shipped on October 16 with a single change, listed under Security: resque-web now rejects state-changing requests that come from another site. Until this release, resque-web had no cross-site request forgery (CSRF) protection at all. A page on any other site could submit a form to your dashboard and clear your failed jobs or delete a queue, as long as the browser it ran in could reach resque-web and was logged in to it. The fix is small and most teams can upgrade without touching anything.

Cut alert fatigue and resolve incidents faster. Learn how to design tests, route alerts to the right owning team, and connect internal and Internet signals.

Correlate internal infrastructure health with Internet-path data to localize WAN slowdowns fast across MPLS, SD-WAN, and direct Internet access at the branch.

To optimize database performance in Ruby on Rails, fix N+1 queries with includes, preload, or eager_load; index the columns your WHERE and JOIN clauses filter on; load only the columns you use with select and pluck; batch large reads and writes with find_each and insert_all; and move to read replicas or sharding only once query-level fixes run out.

Monitoring modernization doesn’t have to begin with a rip-and-replace project. For many IT teams, it starts with a specific need: better visibility, stronger historical context, more useful alerting, or capabilities their current tools simply don’t provide. From there, modernization can happen in stages.

If you’re researching AWS desktop virtualization and application delivery services, it is likely that you have come across Amazon WorkSpaces and Amazon WorkSpaces Applications. While the names sound similar, these two AWS services address different requirements. Amazon WorkSpaces provides a complete cloud desktop, while Amazon WorkSpaces Applications focuses on securely delivering individual applications through AWS-managed application streaming.