Isolate mobile app performance issues
mPulse monitors all network traffic, but only domain results are reported in the mPulse dashboards. Use URL patterns to define rules that specify which paths of the network requests are captured and reported on within your native mobile application.
Here are a few examples on adding URL pattern-matching rules to capture user actions:
- Example 1
- You want to capture all of the user actions associated with http://example.com/... so
you set up a URL pattern rule that looks like this: http://example.com/*.
The rule matches http://example.com/abc and http:/example.com/123, but it does not match http://example.com/abc/123. The rule doesn’t work for this URL because it has two sub-path components, abc and 123. To match this URL, the rule must look like this: http://example.com/*/*.
- Example 2
- You can also use an asterisk (*) to replace components within the query string.
However, each component of the query string needs to have a value of ‘*’, or it will not
be included in the reported URL.
Given this URL:
http://www.website.com/api/x?category=abc&page=xyz
Here are three example patterns with results:
- Pattern 1: /api/x?category=abc&page=xyz
- Result: /api/x
- No query string components are included because none are set to `*`
- Pattern 2: /api/x?category=*&page=xyz
- Result: /api/x?category=*
- Only the category has a `*`, so the page component is discarded
- Pattern 3: /api/x?category=abc&page=*
- Result: /api/x?page=*
- page is set to `*`, and category is discarded
- Pattern 1: /api/x?category=abc&page=xyz
How to
Next steps
Use the Waterfall dashboard to see network requests for your mobile application.