Connect Fastify
Set Fastify up with one pull request Xovris opens for you.
npx xovris@latest initpnpm dlx xovris@latest inityarn dlx xovris@latest initbunx xovris@latest initWill it fit your project?
Checks a package.json fits – in your browser, sent nowhere.
Checked right here, by the same rules the set-up command uses. Nothing is sent anywhere.
Run the wizard
Xovris sets Fastify up for you: connect GitHub once and Xovris raises one pull request that installs the SDK and writes the configuration, for you to review and merge – then it shows the first event the moment it arrives. Do it yourself instead: run one command in your Fastify project – it signs you in through your browser, installs the SDK, writes the configuration and proves the first event arrived, and you never copy a key.
Xovris makes this change for you: connect GitHub once and Xovris raises a pull request that lists every change, for you to review and merge.
What the wizard changes
Before writing anything the wizard shows each change. It records every change in a manifest, so removal is exact.
The wizard starts your Fastify app with Xovris loaded first; it is released once its install test passes in CI and the package is published.
This set-up works on npm, pnpm, yarn and bun, as of 14 November 2026.
- Detects Fastify and your package manager
- Opens your browser to sign you in – no key to paste
- Installs
@xovris/node - Writes to .env
XOVRIS_INGEST_URL,XOVRIS_INGEST_KEY - Waits until your first event is stored, then says so
- Records every change, so this takes it all out again:
npx xovris@latest remove
Variables it writes
The wizard writes these to .env and adds that file to .gitignore if it is not already ignored. It refuses to write a key into a file git tracks.
| Variable | Purpose |
|---|---|
XOVRIS_INGEST_URL | Where events are sent |
XOVRIS_INGEST_KEY | The ingestion key for this project (write-only: it can send events, never read them) |
If you already use another tool
The wizard looks for existing instrumentation first and tells you what it will do before it changes anything, so you never send each error twice.
| Found | What the wizard does |
|---|---|
| OpenTelemetry | Adds Xovris as a second OpenTelemetry exporter – your existing setup keeps working unchanged. |
| Sentry | Offers to run both side by side for a while, or to switch over; it never sends one error to Xovris twice. |
| Datadog and New Relic | Leaves the existing agent in place and offers to export through OpenTelemetry instead of adding a second agent. |
Check it works
The wizard ends by waiting for your first stored event. To check again later, run:
npx xovris@latest verifypnpm dlx xovris@latest verifyyarn dlx xovris@latest verifybunx xovris@latest verifyRemove it
This puts back every change the setup made and switches its key off, then confirms both:
npx xovris@latest removepnpm dlx xovris@latest removeyarn dlx xovris@latest removebunx xovris@latest removeWhat you get
| Signal | State |
|---|---|
| Server errors | Included |
| Browser errors | Not collected |
| Traces | Through OpenTelemetry |
| Metrics | Through OpenTelemetry |
| Logs | Not collected |
| Releases | Included |
| Readable stack traces | Included |
Supported versions
Written for Node.js 20.19 or later.
| Runtime | Node.js >=20.19 |
|---|---|
| Package managers | npm, pnpm, yarn, bun |
| Packages | npm install @xovris/node |
Your data is never used to train our AI. How your data is kept
A problem is called fixed only once it works again. How each fix is checked
XOVRIS LTD, registered in England and Wales, company number 17499910. Registered office: 66 Paul Street, London EC2A 4NA.