Engineering
Fix product errors before customers report them
Monitoring sees customers hitting an error before a support ticket exists.
The product signal auto-summons the same Novix agent a person would summon with @Novix. It combines the alert, customer context and code, then opens a tested pull request for review.
How Novix gets involved
A monitoring signal auto-summons Novix.
Sentry posts a signed webhook. Rollbar and Datadog do not sign theirs, so those arrive on a secret webhook url instead. PagerDuty and Statuspage are polled for triggered incidents.
How the agent handles it
The alert becomes a task, with what it carried
A new Sentry issue or a triggered incident becomes a task in its own right. Sentry stack frames are compacted onto it, so the run starts holding the error rather than a title about it.
The monitoring tool is read back during the run
ContextPulls live evidence from your connected code and monitoring tools.Recent error events, logs and open incidents are pulled from the tools you connected and attached as evidence, fenced as untrusted before anything reaches a prompt.
Written against the error, not a description of it
DiagnoseThe root-cause investigation: it opens the files it suspects in your repo, then names the cause, a confidence and the areas it affects.The diagnosis stage gets the stack, the events and the real file list of the routed repository, and opens the files it suspects before it names them.
Nothing about this path skips a stage
An alert takes the same nine stages a customer report does, including the adversarial pass over the diagnosis and your own build and tests against the patch.
What your team gets
- One task per alert, carrying the frames the alert arrived with
- The error events attached to the diagnosis, so a reviewer can see what it read
- A pull request when it turns out to be a real defect
It never touches the incident
Novix reads your monitoring tools and writes back to the task. It does not acknowledge, resolve, escalate or page anybody, and none of these connectors implements a write.
Works with
- Sentry
- Datadog
- Rollbar
- PagerDuty
- Statuspage
All five raise tasks. All five are also read back as evidence during a run, whatever raised it.
Try it on a real customer problem.
Connect the place reports or product signals already arrive. The same agent takes it from evidence to a tested pull request.