Ruby Stability at Scale
Monitoring
Observability
Stability
Crashes
Ruby
There are many talks, articles, and tutorials on how to monitor your Rails app for stability. These assume the source of the bug comes from your application code, from Rails itself, or from a gem. But what if the source of instability comes from Ruby or a native gem? If Ruby crashes, do you have any monitoring or ways to debug it?
In this talk, we'll look at how we deal with Ruby crashes in the Shopify monolith, the world's largest Ruby on Rails application, and how you can use some of our techniques. We'll cover topics such as how we monitor crashes, capture core dumps for debugging, prevent crashes, and minimize the impact of crashes on production.
In this talk, we'll look at how we deal with Ruby crashes in the Shopify monolith, the world's largest Ruby on Rails application, and how you can use some of our techniques. We'll cover topics such as how we monitor crashes, capture core dumps for debugging, prevent crashes, and minimize the impact of crashes on production.
Sep 05 - 11:15 to 11:45
Track 1 - Effectenbeurs
About the speaker
Peter Zhu
Ruby Core committer, Staff Developer
Peter is a Ruby core committer and Senior Developer at Shopify. He works on improving the performance of Ruby and is currently working on Modular GC and the MMTk integration. He is the co-author of Variable Width Allocation in Ruby, which improves Ruby's performance by optimizing the memory layout.