Sentry 201: Integrations & Sampling That Won't Surprise You

You set up Sentry. Errors are flowing in. You'd call it instrumented. We'd call it a start. When something breaks, you should know what failed, which commit caused it, who owns it, and what the user saw — without jumping between tools or getting surprised by your bill. Most teams are closer to that than they think. This is the 201 session for teams who got Sentry firing events and stopped there.