Network Request (GraphQL)

Understand how GraphQL requests are grouped, named, and displayed in the Network Requests view.

BugSnag Performance automatically detects GraphQL requests from supported mobile SDKs and extracts the GraphQL operation type (query, mutation, or subscription) and operation name. Instead of grouping every request under a generic endpoint such as POST /graphql, BugSnag creates a separate GraphQL span category and groups requests by operation.

GraphQL operations are displayed alongside standard HTTP requests in the existing Network Requests view. No separate tab is required.

GraphQL display names

GraphQL span groups use the following display name format:

• When the operation type and name are available: operation Type endpoint (operation Name)
  • Example: query /graphql (GetUserProfile)
  • Example: mutation /api/graphql (CreatePost)
• When the operation name is missing: query /graphql
• When the operation type is unknown: /graphql (GetUserProfile)
• When both the operation type and name are missing: /graphql

This operation-level grouping makes it easier to identify which GraphQL operation is contributing to slow or failed requests.

GraphQL metrics

For each GraphQL span group, the Network Requests view provides:

• Request volume and request counts
• Latency metrics (percentiles, trimmed mean, etc.)
• Full span waterfall traces for individual requests

Performance monitoring

GraphQL span groups are included in BugSnag Performance monitoring alongside other network spans. You can create performance monitors that watch GraphQL Operations either across the whole GraphQL Operations category or for specific operation span groups (for example query /graphql (GetUserProfile)).

To create a performance monitor:

• Open the Performance view and click Create performance monitor.
• Choose percentile and period (for example P90 over last 1h) and a span count minimum.
• Under Monitor select the GraphQL Operations category.
• Set thresholds for Warning and Critical and choose the notification channels to receive alerts.

The performance monitor UI shows the category GraphQL Operations alongside other categories (App Starts, Screen Loads, Outbound HTTP Requests).

Performance targets

Performance targets allow you to set default Warning and Critical thresholds for groups of spans. Targets can be configured at the category level (for example the GraphQL Operations category) and overridden per-span-group with custom targets.

BugSnag provides a Default targets view where you can set target values for each category. After adding a default for GraphQL Operations, those thresholds will appear as performance target markers on graphs and in span timelines for any span groups that do not have a custom target.

To set or customize targets:

• Go to Project Settings → Performance → Performance targets.
• In Default targets set the Warning and Critical values for the GraphQL Operations category.
• Optionally open Custom targets to add span-group-specific overrides (for example set a stricter P90 for a critical mutation).

Custom targets override the category default for the chosen span group. When a span group has a target configured you will see a performance target indicator in the span list and in the waterfall view for individual spans.

For more details on configuring performance monitors and targets see: Performance monitoring and Performance targets.