Product guide

Use the dashboard to ship reliable uptime

A step-by-step walkthrough to get oriented, create monitors, deploy server agents, and publish status pages your customers can trust.

Find your way around

  • Overview: high-level health and recent incidents at a glance.
  • Monitors: create and manage HTTP/API checks, pause/resume, and view history.
  • Server agents: provision lightweight agents for deeper host metrics.
  • Status & trust: public status pages, incident timelines, and customer-facing audit logs.
  • Alerts: route notifications to email, Slack, Discord, or webhooks.

Tip: every dashboard page now includes a back button plus a “Back to dashboard” shortcut so you can hop between sections quickly.

Create an uptime monitor

  1. Open Dashboard → Monitors and click New monitor.
  2. Choose the monitor type (HTTP/HTTPS, TCP, etc.) and provide the target URL or host.
  3. Set the check interval, expected status code range, and optional headers or body.
  4. Assign tags (e.g., prod, api) to group and filter later.
  5. Pick alert channels and save. You can pause/resume any monitor from the list view.

The monitors page shows live status, group filters, and a refresh action. If you see “loading,” give it a second—the list streams in before empty states appear.

Deploy a server agent

  1. Go to Dashboard → Server agents and select Install agent on the server you want to watch.
  2. Copy the generated install command. It warns if you are not running with sudo and asks for confirmation before continuing.
  3. Run it on the target host. The agent registers, ships heartbeats, and streams CPU/memory basics.
  4. Back in the dashboard, confirm the agent appears online. Use tags/regions to organize fleets.

Agents are HTTPS-only and lightweight. If a host stops reporting, you will see it marked degraded/unknown on the overview and server pages.

Publish status and trust pages

  1. Create or open a status page from Dashboard → Status pages.
  2. Select which monitors/components to expose and tune the error budget you want to display.
  3. Add branding, SEO/metadata, and optional signed share links for granular access.
  4. Use the “Refresh” action to regenerate the cached summary; the page streams top sections first so stakeholders see signal fast.

For customers who need proof, the Trust dashboard surfaces public incidents, uptime proofs, and downloadable audit trails.

Audit logs and exports

  • Open Dashboard → Audit logs to view every action tied to your account or subusers.
  • Filter by actor, path, or response status. Export results for compliance reviews.
  • All entries include method, path, IP, user agent, duration, and the acting user/subuser.

Because logs are stored efficiently, keeping them enabled is low overhead compared to traditional request logs.