Integrations Monitoring
The error opens the bug. The fix resolves the error.
When Tripwire sees a new error above your threshold, Keel files a bug with the stack trace, the release and the number of people it hits. Close the bug and Tripwire marks the error resolved in the next release.
TypeError: cannot read “total” of undefined
HAL-233 · Backlog
- New error crosses 100 events an hourcheckout.ts:212 · v4.12.0Tripwire
- HAL-233 filed: Bug, Urgent, stack trace and 318 affected users attachedKeel
- Routed to Ana, who owns checkout.tsKeel
- Event count updates on the issue every 10 minutes1,204 events · 318 usersTripwire
- Fix merged, HAL-233 doneKeel
- Error marked resolved in v4.12.1; it reopens HAL-233 if it returnsregression watch onTripwire
What it does
Tripwire, wired into the work.
Thresholds, not noise
File only when an error passes a rate or a user count you set per project.
Owner from the code
Keel routes the bug to whoever changed the failing file most this month.
Counts that stay current
Events and affected users refresh on the issue, so priority can follow impact.
Regressions reopen
If the error comes back after the fix shipped, the bug reopens with the new release tag.
Set it up
Three steps, about 4 min.
- 01Connect your Tripwire organization
- 02Pick projects and a threshold for each
- 03Choose the team that receives new bugs
Permissions
What it can see, in writing.
- reads
- error titles, stack traces, counts, releases
- writes
- resolved state and issue links on errors
- never
- request payloads or user data beyond counts
- available
- Team and Business
Questions
About Tripwire.
Often connected together
Connect Tripwire in 4 min.
Available on Team and Business. Start a workspace, then add it from Settings → Integrations.