Automatic Instrumentation
Learn what transactions are captured after tracing is enabled.
Capturing transactions requires that you first set up performance monitoring if you haven't already.
Sentry's routing instrumentation in Flutter automatically tracks and reports page navigation events in your app. It supports both standard Flutter routing and the GoRouter package.
Learn more in our Routing Instrumentation docs.
Sentry's user interaction instrumentation captures transactions and adds breadcrumbs for a set of different user interactions, which include clicks, long clicks, taps, and so on.
Learn more in our User Interaction Instrumentation docs.
Sentry's http.Client instrumentation captures errors and creates transaction from your HTTP requests.
Learn more in our SentryHttpClient Instrumentation docs.
Sentry's Dio instrumentation captures errors and creates transaction from your Dio HTTP requests.
Learn more in our Dio Instrumentation docs.
The app start instrumentation provides insight into how long your application takes to launch.
Learn more in our App Start Instrumentation docs.
Unresponsive UI and animation hitches annoy users and degrade the user experience. Two measurements to track these types of experiences are slow frames and frozen frames. If you want your app to run smoothly, you should try to avoid both. The SDK adds these two measurements for the transactions you capture.
Slow and frozen frames are Mobile Vitals, which you can learn about in the full documentation.
Learn more how to set it up in our Slow and Frozen Frames Instrumentation docs.
The AssetBundle instrumentation provides insight into how long your app takes to load its assets, such as files.
Learn more in our AssetBundle Instrumentation docs.
The Sentry-specific file I/O instrumentation provides insight into how long your app takes to execute File I/O operations.
Learn more about our file I/O integration.
The sqflite database instrumentation provides the ability to track the performance of any sqflite query.
Learn more about our sqflite Database Instrumentation.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").