# Do you really need an MCP to build your app? Sentry recently acquired **XcodeBuildMCP**, the Model Context Protocol server I created to help AI agents navigat...
When Your Database Takes 9 Seconds to Say Hello: A Session Replay Story
You shipped a feature. Users loved it. Then one user casually mentioned it takes "forever" to load. You check your metrics. Response times look fine. You check ...
AI agent observability: The developer's guide to agent monitoring
Most "agent observability best practices" content reads like a compliance checklist from 2019 with "AI" pasted over "microservices." Implement comprehensive log...
You spent months instrumenting your app with OpenTelemetry. The idea of ripping it out to adopt a new observability backend is not an option. Sentry's OTLP endp...
Logging in Next.js is hard (But it doesn't have to be)
A typical Next.js deployment can execute code in up to three different runtimes: Edge, Node.js, and the browser. You may already be capturing logs from server-s...
This blog is based on a recent live workshop. You can watch the the full livestream on Youtube. Next.js gives you a lot for free; server-side rendering, file-ba...
Seer fixes Seer: How Seer pointed us toward a bug and helped fix an outage
Seer is our AI agent that takes bugs and uses all of the context Sentry has to find the root cause and suggest a fix. We use it all the time to help us improve ...
Here's a quick look at how Sentry handles your personal information (PII).
×
Who we collect PII from
We collect PII about people browsing our website, users of the Sentry service, prospective customers, and people who otherwise interact with us.
What if my PII is included in data sent to Sentry by a Sentry customer (e.g., someone using Sentry to monitor their app)? In this case you have to contact the Sentry customer (e.g., the maker of the app). We do not control the data that is sent to us through the Sentry service for the purposes of application monitoring.
