Network Failure Alerts

Instabug now gives you more control and precision when setting up alerts for failed network requests. With our enhanced alerting capabilities, you can receive alerts tailored to specific types of failures, allowing your team to act faster and more efficiently.

🔍 Filter Alerts by Failure Type

You can now specify whether the alert should trigger for:

  • Client-Side Failures: Failures occurring on the user's device (e.g., timeout, no internet).
  • Server-Side Failures: Failures returned from your backend (e.g., 500 Internal Server Error).

This gives you the ability to monitor the type of failures that matter most to your team.

🎯 Add Extra Filters for Granularity

In addition to filtering by failure type, you can further narrow down alerts using the following criteria:

  1. HTTP Status Code

Include/Exclude specific HTTP response codes in your alerts, such as:

  • 500 for internal server errors
  • 404 for not found
  • 401 for unauthorized access
  1. Failure Name

Use the failure name to detect specific issues, especially useful when failure codes are not available (as is often the case with client-side issues).

What is a Failure Name?

A failure name is the descriptive message sent alongside a failure event. You can view failure names by:

  • Navigating to the Network tab on your dashboard
  • Selecting the network request of interest
  • Scrolling to the Failures section
  • Checking the value under the Name column

This enables you to create highly targeted alerts—like catching NoConnectionError or TimeoutException events.