![Cover Image for [Workshop] Your First Steps in Sentry](https://images.lumacdn.com/cdn-cgi/image/format=auto,fit=cover,dpr=2,background=white,quality=75,width=400,height=400/event-covers/lb/3ad20ed7-a876-436e-a6ac-d5b0cde81b40.jpg)
![Cover Image for [Workshop] Your First Steps in Sentry](https://images.lumacdn.com/cdn-cgi/image/format=auto,fit=cover,dpr=2,background=white,quality=75,width=400,height=400/event-covers/lb/3ad20ed7-a876-436e-a6ac-d5b0cde81b40.jpg)
[Workshop] Your First Steps in Sentry
Registration
About Event
It turns out, Sentry does A LOT these days. Errors, Logs, Replays, Traces, and even Agent and MCP monitoring… but all this observability works better with a good foundation. We’re going to step back to 0, and show you how to build a “not bad” Sentry implementation from the ground up.
We’re going hands on in a new Sentry environment to show you how to:
Get started sending, searching, and aggregating logs; and how to get the most out of them
Building your first alerts and notifications
Configure uptime monitors to make sure your app stays up, and screams when its down
What even is a “sample rate” anyways?
Getting started with Replays
The earliest stages of monitoring performance issues