Observe

Observe is in beta

Observe is Capgo’s app-health view for native runtime signals. It helps you judge whether a release is healthy by combining launch timing, WebView timing, issue events, devices, versions, and deployment markers in one screen.

Open an app in the Capgo console and choose Observe. Select a period of 1, 3, 7, or 30 days; the view refreshes its cards, charts, and tables for that interval.

What you can see

The overview shows:

• Tracked devices and the number of native events in the selected period.
• Issue-free rate, issue count, and affected-device count.
• Native launch timing and WebView load timing at P50 and P90.
• A performance chart for launch and WebView timing, plus a volume chart for launches and issues.
• Version health by bundle version: events, devices, issue-free rate, launch P90, and WebView P90.
• Release markers showing when a version was deployed to a channel.
• An action breakdown with event and device counts, P50/P90/P99 timing, and whether Capgo classifies the action as an issue.

If the selected period has no matching native events, Observe shows an empty state rather than inferring that a release is healthy.

Investigate a signal

1. Pick a period that covers the release or incident.
2. Compare the candidate version with its prior stable version in Version health.
3. Check the action breakdown for a rising issue or slower P90 timing.
4. Select the action’s Logs control to open the matching raw logs for the same date range.
5. Use Log Insights for an error-first summary, then Logs for device-level evidence.

Use Observe with progressive rollouts

For a progressive rollout, keep a small cohort until the target version has enough real signals to compare with stable. Observe helps identify a deteriorating launch or WebView metric before raising rollout exposure; it does not automatically change the rollout. Configure auto-pause when you want Capgo to enforce a failure threshold.

Security updates tab

The Security updates subtab lists published advisories matched to native package and CLI versions your bundles already reported. Use it for remediation context after a release, not as proof that an app is fully patched. See Observe security updates for how matching works and what each status means.

Keep going from Observe

Connect Observe with Progressive rollouts for controlled delivery, Log Insights for prioritized errors, Logs for raw event evidence, and Observe security updates for advisory matching.