Error tracking that tells you when something breaks
Vigilon groups repeated errors into one, emails your team when a new error appears or a fixed one comes back, and opens each backend error on the request or job run that failed. For Node.js, Python, Next.js, React and browser apps.
See what broke, how often, and since when.
One group per problem
Repeats of the same error land in one error group, with how often it happens and when it was first and last seen. Numbers and IDs in the message are ignored, so Order 18233 not found and Order 90412 not found count as one.
An email when it is new
The first time a group appears, your team gets an email within about a minute. It names the project, the environment, the app, and whether a request or a background job failed.
An email when it comes back
Resolve a group once the fix ships. If the error happens again, the group reopens as Regressed and sends a regression email, whether or not you deployed.
Mute without losing count
Mute a noisy group for a set time or until you unmute it. It stays in the list and keeps counting occurrences; it just stops emailing.
The failing request, step by step
A backend error opens on the trace of the request or job run behind it, with its database queries, its outgoing calls and the stack trace of the exception.
Server and browser errors together
Errors from Node.js and Python apps sit in the same list as browser, React and Next.js errors, with browser stacks read through your source maps.
From the first exception to one email.
- 01
Install the SDK
Add the Node.js or Python package, or the browser SDK. Unhandled exceptions and failed requests are recorded from the first request.
- 02
Vigilon groups what arrives
Errors with the same app, type and message become one group. Browser errors are grouped by the code that threw them, read through your source maps.
- 03
Your team gets one email
Every active workspace member is emailed by default. Admins choose the recipients, or turn alerts off for a project or for an environment such as staging.
- 04
Fix it and resolve it
Resolve the group when the fix ships. If the error returns, Vigilon reopens it and emails your team again.
Errors are recorded from the first request.
Install the SDK for your runtime and start it with your app. Errors your code catches and handles are recorded with one call: recordException() in Node.js or record_error() in Python. NestJS apps add that call to a global exception filter.
Docs Node.js quickstartPython quickstartNext.js quickstartReact quickstartBrowser quickstartGrouping and alerts
npm install @vigilon/node
export VIGILON_API_KEY="[YOUR_API_KEY]"
node --import @vigilon/node/register server.jsUse a Server key from your project's API Keys settings. The flag starts Vigilon before your app code, which is how it records Express and Fastify errors. NestJS catches errors in its own exception layer, so add a global exception filter that calls recordException(). NestJS exception filter
Error tracking in Vigilon and Sentry.
Sentry is the error tracker most teams already know. This is how the error side compares, with a source for every Sentry fact.
| Capability | Sentry | Vigilon |
|---|---|---|
| Error groups with resolve, mute and regressions | YESResolve or archive an issue; one that comes back after resolving is marked Regressed [13] | YES |
| Email when a new error appears or a fixed one returns | YESAlerts on new issues, and regression emails by default [14] [15] | YES |
| Slack, PagerDuty and issue-tracker alerts | YESSlack, PagerDuty, Microsoft Teams, Jira and more [6] | NOT YETEmail only today |
| Browser apps | YES [12] | ERRORSBrowser, React and Next.js SDKs, with source maps and breadcrumbs |
| Session replay | YESWeb and mobile [7] | NO |
| AI that analyzes and fixes issues | ADD-ONSeer, $40 per active contributor a month [3] | YOUR AGENTVigilon sells no AI; the agent you already use reads the data |
- [3] Seer pricing: sentry.io/product/seer. Checked 2026-10-25.
- [6] Sentry integrations: docs.sentry.io/organization/integrations. Checked 2026-10-25.
- [7] Sentry Session Replay: sentry.io/product/session-replay. Checked 2026-10-25.
- [12] Sentry platforms: docs.sentry.io/platforms. Checked 2026-10-25.
- [13] Sentry issue states: resolved, archived, regressed: docs.sentry.io/product/issues/states-triage. Checked 2026-10-25.
- [14] Sentry issue alerts: the new-issue trigger: docs.sentry.io/product/alerts/create-alerts/issue-alert-config. Checked 2026-10-25.
- [15] Sentry notifications: regression emails: docs.sentry.io/product/alerts/notifications. Checked 2026-10-25.
Error tracking questions.
What is error tracking?
Error tracking records the exceptions and failed requests your app produces in production, groups repeats of the same problem together, and tells you when a new one appears. Vigilon does this for Node.js, Python and browser apps, and links each backend error to the trace of the request or job that failed.
When does Vigilon send an error email?
The first time a new error group appears, and the first time a resolved group happens again. Each group sends at most one new error email, and one regression email each time it is resolved. Emails go out within about a minute of the error reaching Vigilon; there is no digest.
Will a bad deploy flood my inbox?
No. Vigilon sends at most 5 error emails per project and 15 per workspace in any 10 minutes. The rest wait, regressions first, and any still waiting after 24 hours are dropped. An alert for a group that was resolved or muted in the meantime is cancelled.
How does Vigilon decide two errors are the same?
Backend errors with the same app, environment, exception type and message are one group, once numbers and long IDs in the message are replaced. A deploy does not split a group. Browser errors are grouped by the first functions from your own code on the stack, read through your source maps.
Do I need to change my code?
Not for unhandled exceptions and failed requests in Express, Fastify, FastAPI, Flask and Django: install the SDK and start it with your app. Errors you catch and handle yourself need one call, recordException() in Node.js or record_error() in Python. NestJS catches errors in its own exception layer, so it needs one global exception filter that calls recordException().
Can I get error alerts in Slack?
Not yet. Error alerts are sent by email today. Admins choose who receives them, per workspace, per project and per environment.
Which plans include error tracking?
Every plan. Plans differ in how many requests, job runs and browser errors they include and how long data is kept, and Starter is free for its first two months.
Everything else Vigilon watches.
Cron job monitoring
Every run of a scheduled job or queue worker is a trace, and a job that misses its schedule shows as overdue.
Distributed tracing
Every request with an error and every slow request kept as a full trace, with its database queries and outgoing calls.
Endpoint monitoring
Traffic, p50 and p95 latency, error rate and status codes for every route, counted from all requests before any trace is dropped.
Anomaly detection
Error spikes, slower endpoints, error surges, missed job runs and failing job streaks, each checked against its own history. On Team and Pro.
MCP server
Claude Code, Codex, VS Code, Claude and ChatGPT read your errors, traces and job runs over a hosted, read-only MCP server.
Start free for two months.
Pick a plan, add the SDK, and Vigilon starts watching your app. Starter is free for your first two months, with no card needed.