Quickstart
This guide walks you through the essentials: signing in, adding your first monitor, making sure you get notified when something breaks, and reading the results. You can be up and running in a few minutes.
1. Create an account or sign in
Sign up for a NoDisrupt account, or sign in if you already have one. Your account belongs to an organisation, which is the workspace your monitors, status pages and teammates live in. Once you are signed in you land in your organisation's dashboard, ready to add your first monitor.
2. Add your first monitor
Create a new monitor and choose the HTTP type to check that a website or web endpoint is responding correctly. You will configure a few things:
- URL to check - enter the address of the page or endpoint you want to watch,
for example
https://example.com. - Check interval - choose how often the monitor runs, such as every minute or every five minutes. More frequent checks detect problems faster.
- Expected status code - set the HTTP status code that counts as healthy,
typically
200. If the endpoint returns a different code, or fails to respond, the check is recorded as a failure.
Save the monitor and it will start checking on the schedule you chose.
Start with a single, important endpoint - your homepage or login page is a good first check. You can always add more monitors and tune the interval later.
3. Set up an alert contact
A monitor only helps if it can reach you. Add a contact method - such as an email address - so NoDisrupt knows where to send notifications, then make sure your monitor is set to alert that contact. When a check fails, you will be notified through the contact you configured rather than having to watch the dashboard.
4. View results and uptime
After the monitor has run a few times, open it to see its check history. Each result records whether the check passed, the response it received and how long it took, and these results roll up into an uptime percentage over time. This is where you confirm everything is healthy - and where you will look first when an alert comes in.
Want to understand the building blocks behind monitors, results and alerts? Read Core Concepts next.