Sign in

Crashes & Errors

Find the release that broke it.
Switch it off without another

Crash groups, readable stacks and crash-free rates by version, next to the behavior that led there. When the crashing code sits behind an Adaptive Variable, turn it off from Countly instead of shipping a hotfix.

In this demo connected-car app, a release broke charging. This is the crash group behind it, with the stack that names the code.

Part of analytics

A bad release, from
first crash to recovery

One story from the demo app: a release breaks charging, the crash points at a flagged feature, and turning it off brings the numbers back.

After a rollout

The questions engineers
ask the morning after

A release is judged by comparison, not by one number. Each of these has its answer on a screen of its own.

“Did this release make it worse?”

Crash rate by versionCrashes per 1k sessions for every version, next to the one before it, so a busy release and a quiet one compare fairly.

“What broke overnight?”

Issues, by releaseFilter to the new version, sort by occurrences, and see how much of it terminated the app.

“Why does it crash?”

The crash groupA readable stack, the device’s memory and state, and the paths profiles walked right before it crashed.

“Didn’t we fix that?”

RegressedA group resolved in one version comes back as regressed when it crashes again in a newer one.

Into the engineering workflow

Readable stacks,
filed where engineers work

A crash is only useful if someone can read it and someone owns it.

Symbolication

Function names, not addresses

Upload the symbol files from your build, and release crashes turn back into function names, files and line numbers.

Android ·Android native ·iOS ·macOS ·tvOS ·watchOS ·JavaScript

Jira

One issue per crash, kept in step

Create a Jira issue from a crash, with a link back to it. Resolve it on either side, and the other follows.

Create issue ·Link back ·Two-way status

Hooks

The first crash, wherever you work

A crash the project has never reported before can post to Slack, call your on-call tool or email a team.

New crash trigger ·HTTP ·Email

Works with

Crashes & Errors, with the
rest of Countly

Every feature reads the same live data, so an answer in Crashes & Errors doesn’t stop there. These are the handoffs built in.

All features
Adaptive Variables

Switch off the feature behind a crash for everyone, without shipping a release.

Open Alerts

Watch crashes as an alert source, and get told when they cross a threshold before anyone opens the page.

Open Drill

Every crash report is an event, so Drill can break crashes down like anything else.

Open Journeys

A crash can start a journey: apologize, or point to the fixed version.

Open Profiles

Open one occurrence and see the profile behind it, with its own stack and device facts.

Open Hooks

A crash the project has never seen before can start a hook that posts it wherever your team works.

Open SDK Manager

Turn crash tracking on or off from the server, and set how many breadcrumbs and trace lines a crash may carry.

Open

Data ownership

Stack traces stay in
your environment

A crash report carries the stack, device facts, app state and the profile behind it. It stays on the server you chose, with the rest of your data.

Data privacy
AspectFlexEnterprise
EnvironmentDedicated single-tenant instanceYour cloud, your data center or air-gapped
Data residencyThe Google Cloud region you chooseWherever you deploy, including air-gapped networks
Vendor accessOperated by Countly; access limited, granted by you and loggedNo default access
ISO 27001Certified
ISO 27017Certified
ISO 27018Certified
SOC 2Type II examined
TISAX®Participant*

*Countly Ltd. is a TISAX® Participant. TISAX® is a registered trademark of and governed by ENX Association. Learn more at enx.com/tisax

Try it

Every feature.
One data layer.

Start free trialAll features