Operations | Monitoring | ITSM | DevOps | Cloud

When and what should I be logging?

This is a follow-up to Sergiy’s post Errors, traces, logs, metrics: when to reach for what. Modern observability platforms, like Sentry, give developers a lot of choice. For a given problem, should you use traces, profiles, metrics, logs? If you take away one thing from this post, I hope it’s this: when in doubt, start by adding a few targeted log lines.

Sentry 201: Build agentic workflows with the Sentry MCP, CLI and Seer

Agents are pretty good at fixing your apps. We can make them even better. ​In this workshop we’re going to show you how to give your agents superpowers using Seer, the Sentry MCP server, and CLI tool. Join to learn how to: ​- Teach agents how to best implement and work with Sentry through agent skills and the CLI tool. ​- Set up Seer’s agent handoff feature for Claude, Cursor, or GitHub Copilot and have agents start automatically generating pull requests for fixes.

Any Apple update can break our app. Here's how we find out first.

This is a guest post by Dan Mindru, a Frontend Developer and Designer who is also the co-host of the Morning Maker Show. Dan is currently developing a number of applications including PageUI, Clobbr, and CronTool. It feels like with every release, we are walking a tightrope. We need to keep our app lightweight, stable, and performant, all the while depending on APIs that can shift at any moment (without warning, too!).

Reading the agent traces is how you make the call your eval can't

Remember being excited (or dreading, depending on the stage of your career and the company you worked at) about writing unit tests? Or sweating all the details in your end-to-end and integration tests you were sure covered all the use cases your users would hit? These days a lot of UIs are slowly being replaced by a single input field and an agent that promises to deliver the same value a UI would, but with the elegance and pun-ness of a “Jarvis”.