CLS, or cumulative layout shift, can make or break your website’s user experience. In this video we’re going to learn what CLS is, and what causes it.

Learn the basics of frontend Javascript error monitoring with Sentry. Whether you are running React, Angular, Vue, or just “vanilla” JavaScript, see how Sentry can help you find the who, what, when and where behind errors in your frontend project.

What do you do when stack traces and breadcrumbs aren’t enough to reproduce a bug that is inundating your support team with tickets? Session Replay might be the solution every developer didn’t know they needed. Join Sentry engineer Elias Hussary as he shares how you can use Session Replay from Sentry to watch video-like playbacks of user sessions with code-level insights to confirm and debug errors and performance issues more easily. Plus, he’ll give a sneak peek of new and upcoming features we’ve added to our Session Replay product.

Want to catch performance bottlenecks in production without writing manual performance tests and searching through spans? Join the Sentry engineers building Profiling as they share how to use this tool to see the exact lines of code or functions causing slowdowns in your application. During this livestream, the team will dive into Profiling – which gives you code-level insight into your application performance. From flamecharts to functions and slow frames – you’ll get the whole scoop on how to optimize your resource consumption to prevent slow load times and UI jank.

Session Replay from Sentry provides video-like playbacks of user sessions with code-level insights to help developers triage and troubleshoot errors & performance issues more effectively.

While timeouts and slow page loads are frustrating for users and can go unnoticed by developers, Tilled can’t afford either. As a PayFac-as-a-Service provider, fast API endpoints mean the difference between a successful business and one that flops due to dropped payments. Join us to see how the team at Tilled takes the complexity out of performance monitoring, so they can fix slowdowns faster without researching span trees or deciphering dashboards - saving developers time (and their sanity).

Code coverage, arguably a very important measure that we as development teams don’t pay enough attention to. That is until Sentry notifies you of a frustrating/critical/oh s*#t moment. Then we all think: “how could this have been avoided?”, “why didn’t our tests catch it?”, “oh… we didn’t have any coverage on this flow.” With our new Codecov integration, you can avoid regressions (and awkward conversations) by being able to see which lines that caused an issue are covered and which ones are not - right in the stack trace we kick out on every error report.

Join the Sentry developers who built Sentry’s OpenTelemetry support and learn how to understand the performance of your OTel instrumented applications. As the leading open standard for observability, thousands of companies use OpenTelemetry to capture data across their services - but capturing raw logs, traces, and metrics is only the first step in improving software performance.

Watch this summary of the Nextdoor, Riot, and Sentry fireside chat on building better mobile experiences. Then watch the full conversation at bit.ly/building-better-mobile-experiences-8.

In this clip from the workshop "Building better mobile experiences: Fireside chat with Riot, Nextdoor, and Sentry", Julius from Riot shares why they chose to use Sentry for mobile error and performance monitoring.