Errors
Deployment guard
Oxvel links each error to the deployment that introduced it, and reviews every release.
The suspect commit
When an error appears right after a deployment, Oxvel looks for the suspect commit among those that touched the files in the trace. It shows it to you on the incident page and can open a PR that reverts that commit.
The post-release review
30 minutes after each release, Oxvel runs a review. If the deployment brought new errors, you are notified by email or on Slack, with the suspect commit. Otherwise, a "no new errors" line is added to the log.
Knowing what's live
Oxvel looks for the live commit in three places, in this order.
- The
data-releaseof the capture script, or thereleasefield sent by your server. - Sentry releases.
- GitHub production deployments.