Getting started
Asniher checks your websites, APIs, SSL certificates and cron jobs on a schedule, alerts you when something breaks, and publishes the result on a public status page. This guide takes you from sign-up to a working setup.
1. Create an account
Sign up at asniher.com/signup with an email magic link or your GitHub account. There is no password to manage. The Free plan needs no payment details.
2. Add a monitor
Choose a monitor type:
| Type | Use it for | Guide |
|---|---|---|
| HTTP(S) | Websites and APIs that should return an expected status code | HTTP monitors |
| Keyword | Pages that must (or must not) contain specific text | Keyword monitors |
| SSL | Certificates that are about to expire or are not trusted | SSL monitors |
| Heartbeat | Cron jobs, backups and workers that should check in regularly | Heartbeat monitors |
For a first monitor, pick HTTP(S), enter your URL (for example https://example.com) and choose a check interval. The shortest interval depends on your plan: 5 minutes on Free, 1 minute on Pro, 30 seconds on Team.
The first check runs within one interval. The monitor shows Pending until then, and Up or Down after.
3. Connect an alert channel
Your account email receives alerts by default. To alert a team channel, add Slack, Discord, Telegram or a webhook. See Alerts.
Each incident produces two notifications: one when the monitor goes down, and one when it recovers.
4. Publish a status page
Create a status page, choose a slug (for example acme), and select the monitors to show. The page is live at https://acme.status.asniher.com. See Status pages.
5. Optional next steps
- Add the status badge to your README or website footer.
- Point your own domain at your status page with a custom domain (Pro and Team).
- Read how false-alarm protection decides when an incident opens.
What happens when a check fails
- The check fails (wrong status code, timeout, connection error, missing keyword, certificate problem).
- Asniher re-checks after 30 seconds through a different DNS resolver.
- If it still fails and remote probes are available, probes in other regions confirm the failure.
- An incident opens and alerts go out. When a later check succeeds, the incident closes and a recovery alert is sent.
Heartbeat monitors skip steps 2 and 3: a missed ping is already a confirmed signal.