Crash Report Data¶
The Crash Report Data request comprises of elements that can be combined to query data related to crashes and other issues recorded by the Flurry SDK. The parameters that apply to this table:
https ://api-metrics.flurry.com/public/v1/data/crashReport/day/app/country?metrics=sessions,activeDevices,deviceImpactRate&dateTime=2019-06-01/2019-08-01&filters=[…]&topN=[..]&sort=[..]&having=[..]&format=[..]
Crash Report Metrics¶
Below are metrics that are available for reporting.
Metric |
Description |
---|---|
sessions |
number of times users accessed the application where an issue occurred |
activeDevices |
total unique devices that accessed the application where an issue occurred |
issueOccurrences |
total number of issues that occurred |
deviceImpactRate |
the ratio unique devices that experienced an issue to the unique devices that launched the app |
sessionImpactRate |
the ratio sessions that experienced an issue to the number of time users accessed the app |
issueFreeDeviceRate |
1 minus the deviceImpactRate |
issueFreeSessionRate |
1 minus the sessionImpactRate |
Crash Report Dimensions¶
Below are dimensions and dimension attributes that are available for reporting.
Dimension |
Description |
Value |
---|---|---|
company |
Flurry company account |
id, name (default) |
app |
Flurry app |
id, name (default), company|id, apiKey, platform|id, platform|name |
country |
Per country dimension totals |
id, name (default), iso |
appVersion |
App’s version id, name, company id, app id, deleted and filtered. Deleted and filtered are boolean (0 or 1) and reflect current status of an app version based on developer’s action on Flurry developer portal |
id, name (default), company|id, app|id, deleted, filtered |
language |
Language id and name |
id, name (default) |
region |
Region id and name |
id, name (default) |
backgroundSession |
Indicates background session |
id, name (default) |
errorType |
issueFree, UnknownError, RecoverableError, CaughtException, UnrecoverableCrash |
id, name (default) |
osVersion |
OS Version running at time of issue |
id, name (default) |
deviceModelCode |
Device model descriptor (e.g. iPhone10,1) |
id, name (default) |
fingerprint |
Flurry fingerprint code |
id, name (default) |
fingerprintStatus |
The status of the fingerprint data (see below for descriptions) |
id, name (default) |
variant |
The Flurry Config variant active at the time of the issue |
id, name (default) |
deviceModel |
The mapped model name of the device (e.g. iPhone 11 Pro) |
id, name (default) |
sdkVersion |
The version of the Flurry SDK integrated in the app |
id, name (default) |
timeToIssue |
The time between app launch and the issue. See below for description |
id, name (default) |
fingerprintStatus description¶
When an issue comes into Flurry Crash Analytics, it is fingerprinted to find the Issue Group into which it should be placed. The following are the status codes returned from the attempted processing.
SUCCESS - Fingerprint successfully created
QUOTA_REACHED - Your quota for active crash fingerprints has been reached.
RATE_LIMITED - The volume of crashes for your app has reached a level that the data has been rate limited.
INTERNAL_SERVER_ERROR - An issue occurred within the Flurry servers processing this data.
MISSING_ALL_SYM - None of the DSYM/Mapping files required for fingerprinting have not been uploaded.
MISSING_APP_FRAMEWORK_SYM - Some of the DSYM/Mapping files for frameworks used in the app required for fingerprinting have not been uploaded.
MISSING_APP_SYSTEM_SYM - Some of the DSYM/Mapping files for system resources used in the app required for fingerprinting have not been uploaded.
MISSING_APP_SYM - The DSYM/Mapping files for build of the app have not been uploaded.
MISSING_FRAMEWORK_SYSTEM_SYM - Some of the DSYM/Mapping files for system framework resources used in the app required for fingerprinting have not been uploaded.
MISSING_FRAMEWORK_SYM - Some of the DSYM/Mapping files for system resources used in the app required for fingerprinting have not been uploaded.
For MISSING_*_SYM codes, you can find information about how to upload DSYM/Mapping files here.
timeToIssue description¶
The timeToIssue dimension groups the data by the amount of time between the start of the session and the issue occurrence.
0-5 seconds
5-10 seconds
10-15 seconds
15-20 seconds
20-25 seconds
25-30 seconds
30-60 seconds
60-600 seconds
600-3600 seconds
3600-86400 seconds
Time Grain¶
hour
day
week
month
all
Data Retention¶
The data in the Crash Report table is retained for 30-days.
There are instances when you want to know the possible values for dimensions before running metric queries. For example: list names and api keys for all apps on your company account with Crash enabled
https://api-metrics.flurry.com/public/v1/data/crashReport/day/company/app;show=name,apiKey?metrics=...
In general, to see a value other than default name returned for the given dimension, add
;show=all
or
;show=id (any other value listed in the value column above for the given dimension
after the dimension name
https://api-metrics.flurry.com/public/v1/data/crashReport/day/company/country;show=all/category?metrics=sessions,activeDevices&dateTime=2017-05-01/2017-05-02
https://api-metrics.flurry.com/public/v1/data/crashReport/day/company/country;show=iso/category?metrics=sessions,activeDevices&dateTime=2017-05-01/2017-05-02
Refer to Analytics API for all the parameters, list of error codes and other general information about this API
Example key App Usage metrics queries¶
For all your apps, daily Sessions, daily Active Devices, New Devices for 2 days*: * note that since there is no app info included in the filter, results will include all apps for your company
Request:
https://api-metrics.flurry.com/public/v1/data/appUsage/day/app?metrics=sessions,activeDevices,newDevices&dateTime=2016-07-01/2016-07-03
Response:
{
"rows": [{
"dateTime": "2016-07-01 00:00:00.000-07:00",
"app|name": "foo",
"sessions": 372,
"activeDevices": 123,
"newDevices": 32},
{
"dateTime": "2016-07-01 00:00:00.000-07:00",
"app|name": "bar",
"sessions": 1120,
"activeDevices": 487,
"newDevices": 34},
{
"dateTime": "2016-07-02 00:00:00.000-07:00",
"app|name": "foo",
"sessions": 421,
"activeDevices": 140,
"newDevices": 12},
{
"dateTime": "2016-07-02 00:00:00.000-07:00",
"app|name": "bar",
"sessions": 1164,
"activeDevices": 453,
"newDevices": 51}]
}
For a specific app, daily Sessions, Active Devices and New Devices for 2 months:
Request using Flurry API key:
https://api-metrics.flurry.com/public/v1/data/appUsage/day?metrics=sessions,activeDevices,newDevices&dateTime=2019-06-01/2019-08-01&filters=app|apiKey-in[3WD7Q8329867K7MY6RNS]
Request using App name:
https://api-metrics.flurry.com/public/v1/data/appUsage/day?metrics=sessions,activeDevices,newDevices&dateTime=2019-06-01/2019-08-01&filters=app|name-in[appname]