Product documentationVersion 1.0 · October 2026
obsrvly Documentation
For everyone who uses obsrvly to watch websites, APIs and scheduled jobs.
obsrvly watches your websites, APIs, servers and scheduled jobs. It runs checks on a schedule. When a check keeps failing, it alerts your team.
In this walkthrough you set up an alert channel and a URL monitor.
Start here
All 15 chaptersThis chapter explains what obsrvly does. You create your first monitor and alert, learn the main ideas, and let obsrvly suggest monitors for your site.
You work with monitors. A monitor watches one thing, such as a web address, a server port or a certificate.
In this walkthrough you set up an alert channel and a URL monitor.
These terms appear throughout this guide.
Discovery tests your site and suggests monitors you can keep.
A glossary of technical terms ends the chapter.
Browse by chapter
15 chapters · 121 pagesGet started
01Get started
This chapter explains what obsrvly does. You create your first monitor and alert, learn the main ideas, and let obsrvly suggest monitors for your site.
Monitor
02Monitors
A monitor checks one thing on a schedule and tells you when it breaks.
03Monitor settings
Most monitor types share the same settings. This chapter shows how often checks run, how long a check may wait, and where checks run from.
04Assertions
Assertions are your checklist for a healthy response.
05Heartbeats
A heartbeat monitor watches jobs that run on their own, such as backups, cron jobs, queue workers and scheduled pipelines.
06DNS and mail checks
A DNS monitor checks that your domain's records say what they should.
07Browser monitors
A browser monitor checks that a visitor can finish a task on your site, such as signing in.
Protect & alert
08Secrets
Secrets let your monitors use passwords, tokens and keys without writing them into the monitor.
09Alerting
This chapter explains when obsrvly alerts you, how to control it, and how to see what was sent.
10Alert channels
An alert channel is a place obsrvly sends alerts to: an email inbox, a chat room, or a URL on your own system.
11Webhooks
A webhook is an HTTPS address on your own server. obsrvly sends alerts to it as JSON.
Share
12Status pages
A status page is a public web page that shows whether your services are up.
Build
13API
The obsrvly API (application programming interface) lets your scripts and CI jobs do most of what you do in the dashboard.
Manage
14Account and team
In obsrvly, your work belongs to a team, not to one person.
15Security and data
This chapter covers what obsrvly does to keep your data safe.
Conventions in this guide
- Dashboard labels appear in bold, as the dashboard shows them, for example + new monitor. Many labels are lowercase.
- An arrow shows a path through the menus. For example, alerting → channels means select alerting, then channels.
- Values you type, messages and API field names appear in
code. - Text in angle brackets, such as
<channel-id>, is a placeholder. Replace it with your own value. - Technical terms are defined in the glossary (1.5).