---
title: "Tutorials Overview"
url: "https://www.openstatus.dev/docs/tutorial/getting-started"
date: "2018-10-20"
author: "openstatus"
description: "Step-by-step tutorials to create monitors, wire up notifications, publish status pages and reports, and drive it all from the openstatus CLI."
category: "Tutorials"
---

Our tutorials walk you end-to-end through the openstatus workflow: monitor an endpoint, get alerted when it fails, publish a status page, and communicate during an incident — then automate the whole thing from the CLI.

If you're new, follow the tutorials below in order. Each one builds on the previous and takes 5–10 minutes.

Prefer video? The same path is on YouTube as the [openstatus tutorials playlist](https://www.youtube.com/playlist?list=PLejPLN0oV6WA_HyBXwRHOytolZFZX1pXG).

## Get started

1. **[Create an uptime monitor](/docs/tutorial/create-your-first-monitor)** (~5 min) — set up uptime monitoring for your first endpoint.
2. **[Wire up your first notification](/docs/tutorial/your-first-notification)** (~5 min) — create a notification channel, attach it to your monitor, and confirm an alert lands.
3. **[Create a status page](/docs/tutorial/create-your-first-status-page)** (~5 min) — build a public status page to communicate service health to your users.
4. **[Publish your first status report](/docs/tutorial/your-first-status-report)** (~10 min) — walk the four-state incident workflow (investigating → identified → monitoring → resolved) from the dashboard.

## Automate with the CLI

Once you're comfortable with the dashboard, manage your stack as code:

- **[Get started with the openstatus CLI](/docs/tutorial/get-started-with-openstatus-cli)** (~10 min) — install the CLI, authenticate, and export your workspace to Terraform configuration you can version-control.
- **[Manage status reports from the CLI](/docs/tutorial/manage-status-reports-cli)** (~10 min) — open, update, and resolve a status report from the terminal during an incident.

## What's next

- Explore the [how-to guides](/docs/guides/getting-started) for specific tasks and advanced scenarios.
- Dive into the [explanations](/docs/concept/getting-started) to understand the concepts behind the features.
- Look up details in the [reference](/docs/reference/overview).