Operations | Monitoring | ITSM | DevOps | Cloud

Sentry now has logs. Collect and aggregate logs in your Laravel apps, in both the backend and the frontend. Errors won't always capture the whole story, let's see how logs can help us identify a real customer issue.

Sentry has released AI Agent monitoring, and in this video you can see the fast path to getting started with it using the Vercel AI SDK and Anthropic Claude. AI Agent Monitoring uses tracing to let you see details around how AI interactions are happening inside your application. You can see the back and forth conversation flow, token usage, model usage, durations, and much more. Agent Monitoring is out now, take it for a spin, let us know what you think in Discord!

Monitoring agents and LLM applications is... different. Managing everything from tool calls, to model configurations, token usage, and AI systems do their best to solve problems on their own - so errors aren't always clear. Sentry's agent monitoring focuses on making it easy to dive into your AI applications and understand whats breaking, where, so you can fix it faster.

With application performance monitoring and statistics, Sentry.io predicts expected values for any metrics query—and alerts you when your app’s performance falls outside the norm.

Watch Cody walk us through how to use Seer and how quickly it can root cause issues to save you precious time.

There's a lot more context to an error than the message blinking in red on your screen. Seer understands the context of your application and everything behind that error. Seer collects information from the Stack Trace, Logs, Traces and Spans, Profiles, and the code from your GitHub repo and uses it to understand what's causing your issues, and propose fixes.

We're going hands-on with all things application development, and making sure that when your code breaks, you have a good way figure out how to fix it. Sentry Build workshops stay in the code, building software, and debugging real problems with the latest tools from Sentry.

Debugging background jobs is one of those tasks that always sounds easier than it is—until you’re knee-deep in stack traces that offer no real clues. Background jobs love to run in isolated environments, cutting themselves off from all the helpful context you’d normally have. @nikolovlazar shows us how to debug these errors anyway—piecing together the missing context across systems so you can actually fix the problem instead of just guessing.

Try Sentry for free: https://sentry.io
Docs: https://docs.sentry.io