# Glowo Docs > Guides for Glowo — uptime monitoring, alerting, and public status pages. Set up monitors, route alerts, and publish incidents. ## Docs - [Glowo](https://docs.glowo.dev/): Uptime monitoring, alerting, and public status pages. Watch what you ship, tell people when it breaks. - [Getting started](https://docs.glowo.dev/getting-started): From signing up to a working monitor with alerts and a public status page, in about ten minutes. ## Monitors - [Monitors](https://docs.glowo.dev/monitors): What a monitor is, the eight types Glowo can run, and the settings every monitor shares. - [Assertions](https://docs.glowo.dev/monitors/assertions): Go beyond "did it respond" — assert on status codes, JSON fields, body text, headers and response time. - [Regions](https://docs.glowo.dev/monitors/regions): Where Glowo checks from, how multi-region checks are scheduled, and how regions affect false alarms. - [Confirmations and flapping](https://docs.glowo.dev/monitors/confirmations): The settings that decide when a failing check becomes an alert — and how to stop a flapping service from paging you all night. - [On-demand checks and URL probes](https://docs.glowo.dev/monitors/on-demand-checks): Run a check immediately instead of waiting for the next interval, or test a URL before you commit to a monitor. - [Uptime reports and history](https://docs.glowo.dev/monitors/reports): Heartbeats, hourly statistics, and downloadable SLA reports in JSON or CSV. - [Check error reference](https://docs.glowo.dev/monitors/check-errors): Every failure code a Glowo check can report, what it means, and what to do about it. ### Monitor types - [HTTP(S) monitors](https://docs.glowo.dev/monitors/http): Check a URL's status code, response time and body — with custom methods, headers, redirects, TLS verification and assertions. - [TCP monitors](https://docs.glowo.dev/monitors/tcp): Check that a TCP port accepts connections — for databases, brokers and anything that isn't HTTP. - [Ping monitors](https://docs.glowo.dev/monitors/ping): ICMP echo checks for hosts that have no port to talk to. - [DNS monitors](https://docs.glowo.dev/monitors/dns): Check that a DNS record resolves, and optionally that it resolves to the value you expect. - [DNS Diff monitors](https://docs.glowo.dev/monitors/dns-diff): Detect any unplanned change to a DNS answer — hijacks, mistaken edits, and provider drift. - [WebSocket monitors](https://docs.glowo.dev/monitors/websocket): Check that a WebSocket endpoint accepts connections, and optionally that it replies with what you expect. - [gRPC monitors](https://docs.glowo.dev/monitors/grpc): Check a gRPC endpoint via the standard health protocol, or just prove it speaks gRPC. - [Push monitors](https://docs.glowo.dev/monitors/push): Heartbeat monitoring for cron jobs, backups and batch pipelines — alert when something fails to check in. ## Alerting - [Alerting](https://docs.glowo.dev/alerting): The path from a failed check to a message in your inbox — confirmation, suppression, fan-out and retries. - [Acknowledging alerts](https://docs.glowo.dev/alerting/acknowledging): Stop repeat notifications for an ongoing incident without pausing the monitor or hiding the problem. - [Delivery history and retries](https://docs.glowo.dev/alerting/delivery-history): See whether an alert actually arrived — and what Glowo does when a channel is failing. ### Channels - [Notification channels](https://docs.glowo.dev/alerting/channels): The seven ways Glowo can reach you, and how to scope each one so the right alerts reach the right people. - [Email alerts](https://docs.glowo.dev/alerting/email): Send Glowo alerts to an email address, with one-click acknowledge and pause links. - [Slack alerts](https://docs.glowo.dev/alerting/slack): Post Glowo alerts into a Slack channel using an incoming webhook. - [Discord alerts](https://docs.glowo.dev/alerting/discord): Post Glowo alerts into a Discord channel using a webhook. - [Telegram alerts](https://docs.glowo.dev/alerting/telegram): Send Glowo alerts to a Telegram chat, group or channel via a bot. - [SMS alerts](https://docs.glowo.dev/alerting/sms): Text up to ten phone numbers when a monitor goes down. - [PagerDuty alerts](https://docs.glowo.dev/alerting/pagerduty): Send Glowo alerts into PagerDuty's Events API v2 for real on-call rotations. - [Webhook alerts](https://docs.glowo.dev/alerting/webhook): Send alerts to your own endpoint, with HMAC signing, custom headers and delivery IDs for deduplication. ## Status pages - [Status pages](https://docs.glowo.dev/status-pages): A public page that tells your users what is working, what is not, and what you are doing about it. ### Building the page - [Templates and theming](https://docs.glowo.dev/status-pages/design): Three layouts, your colours, your fonts, your logo. - [Components and groups](https://docs.glowo.dev/status-pages/components): Choose which monitors your users see, and organise them into groups that make sense to them. - [Publishing and previews](https://docs.glowo.dev/status-pages/publishing): Publish a status page, or share it privately with a preview link before it goes live. - [Custom domains](https://docs.glowo.dev/status-pages/custom-domains): Serve your status page from your own domain, with a certificate issued automatically. ### Incidents & updates - [Incidents](https://docs.glowo.dev/status-pages/incidents): Tell users what is happening, keep them updated, and leave a record when it is over. - [Maintenance windows](https://docs.glowo.dev/status-pages/maintenance-windows): Schedule planned work so alerts stay quiet, uptime stays fair, and users are told in advance. - [Postmortems](https://docs.glowo.dev/status-pages/postmortems): Publish what happened after an incident — inline, or linked to a document you already have. ### Reaching people - [Subscribers](https://docs.glowo.dev/status-pages/subscribers): Let users follow your status page by email, webhook or Slack — and pick which components they hear about. - [Embeds, badges and feeds](https://docs.glowo.dev/status-pages/embeds-and-badges): Put your status somewhere other than the status page — a badge in your README, a feed in a reader, or live data in your own app. ## Organization - [Workspaces](https://docs.glowo.dev/organization/workspaces): The container for everything — monitors, status pages, channels, members and billing. - [Projects](https://docs.glowo.dev/organization/projects): Group monitors and status pages so scoping, permissions and alerting stay manageable as you grow. - [Members, roles and invitations](https://docs.glowo.dev/organization/members-and-roles): Who can do what in a workspace, and how to invite people. - [Single sign-on (SSO)](https://docs.glowo.dev/organization/sso): Let your team sign in with your identity provider over SAML or OIDC, so access follows joiners and leavers. - [Audit log](https://docs.glowo.dev/organization/audit-log): A record of who changed what in your workspace. ## Plans - [Plans and limits](https://docs.glowo.dev/billing/plans): Every limit on every plan, what happens when you hit one, and how to change plan. ## AI agents - [AI agents](https://docs.glowo.dev/ai-agents): Let Claude Code, Codex, Cursor or another MCP client read and operate your monitoring. - [Connecting an agent](https://docs.glowo.dev/ai-agents/connecting): Connect Claude Code, Claude Desktop, Cursor or any MCP client to Glowo. - [Scopes and consent](https://docs.glowo.dev/ai-agents/scopes): Exactly what you are granting an AI agent, and how to take it back. ## REST API - [Glowo REST API](https://docs.glowo.dev/api): The Glowo REST API — base URL, authentication, the OpenAPI specification, and the conventions every endpoint shares. ## Account - [API keys](https://docs.glowo.dev/account/api-keys): Create, scope, rotate and revoke keys for scripts and integrations.