Read release health
See issue-free devices, native issues, launch P90, and WebView P90 for the reported versions in one view.
Capgo Observe, beta
Know when a release needs attention.
See what changed after your rollout, compare health by reported version, and move from a bad signal to the devices and logs behind it.
- 01DeployMark the version, channel, and deployment date.
- 02ObserveCompare reported health before support tickets arrive.
- 03InvestigateFollow the trend into errors, versions, and devices.
Stop treating production as a black box
Your rollout is only done when you know what happened next.
Observe gives every release a health view, then gives you the evidence to decide what deserves action.
Keep rollout context
Use release markers for version, channel, and deployment date as you read the signals.
Follow the evidence in Logs
Use grouped failures, affected versions, devices, and action logs to investigate a trend.
See the release, not just the metric
Start broad. Narrow fast. Know where to look next.
Read all-version health, compare the versions that diverge, and use the release marker to connect the change to the impact.
Explore Live UpdatesAll versions summary
Read issue-free devices, native issues, launch P90, and WebView P90 before narrowing your investigation.
Version breakdown
Compare reported app versions when health or timing differs from the overall picture.
Action breakdown
Separate launches, WebView loads, native issues, and update activity while you investigate a trend in Logs Insights.
From signal to evidence
Do not hand your team a chart. Hand them the trail.
Observe
See which reported version changed the release picture.
Compare health and timing with the context of what you deployed, where, and when.
Logs Insights
Identify the errors, versions, and devices behind the trend.
Use Logs Insights to group errors by category, follow the daily trend, and identify affected versions and devices. Then open filtered raw action logs for the details.
Read the Logs guide
Customer proof
Release teams rely on Capgo in production
Observe runs on the same platform thousands of teams already use to ship live updates.
Being able to add Device ID's to certain groups and push the changes to only certain groups is a life saver.
Getting set up took less than a day. Channel-based rollouts let me test on my own device before anything hits production users.
Observe every rollout
Ship with proof,
not just hope.
Put deployment history, release health, and Logs Insights in one release workflow.
human support from Martin
Try free for 14 days