Queries

All five commands share these common flags:

• --platform ios or --platform android — filter by platform (default: both)
• --start <ISO date> and --end <ISO date> — explicit time range
• --days <N> — show data from the last N days (mutually exclusive with --start/--end)
• --project-id <id> — run against a specific project without needing a project directory. When passed, the command will not try to create a new EAS project where one is unneeded.
• --json — machine-readable output (implies --non-interactive)
• --non-interactive — fail instead of prompting

Default time range is the last 60 days when none of --days, --start, --end is given.

Supported Metrics

App-startup metrics

Used by observe:metrics-summary and observe:metrics.

Navigation metrics

Used by observe:routes. Measured per route name.

eas observe:metrics-summary

Shows per-version statistical aggregates for one or more metrics, with separate tables per platform.

Stat flags: min, max, median (alias med), average (alias avg), p80, p90, p99, eventCount (alias count).

Default stats: median + eventCount in the table; all stats in JSON.

Table layout:

• One table per metric (with merged value + event count cells, e.g. 0.45s (150))
• Each table shows iOS and Android in separate sections
• App Version column includes build numbers in parentheses (e.g. 1.2.0 (42))
• Footer row per platform shows total events per metric
• Update IDs are omitted from the table to keep output readable when a version has many updates; they are included in the JSON output as an array per version

JSON output shape:

eas observe:metrics

Shows individual performance metric samples, paginated. The metric is a positional argument, not a flag. If omitted and running interactively, prompts for selection; in non-interactive mode it throws an error.

Sample-specific flags:

• --sort <oldest|newest|slowest|fastest> — defaults to oldest
• --limit <N> — samples per page (default 10, max 100)
• --after <cursor> — pagination cursor from the previous run
• --app-version <version> — filter by app version string
• --update-id <id> — filter by EAS update ID

Table layout:

• Summary header shows the metric name, time range, and total sample count across all versions (e.g. TTI samples for the last 60 days — 1,234 total events)
• Columns: Value, App Version (with build number), Update (only when any sample has one), Platform, Device, Country, Timestamp
• When hasNextPage is true, prints Next page: --after <endCursor> hint below the table
• JSON output also includes sessionId, easClientId, and a customParams object per sample

eas observe:routes

Shows per-route statistical aggregates for navigation metrics (Cold TTR, Warm TTR, Nav TTI), grouped by route name with separate sections per platform.

Routes-specific flags:

• --metric <cold_ttr|warm_ttr|nav_tti> — navigation metric(s) to display, can be repeated. Defaults to all three.
• --stat <median|p90|count> — statistic(s) per metric. Aliases: med → median, event_count / eventCount → count.
• --limit <N> — routes per page (default 50, max 200, different from metrics/events which default to 10).
• --after <cursor> — pagination cursor from the previous run.
• --app-version <version> — filter by app version string.
• --build-number <number> — filter by app build number (routes-only).
• --route-name <name> — filter by route name. Repeatable; only the listed routes are returned across both platforms. Duplicates are de-duplicated; omitting the flag returns all routes.
• --update-id <id> — filter by EAS update ID.

Default stats: median + count in the table; median, p90, count in JSON.

Table layout:

• Summary header with the chosen stats and time range, e.g. Med, P90 values (navigation count) for the last 7 days.
• Separate iOS and Android sections.
• First column is Route, followed by one column per metric/stat. With both display stats and count, cells are merged like 0.32s (1240).
• Each platform has its own pagination hint: Next page (iOS): --after <endCursor>.

JSON output shape:

eas observe:events

Shows custom events emitted by the app via the logEvent API in expo-observe. Behavior depends on what is passed:

Events-specific flags:

• --all-events — when no event name argument is given, list all events instead of the name summary. Cannot be combined with an event name argument.
• --session-id <id> — filter to events from a single session (events-only)
• --app-version <version> — filter by app version string
• --update-id <id> — filter by EAS update ID
• --limit <N> — events per page (default 10, max 100)
• --after <cursor> — pagination cursor

Table layout (event listings):

• Summary header: <event-name> events <time range> or Custom events <time range> for --all-events, with a total event count when available
• Columns: Timestamp, Event (only when listing across multiple names), Severity (only when at least one event in the page has a severity), App Version (with build number), Platform, Device, Country
• Next page: --after <endCursor> hint below the table when there is a next page

Empty-result helper: if a specific event name is queried and returns no events, the command prints a yellow No events found matching "<name>" warning followed by the available event names + counts in the same time range — useful for fixing typos.

Truncation note: the event-names summary may flag Result is truncated; not all event names are shown. when there are more names than the server returns in a single response.

JSON output shape (event listing):

The name-summary mode returns { "names": [{ "eventName": "...", "count": 123 }], "isTruncated": false }.

eas observe:versions

Shows app version hierarchy with build numbers, OTA update IDs, and event counts per version.

No metric-related flags. Output shows separate iOS and Android tables with columns: App Version, First Seen, Events, Users, Builds (count), Updates (count).

JSON output returns the full nested hierarchy with buildNumbers[].easBuilds[] and updates[].easBuilds[], including firstSeenAt, eventCount, and uniqueUserCount at every level.

Common Workflows

“What are my app’s startup times right now?”

“Which TTI samples were slowest this week?”

“How fast are over-the-air updates downloading in the field?”

“Which screens are slowest to navigate to?”

“How does navigation perform on just the routes I care about?”

“What custom events is my app emitting?”

“Show me every error event from one user’s session.”

“What versions of my app are in the field?”

“Show me metrics for a specific project without needing to be in the repo”

“Get JSON for scripting”

Notes

• Requires the user to be logged in (eas login).
• When --project-id is provided, the command does not require running inside an EAS project directory; otherwise the project ID is read from the local app.config / app.json. If using this option, ensure that you are logged in as a user that has access to the specified project.
• observe:metrics-summary does not print update IDs in the table but still returns them in JSON for scripting or piping into other commands.