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.

3. Assign monitors#

Pick which of your monitors should run this check. By default a new check only offers monitors you’ve enrolled yourself. If your organisation has opted in to the shared monitor fleet, you can also assign checks to it from here.

Running a check from more than one monitor is how Tenpm Uptime tells “the target is actually down” apart from “one monitor’s own network is having a bad day” — a single monitor’s report is used as-is, but with several, a check is only marked down once a majority agree.

4. Save#

Save the check and it starts running on its next scheduled tick. It appears as a new column-crossing-row on your Dashboard once the first result comes in.

What’s next#

Continue to Reading the dashboard.

Backward Adding your first monitor Reading the dashboard Forward