---
id: gh-eas-observe
name: "eas-observe"
url: https://skills.yangsir.net/skill/gh-eas-observe
author: expo
domain: mobile
tags: ["eas", "expo", "performance", "monitoring", "mobile"]
install_count: 18600
rating: 4.60 (120 reviews)
github: https://github.com/expo/skills/tree/main/plugins/expo/skills/eas-observe
---

# eas-observe

> 此技能用于为Expo项目集成EAS Observe，自动追踪启动、导航和自定义事件性能，并通过EAS CLI查询指标或解读仪表盘数据，帮助快速诊断冷热启动、页面跳转等场景的性能瓶颈，优化用户体验。

**Stats**: 18,600 installs · 4.6/5 (120 reviews)

## Before / After 对比

### 启动性能排查效率

**Before**:

在没有此技能前，开发者手动分析启动性能，需要编写自定义日志、反复测试，耗费大量时间且容易遗漏关键指标，定位慢启动原因通常需要数小时。

**After**:

使用此技能后，自动收集冷启动、热启动、TTI等关键指标，通过CLI或仪表盘一目了然，定位瓶颈时间缩短至几分钟，并支持按版本和路由细分。

| Metric | Before | After | Change |
|---|---|---|---|
| 排查时间 | 60分钟 | 10分钟 | -83% |
| 遗漏错误率 | 30% | 5% | -83% |

## Readme

# EAS Observe

> **EAS service - costs apply.** EAS Observe is a paid Expo Application Services product with free-tier limits. Ingesting and querying production metrics counts against your plan's event/usage allowance. Review https://expo.dev/pricing before enabling it in production.

EAS Observe tracks startup, navigation, and custom-event performance from production Expo apps.

> **Source of truth:** https://docs.expo.dev/eas/observe/ — always consult the canonical docs when API details matter, especially get-started, configuration, integrations, and the metrics reference. EAS Observe is evolving; this skill's references are written to stay accurate but may lag the docs.

## Which reference to read

The three reference files in `./references/` cover the three things people typically need this skill for:

- **Adding EAS Observe to a project** → [`./references/setup.md`](./references/setup.md). Install, wrap the root layout (`AppMetricsRoot` on SDK 55, `ObserveRoot` on SDK 56+), call `markInteractive()` (global on SDK 55, via the `useObserve()` hook on SDK 56+), optional per-route navigation metrics through the Expo Router / React Navigation integrations, and user-defined events via `Observe.logEvent` (SDK 56+).
- **Querying metrics from the terminal** → [`./references/queries.md`](./references/queries.md). The five `eas observe:*` commands — `metrics-summary`, `metrics`, `routes`, `events`, `versions` — with flags, table layouts, JSON shapes, and common workflows.
- **Reading a dashboard or CLI output** → [`./references/metrics.md`](./references/metrics.md). Target thresholds per metric, what the TTI `frameRate.*` params mean, and diagnostic patterns for telling slow-but-smooth startup apart from main-thread contention or hard blocks.

## Quick links to the docs

- Get started: https://docs.expo.dev/eas/observe/get-started/
- Dashboard guide: https://docs.expo.dev/eas/observe/dashboard/
- Metrics reference: https://docs.expo.dev/eas/observe/reference/metrics/
- Expo Router integration: https://docs.expo.dev/eas/observe/integrations/expo-router/
- React Navigation integration: https://docs.expo.dev/eas/observe/integrations/react-navigation/
- User-defined events: https://docs.expo.dev/eas/observe/events/
- Configuration: https://docs.expo.dev/eas/observe/configuration/

## Submitting Feedback
If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
```bash
npx --yes submit-expo-feedback@latest --category skills --subject "eas-observe" "<actionable feedback>"
```
Only submit when you have something specific and actionable to report. Include as much relevant context as possible.


---
*Source: https://skills.yangsir.net/skill/gh-eas-observe*
*Markdown mirror: https://skills.yangsir.net/api/skill/gh-eas-observe/markdown*