We’re back at talking about Monitoring, Profiling and Instrumentation with folks from the Sentry SDK. I’m excited to have on stage Manoel Aranda Neto and Roman Zavarnitsyn to talk as a bit about their Android SDK.
The Sentry Android SDK goes beyond just monitoring. It’s able to auto-instrument your code, using bytecode manipulation (which sounds both scary and cool). Join me in this episode, while the folks from Sentry tell us how this works internally and how Sentry can help you improve your application performances.
Enjoy the show 👨🍳
- 00.00 Intro
- 00.45 Episode Start
- 01.23 Manoel’s Introduction
- 01.45 Roman’s Introduction
- 02.31 What is Sentry?
- 03.20 Is Sentry only for Mobile?
- 03.52 Which languages and SDKs are you supporting?
- 04.50 How is Sentry SDK working internally?
- 06.46 Sentry & the NDK
- 08.07 Symbolicating Native Stacktraces
- 10.16 Monitoring & Performance Impact
- 11.04 Sentry’s Killer Feature
- 13.10 What makes Sentry different from other platforms?
- 14.38 The Sentry Gradle Plugin
- 16.11 Tracing Auto-Instrumentation
- 18.55 How is Auto-Instrumentation working?
- 22.16 Bytecode Manipulation
- 26.03 Which features are you instrumenting?
- 27.51 New ideas for automatic instrumentation?
- 29.54 Sentry & Open Source
- 31.15 The New Github Projects
- 32.33 External Contributors
- 34.08 The feature of Sentry
- 35.56 How you got involved with Sentry?
- 38.06 Further reading
- getsentry/sentry-java on Github
- getsentry/sentry-native on Github
- getsentry/sentry-android-gradle-plugin on Github
- Sentry Android Official Documentation
- Mentioned Resources:
- @marandaneto on Github
- @marandaneto on Twitter
- @romtsn on Github
- @romtsn on Twitter