Network request grouping

Group like network requests together for performance analysis.

On the “Network requests” tab in BugSnag Performance, you can see the performance of network requests made by your app. By default, we simply group the requests by domain, so for example all requests to api.mycorp.com will be grouped together.

In order to get more useful aggregations you can configure your own groupings using URL-based patterns in the “Network endpoint groupings” project settings page - also available via the cog icon in the “Network requests” category homepage.

Syntax

The URL of each network request span will be compared against each configured grouping until one matches. The grouping syntax is:

<domain>/<path>

• the domain can
  • be specified in full or
  • have one or more segments replaced with a * wildcard or
  • be omitted entirely
• the / character must always be included
• the path
  • must follow the / character and
  • uses Open API path templating syntax; in other words path segments in braces ({ }) are effectively wildcards.

You do not need to provide the protocol (http/https). Query strings in the span URLs are ignored while grouping and cannot be included in the rules. Requests using different verbs (GET/POST etc) are always grouped seperately.

Examples

As an example, if you add a grouping of *.mycorp.com/products/{productid}/details, this will match spans with all these URLs:

• https://api.mycorp.com/products/1234/details
• http://subdomain2.mycorp.com/products/5678/details
• http://my.api.mycorp.com/products/5678/details
• https://api.mycorp.com/products/wheelbarrow/details?param=value.

If you are happy to wildcard all domains you can prefix your rule with a *, or omit the domain entirely. */api.mycorp.com/user/{userid} and /api.mycorp.com/user/{userid} are treated in an identical way to each other.

Recommended usage

We recommend that you add groupings that reflect the structure of the endpoints in your API.