menu_bookGetting Started

Welcome to Zharp

Zharp checks your websites, APIs, servers and scheduled jobs around the clock, opens an incident when something fails, and makes sure the right person hears about it. It also collects the errors, traces and logs of your own apps.

These docs are organised by what you want to do. Pick a starting point:

monitor_heart

Set up monitors

Websites, APIs, servers, databases, cron jobs and more, checked from four regions, with alerts when they fail.

description

Send logs

Collect logs from servers, hosting providers or your code, then search, tail and alert on them.

deployed_code

Monitor an application

Add the SDK for errors grouped into issues, traces across front end and API, sessions and replays.

stacked_line_chart

Publish a status page

Show your users what is up and what is down.

What Zharp does

Monitors run a check on a schedule — loading a page, calling an API, opening a port, connecting to a database, reading a certificate — from up to four regions: Europe, North America, Asia and Australia.
Incidents open automatically when a monitor goes down, and resolve themselves when it passes its checks again. You can also report one by hand.
Alerts and escalation decide who is told and how: the person on duty in your on-call schedule, an escalation policy with several steps, and alert channels such as Slack, Telegram, Discord or a webhook.
Status pages show your users the state of the monitors you choose.
Maintenance windows pause alerts for the monitors you pick while you work on them.
Logs keeps every log you send — from your servers, hosting providers, code or the API — in one place to search, follow live and alert on.
App Telemetry: add the Zharp SDK to a web, mobile or server app and see its errors grouped into issues, its traces across front end and API, its logs and its sessions — each tied to the user, device and release.
The Zharp agent runs on your own servers. It collects host metrics, logs and traces, and lets Zharp check databases on a private network.

Your first monitor in four steps

1
Create an account
Sign up with Google, GitHub or your email address. Email sign-ups confirm the address from a link Zharp sends you.
2
Open the create form
In the dashboard, click New on the Monitors page, or Create your first monitor if you have none yet.
3
Pick a type and a target
Leave Monitor type on Website monitor and enter the address under URL to monitor, for example https://example.com.
4
Create it
Click Create monitor. The first check runs straight away, from all four regions, and repeats every three minutes.

lightbulb

Out of the box, a new monitor emails the workspace owner and the person who created it when it goes down and when it recovers. To add Slack or another channel, see Quick Start.