We’re so excited to share our latest features and improvements to the Embrace dashboard!

In this update, we’ll cover our redesign of the Create Monitor section on our dashboard. Now it’s easier than ever to set up monitors for the crashes, logs, and network errors you care about.

Before we do a deep dive, here’s what our updated flow looks like!

That’s a lot to take in, but no worries, we’ll walk through it step by step. Get started by heading to the Monitor page and clicking “Add Monitor.”

Now we’ll go section by section to explain the steps to configure a new monitor.
The four sections are the following:

  • Set a Trigger
  • Define Trigger Thresholds
  • Notify Your Team
  • Name Monitor

Set a Trigger

The first step is to select the type of monitor. This can be one of the following:

  • Crash count
  • Crash user percentage
  • Log count
  • Log user percentage
  • Network requests
  • Network requests user percentage

Once you select the type, a helpful visualization will appear that will update in real-time as you further configure your monitor.

Crash example

The below image is an example of a crash monitor.

For crashes, you can further specify the trigger by adding optional filtering based on the crash message. By adding a complete crash message, the monitor will only track instances of that crash. By adding part of a crash message, you can capture multiple crashes aggregated under a single monitor.

For example, the crash message of android.database.sqlite.SQLiteCantOpenDatabaseException would only apply to that crash whereas the message android.database would also apply for additional crashes that share that subset of text (e.g. android.database.CursorWindowAllocationException).

The Breakout By section allows you to avoid creating individual monitors for every crash grouping. Instead, if you breakout by crash message, each crash grouping will be tracked individually.

Log example

The optional filters for a log include the message as well as the type. Similar to crash monitors, you can set the the entire log message or a subset of it. Embrace currently supports the following log types: info, warning, error, and system.

Network request example

The optional filters for a network request trigger include the following:

  • Domain
  • Method
  • Path
  • Single status code or range of status codes

If you want to track connection errors, you can configure your monitor to do so by checking the appropriate box.

Define Trigger Thresholds

Once you’ve selected your trigger, it’s time to define the conditions you want to be alerted on.

This section involves setting the following criteria:

  • Evaluation method — how a metric should be compared against a threshold value (or percentage) within a time window
  • Time window — the period of time for calculating whether an alert should trigger
  • Thresholds — a value (or percentage) to compare a metric against

Let’s go through each of these steps in more detail.

Evaluation method

Embrace gives you maximum flexibility when it comes to deciding when an issue demands attention. You determine not only a threshold, but also the exact conditions a metric must meet within a time window to trigger an alert.

Currently, there are four choices:

  • On Average
  • At Least Once
  • At All Time
  • In Total

To better explain them, let’s go through an example. Let’s say you’ve selected “crash count” as the metric, a threshold value of “Above 10”, and a time window of 1 hour. Note that monitors are evaluated every minute.

If your evaluation method is On Average, an alert would fire if the average number of crashes during the window exceeds 10. In other words, if there were 601 crashes within an hour, an alert would fire. (601 crashes divided by 60 evaluations (one per minute) is greater than 10.)

If your evaluation method is At Least Once, an alert would fire if at any given minute within the hour, there were 11 or more crashes.

If your evaluation method is At All Time, an alert would fire if for every minute within an hour, there were at least 11 crashes.

If your evaluation method is In Total, an alert would fire if at least 11 crashes happened in aggregate within the hour.

Time window

There are several options for the time window:

  • Last 5 minutes
  • Last 10 minutes
  • Last 15 minutes
  • Last 30 minutes
  • Last 1 hour
  • Last 2 hours
  • Last 4 hours
  • Last 24 hours


Here, you can set various thresholds:

  • Error Threshold
  • Error Recovery Threshold (Optional)
  • Warning Threshold (Optional)
  • Warning Recovery Threshold (Optional)

The Error Threshold is the value (or percentage) that a metric is compared against to determine if an error alert should fire.

The Error Recovery Threshold is a value (or percentage) that a metric must reach after an error alert has triggered before a subsequent alert can fire. In other words, it allows you to only be alerted once for the same spike.

The Warning Threshold is the same as the Error Threshold but for warning alerts.

The Warning Recovery Threshold is the same as the Error Recovery Threshold but for warning alerts.

Notify Your Team

You can configure how you want your entire team or individual team members to be notified. You can be notified by email and/or Slack.

Name Monitor

Lastly, you want to be able to easily find the monitor you’re interested in. In this section, you can give a unique name to the monitor you’ve just created.

And that’s it! Now you can quickly create and configure monitors that will give you better control over how and when an issue deserves attention. As always, please share any feedback so we can continue to build features and improvements that help your team be successful.

How Embrace Helps Mobile Teams

Embrace is an observability and debugging platform built for mobile teams. We are a comprehensive solution that fully reproduces every user experience from every single session. Your team gets the data it needs to proactively identify, prioritize, and solve any issue that’s costing you users or revenue.

Want to see how Embrace can help your team ship better apps? Request a customized demo and see a path to improvement immediately!