Errors

Query fragment error analytics — render failures and parsing errors reported by client apps.

$ xc analytics errors [options]

Options

In addition to the common options, this command supports fragment and error message filtering:

Option	Abbr	Description
`--fragment`	`-f`	Filter by fragment name (supports wildcards)
`--error`	`-e`	Filter by error message (supports wildcards)

Both --fragment and --error accept wildcard patterns. For example:

--fragment /user/profile/* — errors in any fragment under /user/profile/
--error "*parsing*" — errors containing "parsing" in the message

Full Option Reference

Option	Abbr	Description	Default
`--workspace`	`-w`	Workspace to query
`--project`	`-p`	Project to query	Current project
`--channel`	`-c`	Filter by channel name
`--version`	`-v`	Filter by version number
`--platform`	`-t`	Filter by device platform
`--fragment`	`-f`	Filter by fragment name
`--locale`	`-l`	Filter by device locale (user's region setting)
`--country`	`-n`	Filter by country
`--error`	`-e`	Filter by error message
`--range`	`-r`	Query the past N days	`7`
`--interval`	`-i`	Aggregation granularity	`daily`

Output Columns

Column	Description
Period	Time bucket based on the selected interval
Channel	Channel name
Version	Deployment version
Fragment	Fragment name
Platform	Device platform
Locale	Country code from device's locale setting
Country	Country geolocated from device IP
Error	Error message
Count	Number of occurrences

Columns corresponding to filters you specify are promoted to headers and removed from the table. Exception: a --fragment filter with a wildcard pattern keeps the Fragment column, since multiple fragments can match.

Examples

# All errors over the past 7 days
$ xc analytics errors

# Errors for a specific fragment
$ xc analytics errors -f /checkout

# Search for a specific error pattern
$ xc analytics errors -e "*null*" -r 30

# Production errors on Android, daily
$ xc analytics errors -c production -t android