Getting Started on Tenpm Uptime Docs

Creating an account

Mon, 01 Jan 0001 00:00:00 +0000

Creating an account#

Tenpm Uptime accounts are self-serve: you sign up with just an email address, and nothing is created until you confirm you own it.

Go to the login page and choose Create an account.
Enter your email address and submit.

You’ll see the same confirmation either way, whether or not that address already has an account — this is deliberate, so the page can’t be used to check who else is a Tenpm Uptime customer.

Adding your first monitor

Mon, 01 Jan 0001 00:00:00 +0000

Adding your first monitor#

A monitor is the small agent that actually runs your checks. It’s a standalone, open-source binary that you run on your own infrastructure — a home server, a VPS, a container, wherever you’d like your checks to run from. The Tenpm Uptime server never runs your checks itself; it just hands the monitor a list of what to check and collects the results back.

Because the monitor runs on hardware you control, it can reach targets the public internet can’t — internal admin pages, LAN devices, anything behind a firewall.

Creating your first check

Mon, 01 Jan 0001 00:00:00 +0000

Creating your first check#

A check is the thing you want watched — a URL, a TCP port, a TLS endpoint — and the rule that decides whether it’s healthy. Your monitors run it on the schedule you set and report the result back.

1. Open the check form#

Go to Checks and choose Add a check.

2. Describe the target#

Name — how it shows up on your Dashboard.
URL / target, prefixed with a scheme that tells Tenpm Uptime how to reach it:
- http:// or https:// — a web endpoint. This is the common case.
- tcp://host:port — a raw TCP connection, with an optional banner to match against.
- tls://host:port — a bare TLS handshake, for services that expect TLS as the very first bytes on the wire (an SMTPS or IMAPS port, for example), where an https:// check would fail and a tcp:// check would just time out waiting for a plaintext banner.
Check interval — how often it should run.

Every scheme also supports pass/fail rules beyond “did it connect” — matching response content, requiring a specific status code, and more. Start simple here; those options are covered in a dedicated guide once you’re ready for them.

Reading the dashboard

Mon, 01 Jan 0001 00:00:00 +0000

Reading the dashboard#

The Dashboard is a grid: your checks down the side, your monitors across the top, and each cell showing whether that check passed the last time that monitor ran it. It refreshes on its own every 30 seconds.

Layouts#

Use the view switcher at the top of the page to change how monitors are grouped:

Collapsed (the default) — every monitor merged into a single column per check, so you see an up/down count rather than a wall of cells. Good for a quick glance across a lot of checks.
Grid — one column per monitor, so you can see exactly which monitor is reporting a failure.
By class — splits your own monitors from the shared fleet into two groups, useful once you’re using both.

Your choice is remembered in the page’s own link as you navigate, so paging or filtering won’t silently reset it back to the default.

Getting Started on Tenpm Uptime Docs

Creating an account

Creating an account#

1. Sign up#

Adding your first monitor

Adding your first monitor#

Creating your first check

Creating your first check#

1. Open the check form#

2. Describe the target#

Reading the dashboard

Reading the dashboard#

Layouts#