Errors
Errors grouped and explained.
Errors from your apps arrive grouped by cause, with the change that started them and the fix Xovris can make.
XovrisOn its own
- A lit square is a feature people use today
- Newest: A missing page helps you on your way
Every feature in Errors, strongest first.
What fixes and prevents a problem comes first. Type to find one, or open a plan to see only its own.
Nothing here matches those words yet. Xovris notes the words, with no address and no cookie, so what is missing gets written.Ask Xovris instead
Lit: live and workingOpen: Xovris is still working on it
A missing page helps you on your way
A missing address shows where it stops and the closest page, with home, the docs and a box to ask; a server error says it is not your doing and offers to try again.
Repeated errors grouped automatically
The same error repeating is grouped once, while a different fault is kept apart.
Errors without a stack grouped too
Errors that carry no stack trace are grouped by their message pattern, with the grouping measured for precision.
New and unusual errors raised by themselves
A kind of error never seen from a source, or one arriving far faster than usual, is raised without a rule.
A new kind of error is flagged within a minute
An error pattern never seen before is flagged within 60 seconds of its first line arriving.
A broken screen behind a successful response, found
Xovris spots when a page answered fine but the visitor's screen broke, groups it by who it hit and reproduces it.
Blank pages after a 200 are caught
A screen that broke after a successful response - blank, an empty root or an error straight after load - is found from the visitor's own browser.
Error reports that are refused say what happens next
When an error report from a Sentry SDK or a browser is refused, the answer says what Xovris does next - nothing is lost and the next event is kept.
Every error's next step is something Xovris does
Every next step in Xovris's error messages is a door Xovris walks through for you, never a chore left for you.
Error messages that act, not instruct
Errors in Xovris come with the action that resolves them, carried out by Xovris, with the manual way beside it.
No error leaves you with homework
Each error's next step is pressed and done by Xovris, so you are never left with a list of things to try.
Error explanations that do the next step
When an explained error needs a port or a name changed, the step is a button Xovris carries out, with the manual way beside it.
The same error joins its group, and a kind never seen before is raised by itself
An error that arrives again joins its group instead of opening a new one. Errors are grouped by where in your own code they were thrown, with build hashes and chunk numbers taken out. An error with no stack is grouped by its type and message, with the parts that change each time set aside. A kind of error never seen from a source before opens one incident by itself. So does one that arrives 50 or more times at once.
The problem types page opens on the catalogue itself, and each problem on its answer
The page of every answer the API can refuse with had half its first screen empty. It now opens with the catalogue beside the headline: each kind of refusal, how many problem types it holds and the status codes they answer with, each row opening its own list. A problem’s own page shows the answer exactly as a client receives it beside its name, in the first screen.
A problem link opens its page, however it was copied
When an answer from Xovris links to the page that explains it, that page now opens even if the link reached you with its underscore turned into a slash or a hyphen, or cut short at it – never a page that is not there.
Any error read in plain English, free
You can now paste an error or a log line – “connect ECONNREFUSED 127.0.0.1:5432”, an nginx 504, a Java stack trace – and Xovris says what it means, the likely causes in order, what to do now and the documentation it rests on. It reads the clues in your paste, such as localhost inside a container or the real cause at the bottom of a stack trace, hides passwords and keys before reading, and keeps nothing unless you are signed in and ask it to. Three a day need no account.
A failing request points to the change behind it
When requests start failing, Xovris names the release and the repository behind the failures, so you start from the change that matters.
A flood of one error never hides the first of another
When one fault floods your app, Xovris drops only the repeats: the first occurrence of every other error still arrives in full.
The same error stays one issue across releases
Errors from Next.js, Node.js and React apps are grouped the same way when a release changes file names or chunk numbers, so one fault is one issue, not a new one every deploy.
The other areas
Words on this page, in plain English
Each technical word this page uses, said simply.
- Developer kit (SDK)
- A ready-made library a developer adds to an app so it can talk to a service.
- Program-to-program connection (API, APIs)
- A way for one program to ask another for information or to do something, without a person clicking through a website.