From an error to a fix
Finding the error is half the job. From an error group, or the root error of an incident, you can hand it to an e-volv agent that writes the fix, or to your tracker as a ticket. Both stay connected to the error afterwards.
Fix with e-volv
Press Fix with e-volv. e-volv starts an agent run with what Observer knows: the newest message and stack trace, the source line it points at, how often it happens, the trace, and the incident explanation when you start from an incident. The agent clones the linked repository, writes a change and opens a pull request.
The panel follows it: running, pull request open, merged or failed, with links to the run and the pull request. When the pull request merges, the error group is marked Resolved by PR #n. If the error comes back after that, the group regresses as usual and the panel says the fix did not hold.
Nothing merges by itself: a person presses the button and reviews the pull request. It needs the project linked to a GitHub repository in e-volv and the editor role; without a repository the panel says what to connect. Pressing it again while a fix is open shows that fix.
Fix on autopilot
A new-group, regression or release alert rule can start Fix with e-volv automatically. It creates a draft pull request after the group reaches the rule's minimum occurrence count, with at most 3 automatic starts per workspace each UTC day. A group with any existing fix is skipped. Automatic runs use the same managed-run allowance as manual runs. Autopilot currently supports GitHub only.
Owners
Assign an error group to any workspace member from its Owner picker, or use Assigned to me on the errors list. For new groups, Observer first tries the suspect commit author and then the first matching CODEOWNERS email. A manual assignment is never replaced by this sweep. Team owners are not assigned automatically.
Snooze and discuss
An error group can be snoozed for an hour, a day or a week, until it happens 10, 100 or 1000 more times, or until the next release. When the condition is met, Observer marks it regressed and sends the configured regression alert. Comments keep triage context beside the error. Any workspace member can comment, and mentioning a member with @name sends them an in-app notification. Only the author can edit or delete a comment.
Ticket sync
Create ticket opens one in any connected tracker: Jira, Linear, GitHub Projects, GitLab or ClickUp. It is filled in with the error, its counts, first and last seen, the environment, the release, the top stack frames and a link back. Link ticket attaches one that already exists, by key or URL.
The two stay in step:
- Done or closed in the tracker resolves the error group.
- A regression reopens the ticket with the new counts, or adds a comment where the tracker does not allow reopening.
- Resolving the group in Observer adds a comment to the ticket. It never closes your ticket for you.
Trackers are connected under Integrations; see integrations.