Documentation

How Vitrina Engine works, feature by feature. Each page explains what a thing does when you leave it alone as well as how to set it up, because the surprising behaviour is the part worth reading before an incident rather than during one.

• Monitors

  The thirty kinds of check, what an interval means once a failure has to be confirmed, and why a check that fails from one location is not an outage.

• Alerts and channels

  Where an alert goes: email, chat, webhooks, your phone, SMS, WhatsApp and a satellite handset. Which channels belong to a person, which to the team, and what has to be confirmed before anything is sent.

• Status pages

  Publishing a page for your own customers: which monitors appear on it, custom domains, passwords, and the people who subscribe to it.

• Error tracking

  Point an existing Sentry SDK at us, upload source maps, and read the issues an incident carried with it.

• Analytics

  A tag that stores nothing on a visitor's device, custom events, a shareable dashboard, and the alert for traffic that stops.

• Team and workspaces

  Roles, inviting people, confining somebody to one client's workspace, and single sign-on.

• REST API

  Read and write monitors, incidents, channels, status pages and more, with the same permission checks the dashboard uses.

If something here is wrong

Tell us at support@vitrinaengine.com. These pages are written by hand against the code rather than generated from it, which is what lets them explain why something behaves the way it does — and what makes them able to fall out of date. A page that contradicts the product is a bug in the page.