The Waterfall view shows you how certain factors and third-party services directly impact your users, so you can quickly identify the root cause of your performance issues for your web or native mobile app.
Use this dashboard to view object level data that flows into the mPulse system. Everything that is keeping your users waiting is recorded in the waterfall widgets. Once you have an idea where your users are spending the most time and where they may be encountering delays, you can look at the widgets for details to understand why.
You can see the individual beacons, session ID, back-end, front-end, and page load times for your web app in the Beacons widget. The Beacon Details widget has information about your visitors such as URL, performance metrics, and raw data. To determine the bottleneck that slowed down a particular resource, look at the Beacon Waterfall widget.
For native application monitoring, individual network requests within your app(s) can be grouped together and defined as an "action" (using the mobile SDK), then sent to mPulse as a single action type beacon. To make use of the waterfall for native application monitoring, mPulse must receive action type beacons.
You'll need to run the latest version of the iOS or Android SDK library.
To begin monitoring your native mobile app(s), you'll want to define where actions exist within your app using the mobile SDK. Actions can be defined to start and end wherever you'd like, and can include things like navigating to a new view within the app, or adding an item to a shopping cart. In addition, you should create any custom timers, metrics, and dimensions in your app configuration (see Use metrics to understand how performance impacts your business).
You can choose from beacons fired off of mobile network requests, custom timers, custom metrics, and actions within the Beacons widget. The Beacon Details widget has information about your visitors such as the Action Name that you set for your action in the mobile SDK, performance metrics, and raw data. To determine the bottleneck that slowed down a particular resource, look at the Beacon Waterfall widget.
When using the waterfall to analyze your mobile app's performance, pay close attention to where individual network requests occurred during the action. Look for heavy resources such as hero images and banners, or other resources that take a long time to load and create bottlenecks for the overall load time.
Updated 4 months ago