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

In this update, we’ll give a walkthrough of our updated Alerts page (renamed from Monitors) and the new filtering capabilities on our Crash Summary page. These updates provide you with a streamlined process for managing alerts and an easier, more powerful way to drill into the specific crashes you want to investigate.

Here’s what we’ll cover in this post:

  • The updated Alerts page
  • The new filtering on the Crash Summary page

The Updated Alerts Page

The Alerts page, formerly called the Monitors page, stores all your alert information. We’ve simplified the process for creating and managing alerts into one cohesive flow. Now, whether you’re interested in crash counts, first seen issues, or network errors, all alert types are organized and accessible in one place. First, let’s review some terminology before diving in further:

  • Metric alerts - These trigger off either counts or affected user percentages of crashes, logs, or network requests. You can make as many alerts on metrics as you want, giving you full control over how targeted you want your coverage to be.
  • First seen issue alerts - These are proactive alerts, meaning they trigger for situations you can’t predict ahead of time. You can only set these once because they will fire whenever a crash or log happens the first time in a new release.
  • Network error alerts - These are also proactive alerts, and they will trigger whenever any endpoint hits a predefined error percentage with a minimum count. You can set alerts for 4xx errors, 5xx errors, and connection errors. In addition, you can set exclusions for endpoints you do not want to track.

Creating New Alerts

Here’s what the New Alert creation window looks like:

Now, every alert type is created through the same widget. In the image above, a few of the alert types are grayed out. This occurs whenever a first seen issue or network error alert has already been set since those cannot have duplicates.

Managing Alerts

The below image highlights the benefits of this consolidation. We’ve removed the Proactive Monitors section and folded it under Manage Alerts. Now, you not only create all alerts in the same way, but you also investigate them from a single location as well!

Duplicating Alerts

It’s also faster than ever to extend the specifics of a preexisting alert into a new one. You can click on the duplicate icon to open a pre-filled New Alert widget. That way, you’re not starting from scratch, and with a few adjustments, you can create new alerts easily.

Alert History

The Alert History section now functions like a newsfeed for all previous alerts. By clicking the Alert ID, you will be shown a graph that is locked to when the corresponding alert triggered. That way, you can always inspect previous conditions to more effectively tailor monitoring to your use case.

The Detail column is based on the grouping, which differs slightly based on the alert type.

  • For a metric alert, a detail is only available if a Breakout By is set, in which case it is the grouping that caused the alert to trigger.
  • For a first seen issue alert, the detail is the the crash or log that was seen.
  • For a network error alert, the detail is the endpoint (domain, method, path) and error (status code or connection error) that broke the threshold.

Alert Detail

You can navigate to the Alert Detail page by clicking on one of the following:

  • The Alert Name from the Manage Alerts section
  • The Alert Name from the Triggered Alerts section

This page shows a live graph alongside a summary of the conditions for the alert. If a triggered alert has been subsequently changed (e.g. updated or deleted), that information will be shown in the Alert Conditions window.

The New Filtering on the Crash Summary Page

We’ve previously rolled out filtering on the User Sessions page and now we’re adding that functionality to the Crash Summary page. Instead of manually scrolling to locate the crash you’re interested in, you can use our powerful filtering to speed up your search.

By clicking the input box, you’ll be greeted with a list of categories that you can add and fully customize.

The following are the categories that are currently available:  

App
Version - You define this at the page level.
Build
Environment
Framework - This only applies to React Native applications.

Device
Country
Model Factory Name
Jailbroken
Manufacturer
Model Name

OS
OS Major Version
OS Version

User
Persona
Embrace ID
User ID
Username
User Email

Session
Session Property Key
Session Property Value

Crash
Message - This is what we show in the description part of the crash table. For Android, it includes the crash type and method. For iOS, it includes the module and symbol. We treat them as one combined string, so you can match based on the entire message or parts of it.
File Name - This is the file that the method/symbol comes from.
Method/Symbol - For Android/iOS. This is the failed method/symbol call that resulted in the crash.
Module - For iOS. This is the module that the method/symbol comes from.

Depending on the option selected, you can search for matches using one (or more) of the following relational operators:

  • is
  • is not
  • greater
  • greater or equal
  • less
  • less or equal
  • contains
  • does not contain

This image demonstrates how you can add as many filters as you like to target the exact crashes you’re interested in.

The following image showcases how you can filter for either native or framework crashes. Note this only applies to applications using React Native.

And that’s it! We’ve combined metric and proactive alerts into the same flow so it’s easier to create, update, and review them in one place. You can also duplicate alerts to create new ones even faster. In addition, you can access live graphs for active alerts as well as locked graphs for triggered ones. For investigating crashes on the Crash Summary page, you can now use our powerful filtering to drill down to the ones you’re interested in.

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 grow your mobile applications with best-in-class tooling and world-class support? Request a customized demo and see how we help teams set and exceed the KPIs that matter for their business!

Need help improving the performance and stability of your Unity games? Take our SDK for a spin!

Want to learn best practices for scaling your mobile applications? Check out these helpful eBooks!