Operations | Monitoring | ITSM | DevOps | Cloud

Latest Videos

Building a flexible, realtime data warehouse at Sentry with Beam + Dataflow (Syd Ryan)

Syd Ryan describes two hard problems they've solved at Sentry with streaming Beam pipelines. The first solution combines Postgres change data capture and SQL views to produce a table that appears to be updating in real time within BigQuery. The second solution is aggregating 1000s of events per second and backfilling historical data effectively with Beam's unified batch/streaming interfaces.

Beam in Production: Lessons learned and best practices (Mike Clarke)

Mike describes gotchas and early struggles Sentry hit moving streaming data pipelines off our laptops and into production. He covers some unexpected Beam defaults, detecting schema errors, compare performance between the python & java SDK, and proactively identifying when production pipelines break due to unexpected data.

Sentry for Native Crashes: Gaming, IoT, and Beyond

Application crashes have a significant impact on customer experience, which can adversely affect a company’s reputation and revenue. Error and crash reporting is a unique feedback mechanism that provides true data about the quality of their product. Developer teams that create games, mobile applications, IoT, and other high-performance applications need rich insights into application health to quickly and continuously fix software errors with minimal impact.

Sentry and Rookout Integration: A Better way to Find and Debug Errors in Your Code

Rookout’s new Sentry integration empowers you to fix bugs faster than ever before. Sentry features allow you to identify the exact location of an error in your code. With the Rookout integration, you will find an additional prompt to debug the issue live, in production, in Rookout. With the click of a button you will see the same line of code from Sentry highlighted in Rookout’s IDE-like interface, without restarting, redeploying or adding more code. In Rookout you can set non breaking breakpoints and trigger the error again to receive the real time debug data.