Is it our fault?
Reads every error your services emit, decides whether it is your fault, and files the issue.
How it works
-
Connect with OpenTelemetry
Point your OpenTelemetry SDK or Collector at the ingest endpoint with a workspace token. Or ask ourfault to open the pull request that connects a service.
-
Every error is read
Records that carry an exception are grouped into failures. A failure seen before is counted, not judged again.
-
New failures are judged
Each new failure is weighed against your recent deployments and the failing request's trace. The verdict is a fault in your code, someone else's, or too close to call.
-
Your fault becomes an issue
ourfault reads the files the stack trace names and files an issue with the root cause in your repository. When the fix is small and proposed fixes are on, a draft pull request with it follows.
-
Your next deployment settles it
For three days after it, ourfault watches for the failure and says on the issue whether it came back. When it did not, the issue is closed.
-
Pull requests are told
A pull request that changes the code an open failure runs through gets a check naming it. The check informs and never blocks a merge.
What else it does, how it is measured, and what is kept: read more.
Free to start; usage is metered and shown in the workspace.